RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro

["Stephan Mueller" <smueller at Exchange dot Microsoft dot com>]

On NTish systems (including Windows 2000, XP, Server 2003) cmd.exe has
gained some useful enhancements over the years.  Find much of the new
stuff in the output of
	set /?
	for /?
	if /?
	call /?
Of particular interest here: call /? documents that %* is supported as a
way to get all the arguments (and from personal experience, it looks a
lot like it's implemented as if your code simply gets a pointer into the
buffer containing the text you typed -- spaces between arguments and all
quoting are exactly unchanged.  Sometimes this extra info can be
helpful.  Some of this stuff requires command extensions to be enabled
(as Igor hinted at below).

Another way to work around the 9 argument limit is with a for (or
goto-based) loop that works with %1 and uses shift to iterate through
all the arguments.

I'm not saying any of this is pretty, just that it's there for those
cases when you need to write it in batch.

stephan();



-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
Of Hannu E K Nevalainen (garbage mail)
Sent: Sunday, July 27, 2003 5:17 AM
To: cygwin@cygwin.com
Subject: RE: DLL 1.3.22 - etags 5.5.4 fails on XP Pro


> From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
> Sent: Sunday, July 27, 2003 2:22 AM

> On Sat, 26 Jul 2003, Hannu E K Nevalainen (garbage mail) wrote:
>
> > > From: cygwin-owner@cygwin.com
> [mailto:cygwin-owner@cygwin.com]On Behalf
> > > Of Igor Pechtchanski
> >
> > --8<--
> > > What you could do is create an "etags.bat" that runs 'bash -c
> etags "%1"
> > > "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"', put it in your PATH, and

> > > you should be able to call that from NTEmacs.
> > >       Igor
> >
> >  Hmm... I can't remember if there is a equiv. of $@ in 
> > DOS/BAT-files...
> >
> > $ man bash
> > /\$\@

> AFAIK, there isn't, at least on Win9x.  WinNT/2k command extensions 
> might have something, though.  Another reason not to use it is that 
> you'd probably want to cygwinize the paths anyway, by calling cygpath 
> on each parameter...
>
> BTW, the one advantage of using a batch file is that invoking "etags" 
> from a DOS/Windows program will automatically call that file (just 
> like with a .exe), but a link will not get invoked (and neither will 
> the shell script).
> 	Igor

 The one limitation is the one of max _nine_ arguments/option flags.
There are times when that can be a severe limitation. Dunno if it fits
this time though.

> P.S. I know very well what $@ is, thank you very much. ;-)

 =-) there might be others here that don't - feel free to "take it or
leave it" ;-P

/Hannu E K Nevalainen, B.Sc EE/Microcomputer systems, 59?14'N, 17?12'E.
--END OF MESSAGE--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/