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

Previous Next

Full log

View this message in rfc822 format

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

[Message part 1 (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 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.