GNU logs - #68697, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#68697: Add option to not always use *grep* buffer when executing `grep' or `vc-git-grep' command
Resent-From: Nafiz Islam <nafiz.islam1001@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 24 Jan 2024 20:17:02 +0000
Resent-Message-ID: <handler.68697.B.17061274079902 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 68697 <at> debbugs.gnu.org
MIME-Version: 1.0
From: Nafiz Islam <nafiz.islam1001@HIDDEN>
Date: Wed, 24 Jan 2024 15:16:12 -0500
Message-ID: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
Content-Type: multipart/alternative; boundary="0000000000009c2096060fb6bcc8"
Received-SPF: pass client-ip=2a00:1450:4864:20::632;
 envelope-from=nafiz.islam1001@HIDDEN; helo=mail-ej1-x632.google.com
X-Spam_score_int: -18
X-Spam_score: -1.9
X-Spam_bar: -
X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org",
 has NOT identified this incoming email as spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 Content preview: 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 resu [...] 
 Content analysis details:   (1.2 points, 10.0 required)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends
 in digit (nafiz.islam1001[at]gmail.com)
 -0.0 SPF_HELO_PASS          SPF: HELO matches SPF record
 1.0 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail
 provider (nafiz.islam1001[at]gmail.com)
 0.0 HTML_MESSAGE           BODY: HTML included in message
 -0.0 T_SCC_BODY_TEXT_LINE   No description available.
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: 0.2 (/)

--0000000000009c2096060fb6bcc8
Content-Type: text/plain; charset="UTF-8"

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.

--0000000000009c2096060fb6bcc8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The way `grep&#39; and `vc-git-grep&#39; works right =
now is that it will always output its result to a buffer called `*grep*&#39=
;. So, if I perform another `grep&#39; command, it will overwrite the previ=
ous grep result (unless I rename the buffer beforehand).</div><div><br></di=
v><div>I would like, at least,  an option to create a new buffer each time =
a `grep&#39; command is executed. Maybe each new buffer could be given the =
name based on the regexp or the grep shell command used.<br></div></div>

--0000000000009c2096060fb6bcc8--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Nafiz Islam <nafiz.islam1001@HIDDEN>
Subject: bug#68697: Acknowledgement (Add option to not always use *grep*
 buffer when executing `grep' or `vc-git-grep' command)
Message-ID: <handler.68697.B.17061274079902.ack <at> debbugs.gnu.org>
References: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
X-Gnu-PR-Message: ack 68697
X-Gnu-PR-Package: emacs
Reply-To: 68697 <at> debbugs.gnu.org
Date: Wed, 24 Jan 2024 20:17:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 68697 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
68697: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D68697
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#68697: Add option to not always use *grep* buffer when executing `grep' or `vc-git-grep' command
Resent-From: Eli Zaretskii <eliz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 25 Jan 2024 07:26:02 +0000
Resent-Message-ID: <handler.68697.B68697.17061675115614 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Nafiz Islam <nafiz.islam1001@HIDDEN>
Cc: 68697 <at> debbugs.gnu.org
Date: Thu, 25 Jan 2024 09:24:50 +0200
Message-Id: <86plxpdge5.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
In-Reply-To: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
 (message from Nafiz Islam on Wed, 24 Jan 2024 15:16:12 -0500)
References: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> From: Nafiz Islam <nafiz.islam1001@HIDDEN>
> 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 sent to bug-gnu-emacs@HIDDEN:

