[..]
> Granted, functions are more useful, but I haven't gotten around to
> really incorporating any of my own functions into $HOME/.bashrc yet.
> Aliases can be written much faster.
> The above clippings seem to be a very very good solution. However,
> think Bash should be smart enough (ie. have an option) to source any
> aliases (or functions in bashrc) if called non-interactively.
Well that's precisely what setting the 'reserved' $BASH_ENV environment
variable does.
Why they had to implement it in this roundabout way rather than via
a straightforward command-line flag is something you may want to ask the
bash maintainers.
May be worth your time, come to think of it: I am running a fairly old
bash 3.2 (debian stable) and things may have improved in this respect.
Let me know if you find anything useful.
Thanks,
cj
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment