Re: Aliases no longer defined?

[Rolf Campbell <rcampbell at tropicnetworks dot com>]

Peter Davis wrote:
> To recap, this same exact .bashrc file used to work, on my previous
> Windows(2000) machine. Now, on WinXP, it doesn't.  In fact, even if I
> explicitly type "source~/.bashrc" at the shell prompt, it doesn't work. 
This is because ~ expands to ${HOME}, which is /cygdrive/c/home.

> I don't get errors, but the aliases are not defined. That is the problem
> I've been seeing. I'd like to have some aliases for common commands, and
> I'd like to be able to set some environment variables, like adding some
> dirctories to my path. (These don't need to be in the Windows-wide
> path... just in Cygwin.) Also, copying .bashrc to .bash_profile and then
> starting a new bash shell doesn't work.
>
> If anyone can tell me how to define these aliases and environment
> variables, I'll be*very* grateful.
>
>
>
> > You can still set your HOME, there's nothing (that I know of!) wrong
> > with doing so.
>
>
>
> Igor suggested that my $HOME is set wrong, although everything worked on
> my old machine with this same setting.  What should this be, and how
> should it get set?
You should not set it.  Cygwin will do it for you.

If you want Emacs to work, then set it to your real cygwin home, and 
move your .emacs* files into your real home dir. (That's the way I do it).



--
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/