Quoth Chetan <[email protected]>: > Sebastian Tennant <[email protected]> writes: > >> Ignore this entire thread! >> >> If you want your shell aliases and functions to be accessible via 'M-!' >> (shell-command) then use this two-line solution: >> >> http://article.gmane.org/gmane.emacs.help/61529 >> >> Thanks to Michael Heerdegen for pointing this out. >> >> Sebastian > > This has the undesirable effect on shell scripts written by someone > else and possibly your own. There is obviously a reason why aliases > are not loaded by default in non-interactive shells, but they can be > enabled if one is prepared to deal with it.
Indeed, and Peter Dyballa made the same point on gmane.emacs.help: http://article.gmane.org/gmane.emacs.help/61533 I argue that as BASH_ENV is set in ~/.emacs, and not elsewhere, it can only potentially cause problems with scripts/commands called/issued from inside Emacs, i.e., cron/at jobs are unaffected. But yes, if people are at all worried they should use my functions (interactive-shell-command and asynchronous-interactive-shell-command) rather than setting BASH_ENV. Sebastian _______________________________________________ gnu-emacs-sources mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-emacs-sources
