From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Lars Ingebrigtsen <larsi@gnus.org>,
43120@debbugs.gnu.org, 19032@debbugs.gnu.org,
Sean Whitton <spwhitton@spwhitton.name>
Subject: bug#19032: bug#43120: 28.0.50; fido-mode: M-j before completions appear selects wrong choice
Date: Wed, 9 Sep 2020 20:54:39 +0100 [thread overview]
Message-ID: <CALDnm52F_EMUOzLj48oTPopx73euRVHfCS1ixLb401eybjBj+Q@mail.gmail.com> (raw)
In-Reply-To: <jwvpn6uwwya.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On Wed, Sep 9, 2020 at 8:52 PM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> >>> Nope, sorry. You're right. It should read minibuffer-complete-and-exit
> there
> >>> of course.
> >> IIRC this depends on whether the completion is `require-match` or not.
> > If so, shouldn't minibuffer-complete-and-exit take care of that?
>
> Yes and no: IIRC depending on `require-match`, RET is bound either
> to `minibuffer-complete-and-exit` or to `exit-minibuffer`.
Bah, so the remap you suggested wouldn't work anyway. What to do?
The good 'ol :filter trick? How does it go again?
João
[-- Attachment #2: Type: text/html, Size: 992 bytes --]
next prev parent reply other threads:[~2020-09-09 19:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 21:00 bug#43120: 28.0.50; fido-mode: M-j before completions appear selects wrong choice Sean Whitton
2020-08-30 23:50 ` João Távora
2020-08-31 16:37 ` Sean Whitton
2020-09-01 14:16 ` Lars Ingebrigtsen
2020-09-01 18:27 ` João Távora
2020-09-03 12:40 ` João Távora
2020-09-03 13:11 ` Lars Ingebrigtsen
2020-09-03 13:13 ` João Távora
2020-09-03 13:51 ` Lars Ingebrigtsen
2020-09-03 13:55 ` João Távora
2020-09-01 14:19 ` Lars Ingebrigtsen
2020-09-03 23:23 ` Sean Whitton
2020-09-04 2:11 ` Lars Ingebrigtsen
2020-09-04 3:22 ` Sean Whitton
2020-09-04 3:27 ` Lars Ingebrigtsen
2020-09-04 14:47 ` Sean Whitton
2020-09-05 12:25 ` Lars Ingebrigtsen
2020-09-05 15:32 ` Sean Whitton
2020-09-05 21:12 ` Lars Ingebrigtsen
2020-09-06 18:26 ` bug#19032: " João Távora
2020-09-07 10:30 ` Lars Ingebrigtsen
2020-09-07 10:37 ` bug#19032: " João Távora
2020-09-07 11:43 ` Lars Ingebrigtsen
2020-09-07 17:30 ` Stefan Monnier
2020-09-08 6:52 ` João Távora
2020-09-08 8:59 ` bug#19032: " João Távora
2020-09-09 14:01 ` OGAWA Hirofumi
2020-09-09 16:11 ` bug#19032: " João Távora
2020-09-09 17:52 ` Stefan Monnier
2020-09-09 19:13 ` bug#19032: " João Távora
2020-09-09 19:52 ` Stefan Monnier
2020-09-09 19:54 ` João Távora [this message]
2020-09-09 19:57 ` João Távora
2020-09-09 20:35 ` bug#19032: " Stefan Monnier
2020-09-09 22:08 ` João Távora
2020-09-10 4:36 ` Stefan Monnier
2020-09-10 18:51 ` bug#19032: " Juri Linkov
2020-09-10 19:15 ` João Távora
2020-09-09 18:58 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALDnm52F_EMUOzLj48oTPopx73euRVHfCS1ixLb401eybjBj+Q@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=19032@debbugs.gnu.org \
--cc=43120@debbugs.gnu.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=spwhitton@spwhitton.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).