Donald MacVicar wrote: > Andrew DeFaria wrote: > >> Sam Edge wrote: >> >>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere] >>> @="&Bash Prompt Here" >>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command] >>> @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\"" >>> [HKEY_CLASSES_ROOT\Drive\shell\BashHere] >>> @="&Bash Prompt Here" >>> [HKEY_CLASSES_ROOT\Drive\shell\BashHere\command] >>> @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\"" >> >> >> Personally I'm fond of "Bash this!" instead of "Bash Prompt Here" :-) ! >> >> Also, the above does not handle the issue of the user's startup >> scripts. Here's what I have: >> >> HKEY_CLASSES_ROOT\Directory\shell\BashHere] >> @="B&ash this!" >> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command] >> @="rxvt -e bash -c \"cd '%1';exec bash -rcfile ~/.bash_login\"" >> [HKEY_CLASSES_ROOT\Drive\shell\BashHere] >> @="B&ash this!" >> [HKEY_CLASSES_ROOT\Drive\shell\BashHere\command] >> @="rxvt -e bash -c \"cd '%1';exec bash -rcfile ~/.bash_login\"" >> >> Note if you do not wish to use rxvt then simply remove the "rxvt -e " >> portion. This also makes the assumption that Cygwin's bin is in your >> Windows System Environment variable PATH (which is should be, >> especially if you use inetd) and that you've appropriately named your >> bash startup stuff .bash > > > surely you could just have @="rxvt -ls -e bash -c \"cd '%1'; exec bash > --login\"" and then all the startup scripts would be run properly?
Nope! Because --login runs /etc/profile and /etc/profile cd's to $HOME! > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/