RE: [h-e-w] cygwin setup guide / Emacs from Bash Question

[Sprenger, Karel]

Hi,

In my ~/.bashrc I have the following stuff related to emacs:

INFOPATH='/emacs/info;/usr/info;/usr/local/info'
alias edit='gnuclientw'
alias emacs='INFOPATH=`cygpath --windows --path $INFOPATH`;/emacs/bin/emacs'

Normally, I have emacs already up and running when I open up a Bash shell 
window and then I use the edit alias to well edit files :-)  If emacs is not 
already running, I use the emacs alias to start it after fixing the INFOPATH 
setting so emacs will grok it.   Hope this helps.

Cheers,
Karel

-----Original Message-----
From: Paul Whitfield [mailto:address@hidden
Sent: donderdag 23 mei 2002 3:37
To: Emacs Help (Windows)
Subject: Re: [h-e-w] cygwin setup guide / Emacs from Bash Question


Underwood, Jonathan wrote:
>>From the Cygwin FAQ (www.cygwin.com):
> 
> ;; This assumes that Cygwin is installed in C:\cygwin (the
>       ;; default) and that C:\cygwin\bin is not already in your
>       ;; Windows Path (it generally should not be).
>       ;;

This is a strange comment... I always have cygwin in my
path... otherwise I don't get to use ls, find, etc etc
from the command prompt.

One think I find is that If I every run emacs (well actually
gnuclientw.exe) from the bash prompt it does weird things
to my environment. The cygwin environment screws up my
normal emacs environment.

Does anyone have a work arround for this?
Currently my only solution is to never run emacs from
bash... which is a pain since I you cygwin based development
tools.

Paul