igrep-find - default "File(s)" argument no longer includes path
Steven E. Harris
`igrep-find', making it difficult to search for files in any directory
but the current one. My previous version of igrep prompted for a file
pattern by offering the buffer's current working directory followed by
a sensible wildcard:
,----[ Old `igrep-find' prompt ]
| egrep File(s): ~/src/foo/bar/baz/*
`----
With this, I could easily back up a few directories or edit the path
in any way. It was easy to search in a directory distant from the
current buffer's directory.
The new prompt comes up with a nice default wildcard, but omits the
directory:
,----[ New `igrep-find' prompt ]
| [find] egrep File(s) [default: *.cpp]:
`----
I know that I can then start typing "../../" and tabbing around, but I
can't figure out how to get the directory back into the default
prompt.
By default, the igrep uses the function `igrep-files-default' (bound
to `igrep-buffer-file-name-pattern') to build the file prompt. I don't
see a similar function to restore the old behavior.
* * *
For the record, trying to search within, say, "~/src/" fails due to
`shell-quote-argument' around line 812 in igrep.el:
,----[ (igrep-find "egrep" "foo" '("~/src/*") nil) ]
| cd /usr/local/lib/xemacs/xemacs-packages/lisp/igrep/
| find \~/src -type d \( -name RCS -o -name CVS -o -name SCCS \) -prune -o -type f \! -name \*\~ \! -name \*\,v \! -name s.\* -print0 | xargs -0 -e egrep -n -e foo /dev/null
| find: ~/src: No such file or directory
|
| igrep exited abnormally with code 123 at Thu Sep 5 09:47:11
`----
--
Steven E. Harris :: seha...@raytheon.com
Raytheon :: http://www.raytheon.com
Stephen J. Turnbull
Steven> The most recent igrep package behaves differently when
Steven> using `igrep-find',
Please report this as a bug using either the procedure recommended for
the igrep package, or M-x report-xemacs-bug.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py