Specifically you'll see # > conda initialize >.īelow that is Anaconda setting its own directories to the front of $Path. Open that and you should see some lines towards the bottom dealing with anaconda. If you're in my situation or are just using Anaconda then here is where you can edit path. Where to do this was very confusing since there are multiple areas that deal with your $PATH variable according to Google searching. I wanted to edit the $PATH variable in an editor somewhere since I wanted to put one directory first and then later remove it.

I'm running MacOS Ventura and have Anaconda installed which is also initialized in the terminal. I'm posting my scenario here in case anyone else ends up here with slap-dash bash skills. The solution I used was to symlink the libraries needed into /usr/local/lib The reason was that I had a custom path that included some libraries required by the application, but that was not available when the application was run by the launcher. In my case, the problem is that my application was crashing when run via the application launcher, but runs fine when run from a terminal window. That can cause all sorts of trouble, for example if you setup you environment to use a specific version of Java: your application will not see that and use the 'default' java, which will be the one with the highest version number. Meaning that your profile is not run and that your custom settings (PATH, environment variables.

In all those cases, the application itself (i.e the binary or shell script inside the application) is launched by launchd without any parent shell. You launch your applications in diverse ways: click the icon in /Applications, or type the name in Spotlight search, or click an icon in the Dock. They are not read by the processes that are used to launch your applications. bash_profile etc.) are only read by login shells. There's one important fact I only realized today while debugging a problem: the profile settings (.

Default macos folder locations