Subject: bug#68697: Add option to not always use *grep* buffer when executing `grep' or `vc-git-grep' command
Resent-From: Juri Linkov <juri@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 25 Jan 2024 07:49:01 +0000
Resent-Message-ID: <handler.68697.B68697.17061688948014 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Nafiz Islam <nafiz.islam1001@HIDDEN>
Cc: 68697 <at> debbugs.gnu.org
From: Juri Linkov <juri@HIDDEN>
In-Reply-To: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
 (Nafiz Islam's message of "Wed, 24 Jan 2024 15:16:12 -0500")
Organization: LINKOV.NET
References: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
Date: Thu, 25 Jan 2024 09:45:40 +0200
Message-ID: <86plxp9a4k.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> 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.

I'm using such config to create unique buffer names for
`compile' and `grep':

```
(setq compilation-buffer-name-function
      (lambda (name-of-mode)
        (generate-new-buffer-name
         (concat "*" (downcase name-of-mode) "*"))))
```

Currently in bug#68570 we are discussing about adding an option
to `project-compilation-buffer-name-function' to create unique names
for project compilation buffers.

So the same way we could turn `compilation-buffer-name-function'
into a defcustom with an option for unique compilation/grep buffers.

> Maybe each new buffer could be given the name based on
> the regexp or the grep shell command used.

A name based on a regexp could be another option indeed.
Here is what I'm using for xref buffer names with a regexp:

```
(with-eval-after-load 'project
  ;; Instead of numbers append the regexp to the xref buffer name:
  (define-advice project-find-regexp (:around (ofun &rest args) unique)
    (require 'xref)
    (let ((xref-buffer-name
           (generate-new-buffer-name
            (format "%s<%s>" xref-buffer-name (car args)))))
      (apply ofun args))))
```

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#68697: Add option to not always use *grep* buffer when executing `grep' or `vc-git-grep' command
Resent-From: Nafiz Islam <nafiz.islam1001@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 25 Jan 2024 14:59:01 +0000
Resent-Message-ID: <handler.68697.B68697.170619471510132 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 68697
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Eli Zaretskii <eliz@HIDDEN>
Cc: 68697 <at> debbugs.gnu.org
Received: via spool by 68697-submit <at> debbugs.gnu.org id=B68697.170619471510132
          (code B ref 68697); Thu, 25 Jan 2024 14:59:01 +0000
Received: (at 68697) by debbugs.gnu.org; 25 Jan 2024 14:58:35 +0000
Received: from localhost ([127.0.0.1]:48863 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1rT1Bb-0002dK-56
	for submit <at> debbugs.gnu.org; Thu, 25 Jan 2024 09:58:35 -0500
Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]:43221)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <nafiz.islam1001@HIDDEN>) id 1rT1BZ-0002d7-Ig
 for 68697 <at> debbugs.gnu.org; Thu, 25 Jan 2024 09:58:34 -0500
Received: by mail-ej1-x634.google.com with SMTP id
 a640c23a62f3a-a30e445602cso157876766b.0
 for <68697 <at> debbugs.gnu.org>; Thu, 25 Jan 2024 06:58:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1706194702; x=1706799502; darn=debbugs.gnu.org;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=LjDSJ9Yo1NM9qheo10VXqVYdSRmmGuDHbKJN9UN5gqc=;
 b=S3jBreMEC0+TSlfBtKLyMLuf92/r1eucPKj47OcHJJcJvoLCBK4Bb9YitW48SBr1D0
 RAi1z9GLiA5X7u9/O7IjOMTErZytALqAgeyHdflWuxpATXA4LkMWENw5bd9dAVcgugSp
 XI9Ac+NVypn3/+vvtrlZTM0GIcCC1kx2gCpb9ZoREkasH4WQnn6wD+Wt2/sDbFaDprtI
 wib6eQ+TrHQnIEeUca2LpQi2+5ME09OycpMDPlCcjxgKL0E8OY+a9IjUME2ZM0woBAc0
 DlXUaWfOGlfY6BR+EFzsCmSC7oFGQfhKrms3hBytlm1La6teldjkjDGEY0INupxXFJqP
 h61g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1706194702; x=1706799502;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
 :reply-to;
 bh=LjDSJ9Yo1NM9qheo10VXqVYdSRmmGuDHbKJN9UN5gqc=;
 b=ReydwNKwyp4OEGaj3UEr1qkwsB7sNc/h2Oxok1fLNUX5UKFeRS1Z++A9lTNycFhplr
 gfnA5MCVGb+z+gyXRwKB5naMko0pqNtPbm6JXz90M+tSHT0/6elb6YxTs0wGNfq/8DTX
 Ts8KGMzZu//JRDB4PCDkFahUvtbNZFS2reioLG612LpBNNVzQZlZ7I+Zq2Y5ypBtJiCh
 rYiYK5h9/j9RJYm+c6A1vSRA0V5yo3IzpXbpT8Umtu3YJkybYBA+nFBI5rE6dAhZ8i5Y
 Z8szEGo6oQ85NU13fmpHC5rTkYgfcw+KcqSRLmqNU2gd0yWYugiwfSNbbBKYo/dvFo4f
 8XAQ==
