change to igrep btwn 2.87 and 2.95?

[Stuart Popejoy]

Hello,

I recently did a big package upgrade which included igrep. I make
heavy use of igrep-find while programming, and I was wondering if there is
a way to make igrep specify it's file(s) target like it did in 2.87.

In the past, after specifying the expression to grep on, I was
prompted for the file(s) target like:
Search File(s):/foo/bar/baz/*.c

This is assuming I'm editing something.c and am in /foo/bar/baz. Thus,
if I wanted to search everything below /foo, i simply deleted back to
that and hit enter/

Now, the prompt simply asks for "*.c"; if I want to search above the
current directory, i have to enter "../../.." etc. This works, but
it's a lot less intuitive to see what directory I'm searching.

Is there any way to return igrep to it's old prompting style, or is it
"the new way or the highway"?

Much Thanks,
Stuart Popejoy

[Steven E. Harris]

Stuart Popejoy <stuart-at-pink...@ilovespam.net> writes:

> In the past, after specifying the expression to grep on, I was
> prompted for the file(s) target like:
> Search File(s):/foo/bar/baz/*.c
>
> This is assuming I'm editing something.c and am in /foo/bar/baz. Thus,
> if I wanted to search everything below /foo, i simply deleted back to
> that and hit enter/

I wrote about a similar problemน in September and agree that the new
interface is lacking. Stephen Turnbull suggested that I file a bug
against igrep, but I dropped the ball and never filed it. Feel free to
use my post in composing a bug report.

Footnotes:
น http://groups.google.com/groups?&threadm=87ptvs74tf.fsf%40harris.sdo.us.ray.com

--
Steven E. Harris :: seha...@raytheon.com
Raytheon :: http://www.raytheon.com