From: Andrew Schwartzmeyer <andrew@schwartzmeyer.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 42101@debbugs.gnu.org
Subject: bug#42101: icomplete-fido-ret doesn't always use minibuffer-default when input is empty
Date: Sat, 25 Jul 2020 21:11:21 -0700 [thread overview]
Message-ID: <3151C929-A606-42FF-B839-C5A0239D4BEE@schwartzmeyer.com> (raw)
In-Reply-To: <CALDnm51Hqc0+imASYpAAJvCXQwSGwuVaHGAjjJkMecr-wmJ3Vw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
This bug can be fixed by deleting the expression:
,(lambda (comp)
(string-prefix-p minibuffer-default comp))
from icomplete--sorted-completions.
But it’s obviously there for some reason, so idk.
> On Jul 4, 2020, at 2:35 AM, João Távora <joaotavora@gmail.com> wrote:
>
> Schwartzmeyer <andrew@schwartzmeyer.com <mailto:andrew@schwartzmeyer.com>> wrote
>
> > Any clue?
>
> I'm sorry Andrew haven't had time to look into it yet, but your analyses help. Just note that Fido-mode is indeed geared primarily to working with flex. But it should be customizable of course.
>
> João
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
prev parent reply other threads:[~2020-07-26 4:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 5:59 bug#42101: icomplete-fido-ret doesn't always use minibuffer-default when input is empty Andrew Schwartzmeyer
2020-06-28 6:36 ` bug#42101: Andy Schwartzmeyer
[not found] ` <handler.42101.B.159332399316501.ack@debbugs.gnu.org>
2020-06-29 1:48 ` bug#42101: Acknowledgement (icomplete-fido-ret doesn't always use minibuffer-default when input is empty) Andrew Schwartzmeyer
2020-06-29 13:52 ` João Távora
2020-06-30 1:41 ` Richard Stallman
2020-06-29 14:00 ` bug#42101: icomplete-fido-ret doesn't always use minibuffer-default when input is empty João Távora
2020-07-04 5:22 ` Andrew Schwartzmeyer
[not found] ` <FDB51F0D-4611-4146-BA7A-6FD6AA566442@schwartzmeyer.com>
2020-07-04 9:35 ` João Távora
2020-07-26 4:11 ` Andrew Schwartzmeyer [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=3151C929-A606-42FF-B839-C5A0239D4BEE@schwartzmeyer.com \
--to=andrew@schwartzmeyer.com \
--cc=42101@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
/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.