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 15:49:01 -0500
> Robinow, David writes:
> > 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)
>
> That might be a clue. I ran this on:
> CYGWIN_NT-4.0 GIRCH19 1.1.4(0.26/3/2) 2000-08-03 20:53 i686 unknown
> GNU bash, version 2.04.0(1)-release-(i586-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.)
>
> Um, without etags.exe how do you get any output? Do you mean you used
> /usr/bin/etags? My (probably slightly outdated) etags claims to be:
> Exuberant Ctags 3.5.1, by Darren Hiebert <darren@hiebert.com>
No, I used the etags.exe from NTemacs 20.7 which is what you referred
to in your post.
What I meant is that I am not normally a user of these tools so my
understanding is limited.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com