[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [h-e-w] etags with ntemacs 21.1
From: |
Gallucci, David |
Subject: |
RE: [h-e-w] etags with ntemacs 21.1 |
Date: |
Tue, 13 Nov 2001 14:01:39 -0500 |
I had the same dilema, and use the following line at the shell command
prompt. ( M-! )
dir /b *.h *.cpp | etags -
I am piping the output of the dir command to etags. The trailing hyphen
tells etags to read the file list from stdin. Works for me. Also, you can
add the /s switch to the dir command to recurse an entire directory tree.
HTH,
Dave Gallucci
-----Original Message-----
From: Jim Davidson [mailto:address@hidden
Sent: Tuesday, November 13, 2001 1:24 PM
To: address@hidden
Subject: [h-e-w] etags with ntemacs 21.1
Dr Francis J. Wright writes:
> Maybe the 20.7 version was compiled so as to support wildcards
> internally, whereas the 21.1 version is not and assumes that a shell
> will expand them. Have you tried running it under a UNIX-style shell,
> such as Cygwin bash? (Actually, sh should suffice for just expanding
> wildcards.)
Good point. I hadn't thought about how the wildcards were expanded.
Actually, I do use cygwin bash, but I had a .bat file that I use to update
my
TAGS table. I switched that to a shell script, and things work again.
It would still be convenient, IMO, to have wildcard expansion inside the
etags
utility, since it used to be there, but it's not a show-stopper.
-Jim