GNU bug report logs - #78916
31.0.50; C-g fails to exit loop

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> protonmail.com>
Cc: 78916 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, kupfer <at> rawbw.com
Subject: bug#78916: 31.0.50; C-g fails to exit loop
Date: Sat, 05 Jul 2025 12:47:57 +0300

> Date: Sat, 05 Jul 2025 08:17:23 +0000
> From: Pip Cet <pipcet <at> protonmail.com>
> Cc: monnier <at> iro.umontreal.ca, 78916 <at> debbugs.gnu.org, kupfer <at> rawbw.com
> 
> "Eli Zaretskii" <eliz <at> gnu.org> writes:
> 
> >> Date: Fri, 04 Jul 2025 18:16:29 +0000
> >> From: Pip Cet <pipcet <at> protonmail.com>
> >> Cc: Eli Zaretskii <eliz <at> gnu.org>, 78916 <at> debbugs.gnu.org, kupfer <at> rawbw.com
> >>
> >> "Stefan Monnier" <monnier <at> iro.umontreal.ca> writes:
> >>
> >> >> (However, there are other good reason not to apply this patch, and
> >> >> simply fix read-key to optionally allow quitting instead.
> >> >
> >> > That wouldn't fix the `C-]` case.
> >>
> >> I'm not sure it's that important.  It's not documented in
> >> query-replace-help, and I'm not really sure whether it should behave
> >> like C-g or ESC (or should ESC be fixed, too?) or any unbound key (like
> >> "r").
> 
> > C-] is documented in the manual as part of this catch-all:
> 
> >      Aside from this, any other character exits the ‘query-replace’, and
> >   is then reread as part of a key sequence.  Thus, if you type ‘C-k’, it
> >   exits the ‘query-replace’ and then kills to end of line.  In particular,
> >   ‘C-g’ simply exits the ‘query-replace’.
> 
> That is no longer accurate if we apply Stefan's fix, which will prevent
> C-] from being reread over and over again in Mike's loop.

Which is why I suggested to augment that.

> The last sentence contradicts the rest of it, too: if C-g is reread,
> it doesn't simply exit the 'query-replace'.

When we know what change we will install and how it will affect C-g,
we can make that part more accurate.

> So the documentation in the manual is contradictory and inaccurate, and
> the documentation in query-replace-help is incomplete.

Are you talking about the documentation on the release branch (and the
behavior on that branch), or are you talking about the master branch?
If the latter, then this discussion is precisely how to make the code
behave like the documentation used to say.

Previous Next

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