unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68022@debbugs.gnu.org
Subject: bug#68022: 30.0.50; File cache completions accumulate instead of replacing minibuffer input
Date: Mon, 25 Dec 2023 14:47:52 +0100	[thread overview]
Message-ID: <m1jzp2xuk7.fsf@dazzs-mbp.home> (raw)
In-Reply-To: <8334vqbge3.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 25 Dec 2023 14:44:52 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Mon, 25 Dec 2023 07:54:22 +0100
>> From:  Eshel Yaron
>>
>> With emacs -Q:
>>
>> 1. M-x file-cache-add-directory-using-find /path/to/emacs/
>> 2. C-x C-f mini C-TAB
>> 3. Observe the *Completions* buffer pop up with file cache
>> completions, suggesting as usual to "type M-<down> or M-<up> to move
>> point between completions."
>> 4. M-<down> M-<down> M-<up> ...
>> 5. Each candidate you highlight this way is inserted in the minibuffer
>> after the current input, instead of replacing the appropriate part of
>> the input.
>>
>> I see this already in Emacs 29.1, FWIW.
>
> Something is missing in the recipe above, because I get "No match"
> when I press C-TAB in step 2.  What did I miss?

Hmm, I'm not sure.  Perhaps `file-cache-add-directory-using-find` didn't
do its job for some reason?  The point is just to add a bunch of file
names to the cache.

> Is the above supposed to work in any Emacs source tree?  Also, what
> should be the default-directory in step 1 (if it's important) --
> should it be the root of the Emacs source tree?

That shouldn't matter, I think, as long as you have several files with
"mini" in their names in the cache.  Any other invocation of `C-TAB`
that pops the *Completions* buffer should show the same behavior AFAICT.







  reply	other threads:[~2023-12-25 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25  6:54 bug#68022: 30.0.50; File cache completions accumulate instead of replacing minibuffer input Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-25 12:44 ` Eli Zaretskii
2023-12-25 13:47   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-25 15:05     ` Eli Zaretskii
2023-12-25 15:41       ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-25 16:50         ` Eli Zaretskii
2023-12-25 17:35           ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=m1jzp2xuk7.fsf@dazzs-mbp.home \
    --to=bug-gnu-emacs@gnu.org \
    --cc=68022@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=me@eshelyaron.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 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).