From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Philip Kaludercic <philipk@posteo.net>
Cc: "54374@debbugs.gnu.org" <54374@debbugs.gnu.org>
Subject: bug#54374: [External] : bug#54374: 29.0.50; previous-completion fails at beginning of completions buffer
Date: Mon, 14 Mar 2022 15:21:10 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488BFB3EB3476EBE924FF8EF30F9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86bky99c7r.fsf@mail.linkov.net>
> when point is at the beginning of the completion buffer,
> then previous-completion switches to the minibuffer.
Not good. Keys that cycle among completions should
do exactly that. And they should wrap around, at
least by default (with a user option to not do that).
If point is at bob then backward cycling should move
to the last completion.
> But if point is at the first completion, then previous-completion wraps
> to the last completion. Shouldn't point at the beginning of the buffer
> wrap to the last completion as well?
Of course it should. If point is there or at any
place before the first completion then backward
cycling should wrap around to the last completion.
prev parent reply other threads:[~2022-03-14 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 17:39 bug#54374: 29.0.50; previous-completion fails at beginning of completions buffer Juri Linkov
2022-03-13 20:39 ` Philip Kaludercic
2022-03-14 3:22 ` Eli Zaretskii
2022-03-14 8:20 ` Philip Kaludercic
2022-03-14 12:59 ` Eli Zaretskii
2022-03-14 13:34 ` Philip Kaludercic
2022-03-14 8:35 ` Andreas Schwab
2022-03-14 8:30 ` Juri Linkov
2022-03-14 14:12 ` Philip Kaludercic
2022-03-14 18:24 ` Juri Linkov
2022-03-18 21:49 ` Philip Kaludercic
2022-03-19 19:13 ` Juri Linkov
2022-05-24 19:12 ` Juri Linkov
2022-05-26 16:26 ` Juri Linkov
2022-05-27 16:13 ` Juri Linkov
2022-03-24 18:11 ` Juri Linkov
2022-03-14 15:21 ` Drew Adams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB5488BFB3EB3476EBE924FF8EF30F9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=54374@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.