VMD-L Mailing List

From: Pacci Evaristo, Felipe Fabricio (felipepacci_at_gmail.com)
Date: Tue Dec 21 2021 - 13:10:55 CST

Hi FX,

I followed your advice and was able to recover the desired behavior! The
way I'd been doing things before, I had the following content for the
executable /usr/local/bin/vmd:

#!/bin/bash
>

"/Applications/VMD 1.9.4a55-arm64-Rev11.app/Contents/MacOS/VMDLauncher" $1
> $2 $3 $4 $5 $6

Changing the path in /usr/local/bin/vmd to "/Applications/VMD
1.9.4a55-arm64-Rev11.app/Contents/MacOS/startup.command" was all it took to
"fix" my issue.

Thanks for your help,

*Felipe Fabricio Pacci Evaristo*

*Mobile:* +1(773)569-2978

*Email:* felipepacci_at_gmail.com

*Skype:* felipepacci

*Pronouns:* he/him/his

On Thu, Dec 16, 2021 at 10:42 PM FX <fxcoudert_at_gmail.com> wrote:

> Hi,
>
> I don’t think things have changed with ARM macOS. If you open the app with
> “open /path/to/VMD.app” then its working directory resets to $HOME. You can
> run it in the current directory by bypassing open, and simply running
> "/Applications/VMD.app/Contents/MacOS/startup.command”
>
> FX