GNU bug report logs - #68697
Add option to not always use *grep* buffer when executing `grep' or `vc-git-grep' command

Previous Next

Full log

Message #14 received at 68697 <at> debbugs.gnu.org (full text, mbox):

From: Nafiz Islam <nafiz.islam1001 <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 68697 <at> debbugs.gnu.org
Subject: Re: bug#68697: Add option to not always use *grep* buffer when
 executing `grep' or `vc-git-grep' command
Date: Thu, 25 Jan 2024 09:58:10 -0500

[Message part 1 (text/plain, inline)]

Oh right, I can use compilation-buffer-name-function. My only issue is that
it doesn't have enough context to generate a meaningful buffer name; it
only takes a name-of-mode. A meaningful buffer name could consist of the
regexp or the entire grep shell command.

On Thu, Jan 25, 2024 at 2:24 AM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Nafiz Islam <nafiz.islam1001 <at> gmail.com>
> > Date: Wed, 24 Jan 2024 15:16:12 -0500
> >
> > The way `grep' and `vc-git-grep' works right now is that it will always
> output its result to a buffer called
> > `*grep*'. So, if I perform another `grep' command, it will overwrite the
> previous grep result (unless I
> > rename the buffer beforehand).
> >
> > I would like, at least, an option to create a new buffer each time a
> `grep' command is executed.
> > Maybe each new buffer could be given the name based on the regexp or the
> grep shell command
> > used.
>
> Did you try to define a compilation-buffer-name-function that would do
> what you want?  Such a function can produce any buffer name you want.
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.