GNU bug report logs - #77732
grep-edit-buffer errors with incionsistent behaviour

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#77732: closed (grep-edit-buffer errors with incionsistent
 behaviour)
Date: Sat, 26 Apr 2025 12:38:02 +0000

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

Your message dated Sat, 26 Apr 2025 15:37:11 +0300
with message-id <86v7qrt7yg.fsf <at> gnu.org>
and subject line Re: bug#77732: grep-edit-buffer errors with incionsistent behaviour
has caused the debbugs.gnu.org bug report #77732,
regarding grep-edit-buffer errors with incionsistent behaviour
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
77732: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=77732
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Johann Höchtl <johann.hoechtl <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: grep-edit-buffer errors with incionsistent behaviour
Date: Fri, 11 Apr 2025 11:33:59 +0200

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

I am using Emacs from HEAD on Windows

I tried to reproduce the behaviour with emacs -Q but it still remains
inconsistent.

When I rgrep and there are few results (< 15) , I can enter grep buffer
pres 'e' to enter grep-edit mode, get out of it with C-c C-c, re-enter with
'e' and so on.

When there are more results, (between 15 and 70)  I still can enter with
'e' get out with C-c C-c but when I try to re-enter I get the error message
Wrong type argument: stringp, nil
The buffer later although still in grp-mode does not behave any longer as a
grep mode, 'g' or 'e' results in the error Buffer is read only : #<buffer
*grep*>

When there are many results, I get the error message Wrong type argument:
stringp, nil already on the first invocation attempt.

Thew boundaries are somewhat moving but at least I have the feeling the
more matches are, the more frequently I run into the

Wrong type argument: stringp, nil

already at first try.

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

[Message part 5 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Johann Höchtl <johann.hoechtl <at> gmail.com>
Cc: 77732-done <at> debbugs.gnu.org, visuweshm <at> gmail.com, ultrono <at> gmail.com
Subject: Re: bug#77732: grep-edit-buffer errors with incionsistent behaviour
Date: Sat, 26 Apr 2025 15:37:11 +0300

> From: Johann Höchtl <johann.hoechtl <at> gmail.com>
> Date: Wed, 23 Apr 2025 11:08:22 +0200
> Cc: Eli Zaretskii <eliz <at> gnu.org>, visuweshm <at> gmail.com, 77732 <at> debbugs.gnu.org
> 
> Am Di., 22. Apr. 2025 um 17:52 Uhr schrieb Paul Nelson <ultrono <at> gmail.com>:
> 
>  Try opening the new grep.el, C-c C-e in the buffer, then C-x C-e with point after the "defvar
>  grep-compilation-transform-finished-rules" form
> 
> That worked
> I did some tests with few matches, many matches 
> For my use-cases this fixes the bug.

Thanks, I've now installed this on the master branch, and I'm closing
this bug.

Previous Next

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