3 ms·
What has always been a blocker for me to follow your example, is the desire to use many such scripts from the command lines provided inside an $editor or $email
by ta8645 4y ago
What has always been a blocker for me to follow your example, is the desire to use many such scripts from the command lines provided inside an $editor or $email client. There probably is a way to configure both of them to see the aliases, but it's more straightforward to just have everything in the PATH.
- nequo 4y agoYes, it seems cleaner to just put "export PATH=$HOME/bin:$PATH" in $HOME/.bashrc. That avoids collisions with /usr/bin and /usr/local/bin. (Or rather, resolves collisions in favor of your personal bin directory.)
- account42 4y agoYour PATH is inherited by child processes that you start, including scripts that expect the system version of commands that have the same name as your commands.