GNU bug report logs - #57163
completing-read not allow cycling of the options by default

Previous Next

Full log

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

From: uzibalqa <uzibalqa <at> proton.me>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: michael_heerdegen <at> web.de, 57163 <at> debbugs.gnu.org
Subject: Re: bug#57163: completing-read not allow cycling of the options by
 default
Date: Sat, 13 Aug 2022 18:15:26 +0000

------- Original Message -------
On Saturday, August 13th, 2022 at 5:21 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:


> > Date: Sat, 13 Aug 2022 16:09:53 +0000
> > From: uzibalqa uzibalqa <at> proton.me
> > Cc: michael_heerdegen <at> web.de, 57163 <at> debbugs.gnu.org
> >
> > M-n and M-p work as you say. Have noticed that when one is using debug-on-error,
> > using M-n until the last option gives
> >
> > Debugger entered--Lisp error: (user-error "End of defaults; no next item")
> > signal(user-error ("End of defaults; no next item"))
> > user-error("End of defaults; no next item")
>
>
> Well, don't set debug-on-error, then.
>
> > After that, doing M-p gives [M-p is undefined]
>
>
> Because you are in the debugger, in recursive-edit. Type C-] to exit
> that.

Should it be a user-error though?  Is there any scheme to set another keybinding
for `M-n` and `M-p` for things like completing-read?  Being able to use [up] and
[down] would be both convenient and intuitive (particularly people who use packages
like company-mode), but cannot see that completing-read could allow that.

Previous Next

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