From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 34116@debbugs.gnu.org
Subject: bug#34116: 27.0.50; minibuffer-force-complete-and-exit mostly broken
Date: Fri, 18 Jan 2019 22:18:22 +0000 [thread overview]
Message-ID: <87tvi5pq35.fsf@gmail.com> (raw)
In-Reply-To: <jwvva2lalue.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Fri, 18 Jan 2019 13:00:35 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Yes, it elegantly fixes this bug, but complicates #34077.
>
> I don't see why. Can you explain?
If I do that, then C-M-i will still cycle/rotate after completing say,
'/emacs/sr' to '/emacs/src', which means that
completion-all-sorted-completions, used by the prospects, listing is
still forcibly cached by minibuffer-force-complete.
The reason it shouldn't be, IMO, is that the result is I will now see
'{src | libsrc}' as candidates, instead of seeing the files under
emacs/src/. The problem is really that now I can't know if those are
actual dirs emacs/src/src emacs/src/libsrc.
You could argue that's just my personal preference and the cycling still
makes sense, so I put this new behaviour is a separate command
icomplete-force-complete as a compromise. But with your technique I
can't implement it properly.
João
next prev parent reply other threads:[~2019-01-18 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 13:56 bug#34116: 27.0.50; minibuffer-force-complete-and-exit mostly broken João Távora
2019-01-17 14:57 ` Stefan Monnier
2019-01-17 15:03 ` João Távora
2019-01-18 12:13 ` João Távora
2019-01-18 13:09 ` Stefan Monnier
2019-01-18 13:28 ` João Távora
2019-01-18 18:00 ` Stefan Monnier
2019-01-18 22:18 ` João Távora [this message]
2019-01-19 2:31 ` Stefan Monnier
2019-01-23 15:49 ` João Távora
2019-01-23 16:09 ` Stefan Monnier
2019-01-23 16:36 ` bug#34077: " João Távora
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=87tvi5pq35.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=34116@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).