Re: [h-e-w] Etags (different results from cmd or from emacs)

[Andrei Stebakov]

It's good that you mentioned the shell, as I was only thinking of the find or etags commands.
I looked into the .emacs file and noticed that I have two conflicting shells one is in
'(w32shell-shell (quote cmd))
another one was
(setq explicit-shell-file-name "bash")
I didn't notice the moment when '(w32shell-shell (quote cmd)) crept into the custom-set-variables, so after I set it to bash my 
"find.exe . -iname '*.cpp' -o -iname '*.h' -o -iname '*.c' | xargs etags"
command started to produce the consistent result tags file, which I can create if I run the same command from shell (either cmd or bash).
Now, I'll keep an eye on igrep-find and see if I have the same problem as before (different results when running the same command multiple times).

Thank you,
Andrew

On Fri, Jun 27, 2008 at 5:05 AM, Eli Zaretskii <address@hidden> wrote:

> Date: Thu, 26 Jun 2008 14:23:38 -0400
> From: "Andrei Stebakov" <address@hidden>

>
> I've been lately having problems with running cygwin's find.exe and etags
> from Emacs (Emacs-23-CvsP080612-EmacsW32-1.58.exe installer)
> When I use igrep-find (which uses cygwin's find.exe) from emacs, it takes
> much longer and returns partial results or no results at all so I need to
> run the same command again.

Does this happen if you use natively-compiled binaries of find.exe?

> With etags, if I run this command from cmd:
> "find.exe . -iname '*.cpp' -o -iname '*.h' -o -iname '*.c' | xargs etags"
> It create tags file of approximately 9MB and I can see all tags are there.
> If I run it from emacs:
> (shell-command "find.exe . -iname '*.cpp' -o -iname '*.h' -o -iname '*.c' |
> xargs etags")
> The size of resulting tags file is ~4MB and it misses tags.

What shell is used when you run shell-command?