X-Gm-Message-State: AOJu0YwLU9yZ3O28aU0eEYa/c9u99AVCKwce3sdyByPaIW//cmxIBuSz
 sB947+BvSwQkHiX6akTBTXguw1xzk23y71AUnSJMujfUv8FeclkEM4e5TSbS5QZITyRnRMoTxZl
 Mp9uevvAUDga1aunA25SHeA+Flyk=
X-Google-Smtp-Source: AGHT+IHFFDR9b3owcY4KDk+f/aUXmyXLzioT5ueLlUw5oUzGgLXRGdMvAQ5FUcIdOllfvHzpqVcVAD/BFGu3W0xj6E8=
X-Received: by 2002:a17:906:b243:b0:a31:1469:4861 with SMTP id
 ce3-20020a170906b24300b00a3114694861mr1079597ejb.33.1706194701625; Thu, 25
 Jan 2024 06:58:21 -0800 (PST)
MIME-Version: 1.0
References: <CAKjtFcQAfzzO5gHOq1kORpJQ3dzz788KTW-j5jsCMjdaGqxxXg@HIDDEN>
 <86plxpdge5.fsf@HIDDEN>
In-Reply-To: <86plxpdge5.fsf@HIDDEN>
From: Nafiz Islam <nafiz.islam1001@HIDDEN>
Date: Thu, 25 Jan 2024 09:58:10 -0500
Message-ID: <CAKjtFcRL7V1sL8AJBLp3D9Lv6+xEfx02s82oV8_sofffT75HuQ@HIDDEN>
Content-Type: multipart/alternative; boundary="0000000000001bae94060fc66946"
X-Spam-Score: 0.2 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -0.8 (/)

--0000000000001bae94060fc66946
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM Eli Zaretskii <eliz@HIDDEN> wrote:

> > From: Nafiz Islam <nafiz.islam1001@HIDDEN>
> > 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 th=
e
> 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 th=
e
> 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.
>

--0000000000001bae94060fc66946
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Oh right, I can use compilation-buffer-name-function. My o=
nly issue is that it doesn&#39;t have enough context to generate a meaningf=
ul buffer name; it only takes a name-of-mode. A meaningful buffer name coul=
d consist of the regexp or the entire grep shell command.<br></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 25=
, 2024 at 2:24=E2=80=AFAM Eli Zaretskii &lt;<a href=3D"mailto:eliz@HIDDEN"=
>eliz@HIDDEN</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">&gt; From: Nafiz Islam &lt;<a href=3D"mailto:nafiz.islam1001@g=
mail.com" target=3D"_blank">nafiz.islam1001@HIDDEN</a>&gt;<br>
&gt; Date: Wed, 24 Jan 2024 15:16:12 -0500<br>
&gt; <br>
&gt; The way `grep&#39; and `vc-git-grep&#39; works right now is that it wi=
ll always output its result to a buffer called<br>
&gt; `*grep*&#39;. So, if I perform another `grep&#39; command, it will ove=
rwrite the previous grep result (unless I<br>
&gt; rename the buffer beforehand).<br>
&gt; <br>
&gt; I would like, at least, an option to create a new buffer each time a `=
grep&#39; command is executed.<br>
&gt; Maybe each new buffer could be given the name based on the regexp or t=
he grep shell command<br>
&gt; used.<br>
<br>
Did you try to define a compilation-buffer-name-function that would do<br>
what you want?=C2=A0 Such a function can produce any buffer name you want.<=
br>
</blockquote></div>

--0000000000001bae94060fc66946--

Last modified: Thu, 25 Jan 2024 15:00:02 UTC

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