On Wed, Feb 27, 2013 at 3:15 PM, Kevin Layer wrote: > That was one of the experiments I did, and I saw no evidence that any > commands were executed. I even passed it as the argument to the > invocation. > > As for the assumption, I understand that an error could have > short-circuited the processing of my init file, but in the bash's that > haven't read it, > > . .bashrc > > produces no errors *and* has my aliases and new prompt.
$HOME/.bashrc isn't always read. It depends on how bash is executed. If this is a --login you need $HOME/.bash_profile that sources $HOME/.bashrc. http://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html#Bash-Startup-Files -- Earnie -- https://sites.google.com/site/earnieboyd -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple