How about just renaming the find.exe that comes with Windows. At least this
is what I did few months back and so far no problems.
- Niranjan
-----Original Message-----
From: Steve Haflich [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 18, 2000 9:08 AM
To: Yaroslav Bulatov
Cc: [EMAIL PROTECTED]
Subject: Re: JTags -- parameter not correct
From: Yaroslav Bulatov <[EMAIL PROTECTED]>
Does anybody see the following messages when changing to directory of the
project and running jtags from bash? --
C:/emacs/site/jde-2.2.2/lisp/jtags
Tagging classes and constructors
FIND: Parameter format not correct
etags: no input files specified.
I haven't seen this specifically, but can offer a good guess as to the
source of the problem:
Obviously you are running on Windows. On Windows there are two very
different find commands -- one is the native Windows utility, and the
other is typically the Unix-like command such as is provided by
Cygwin. Although these have similar function (searching filesystems
for files) they otherwise have completely different command
interfaces, etc.
I don't know how to fix this, but two strategies to investigate are
- changing the Windows search PATH order in autoexec.bat
- locating the place find is invoked and providing a more-explicit
path to the Unix/Cygwin/whatever version.
The first approach may be dangerous, so I'd try the second. But
perhaps someone else has already solved this and can provide better
info about a solution...