[27524] in Athena Bugs
Re: Debathena: emacs
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Jan 12 13:07:38 2011
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@mit.edu>
In-Reply-To: <201101121651.p0CGpPAm009464@outgoing.mit.edu>
Date: Wed, 12 Jan 2011 13:07:35 -0500
Message-Id: <64264FEF-A683-48E7-9F53-75BFE6301C86@mit.edu>
To: boojum@mit.edu
Content-Transfer-Encoding: 8bit
Cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu
I can't reproduce this on ten-thousand-dollar-bill. Are you sure this isn't something in one of your dotfiles? I think we generally try not to depend on things in lockers (in this case, the gnu locker).
-Jon
On Jan 12, 2011, at 11:51 AM, boojum@MIT.EDU wrote:
> System name: ten-thousand-dollar-bill
> Type: x86_64
> Display type: VMware SVGA II Adapter
>
> Shell: /bin/athena/tcsh (?)
> Window manager: unknown
>
> What were you trying to do?
> M-x find-grep-dired to grep through files
>
> What's wrong:
> It appears to have ggrep hard coded in as the grep of choice,
> but can't find it. The grep output looks like:
>
> /tmp/:
> find . \( ! -type d -exec ggrep -q lkj {} \; \) -exec ls -ld \{\} \;
> find: `ggrep': No such file or directory
> find: `ggrep': No such file or directory
> ...
>
> What should have happened:
> It should have grepped, either by using a version of grep on the
> machine, or grabbing one from somewhere else in AFS, I suppose.
>
> Please describe any relevant documentation references:
>
> HELP buffer (hey, it says "grep" in the command here, not "ggrep")
>
> find-grep-dired is an interactive compiled Lisp function.
>
> (find-grep-dired DIR REGEXP)
>
> Find files in DIR containing a regexp REGEXP and start Dired on output.
> The command run (after changing into DIR) is
>
> find . -exec grep -s -e REGEXP {} \; -ls
>
> Thus ARG can also contain additional grep options.
