On Mon, 31 Mar 2003, Peter Davis wrote:
> I recently switched from Windows NT4 and Windows 2000 to Windows XP. I
> installed cygwin freshly on both systems. Now I'm noticing that on both
> systems, .bashrc seems to be completely ignored. I haven't changed this
> file at all, but suddenly the aliases I define and export are not
> defined when I try to type them at the shell prompt.
>
> If I do
>
> source ~/.bashrc
>
> it works without error, but the aliases are *still* not defined. I
> noticed by running 'cygcheck -s' that the new systems seem to have DLL
> build 1.3.22 (3/18/2003), while the older ones were running build 1.3.20
> (2/18/2003). However, nothing else has changed. This used to work, but
> now doesn't.
>
> Any clues?
>
> Thanks,
> -pd
Two questions: is bash invoked with a --login option, and is ~/.bashrc
readable by the user you invoke bash as? If bash is invoked with --login,
the file executed is .bash_profile, not .bashrc. I solve this by making
.bash_profile a symlink to .bashrc.
Igor
P.S. On an unrelated note, the use of shell functions is recommended over
the use of aliases.
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Knowledge is an unending adventure at the edge of uncertainty.
-- Leto II
--
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/
