True, and one of the reasons why I use NT Emacs rather than the cygwin
port is that it fully understands Windows sytle naming conventions and
drive identifiers. Since everything has to be mounted under fake mount
points with cygwin there really is quite a disjoint between the two.
Certainly not insurmountable, but annoying all the same.
I've really not found a good free solution and so I still use MKS Toolkit.
As an aside, the realy stumbling block that I have with cygwin is that
it's pty handling screws with the way that Java, a the Java Service
Wrapper and stdout interact. Basically the combination works just fun
under MKS sh and cmd.exe and doesn't under cygwin. Very frustrating.
Guy
Stephen Leake wrote:
Neil Mackie <[EMAIL PROTECTED]> writes:
But why would a shell be a concern when you can do everything from
within emacs? &8->
I see the smiley, but for newbies we should make clear: a _lot_ of the
functionality of Emacs as an Integrated Development Environment comes
from the ability to run shell commands. So a Gnu-compatible shell
(such as Cygwin bash) enhances Emacs tremendously.
--
Guy Gascoigne - Piggford
www.wyrdrune.com
