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

Previous Next

Full log

View this message in rfc822 format

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: bug#57163: completing-read not allow cycling of the options by default
Date: Sat, 13 Aug 2022 18:28:52 +0000

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


> > Date: Sat, 13 Aug 2022 18:15:26 +0000
> > From: uzibalqa uzibalqa <at> proton.me
> > Cc: michael_heerdegen <at> web.de, 57163 <at> debbugs.gnu.org
> >
> > > > 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?
>
>
> A low-level API such as completing-read has no business in deciding
> which errors are user-errors and which aren't. That's for the calling
> application to decide.
>
> > 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.
>
>
> <UP> and <DOWN> arrow keys work here, they do the same as M-p and M-n.
>

Cannot see <UP> and <DOWN> arrow keys described in "8.1 Using the Minibuffer" or after that.

Previous Next

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