On Tue, Jun 2, 2020 at 4:54 PM Rich Siegel <[email protected]> wrote:
On 6/2/20 at 4:19 PM, [email protected] (TJ Luoma) wrote: > > >1. Where is BBEdit getting its $PATH definition from? > > Your Unix login environment (e.g. ~/.bash_profile or equivalent > for zsh or whatever shell it is you're using). So, $PATH should > be the same in BBEdit as it is in Terminal. > 1. That is obviously the smartest way to do it, and so I should have assumed that would be the way that BBEdit would do it. 2. For those new to zsh, make sure that your $PATH is set in ~/.zshenv 3. FWIW, I have used this at the top of my scripts for a long time: if [[ -e "$HOME/.path" ]] then source "$HOME/.path" else PATH=/usr/local/scripts:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin fi That way I can define a PATH in a file un-creatively named ~/.path and have it automatically apply to all of my scripts (which makes it easy to update/change), but if (for some reason) that file is not there, it will use my most commonly desired PATH. TJ -- This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email "[email protected]" rather than posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/CADjGqHvc54yGKvSYk%3DqBffLHnkF%2ByWPZNAaCBwpFXpU06Db3dw%40mail.gmail.com.
