This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: etags problem in bash, not in cmd.exe
- To: 'Markus Hoenicka' <Markus dot Hoenicka at uth dot tmc dot edu>, cygwin at sourceware dot cygnus dot com
- Subject: RE: etags problem in bash, not in cmd.exe
- From: "Robinow, David" <drobinow at dayton dot adroit dot com>
- Date: Fri, 1 Dec 2000 14:05:00 -0500
> I ran into a problem with the etags.exe shipped with NTEmacs
> 20.7.1. I'm not sure whether it is an etags problem or a CygWin bash
> problem, therefore I ask on both sides.
>
> My setup:
> I use the CygWin bash as the default shell in NTEmacs. I also use the
Which version of cygwin/bash? I've got:
CYGWIN_NT-4.0 MENACE 1.1.6(0.30/3/2) 2000-11-21 21:00 i686 unknown
GNU bash, version 2.04.0(8)-release (i686-pc-cygwin)
and I don't get this error. (I just tried your example, I don't use
etags.exe or tdtd so my test is only as good as your example.)
> Now I add one space after ENTITY. This should not change the
> etags output
> as there is one space in the test file after ENTITY. In cmd.exe I get:
> F:\home\markus\workspace\test2>d:\win32app\emacs207\bin\etags
> --regex='/<!\(ELEMENT\|ENTITY \)/' --output=- tutorial.dtd
> ?
> tutorial.dtd,33
> <!ENTITY ¦8,378
> <!ELEMENT¦12,592
>
> whereas in bash I end up with:
> $ /cygdrive/d/win32app/emacs207/bin/etags.exe
> --regex='/<!\(ELEMENT\|ENTITY \)/' --output=- tutorial.dtd
> ?
> tutorial.dtd,19
> <?xml version=¦1,0
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com