unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: Stephen Berman <stephen.berman@gmx.net>,
	hx <silent2600@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: emacs 29 expand command in minibuf
Date: Sat, 18 Jun 2022 09:37:07 +0200	[thread overview]
Message-ID: <87v8syquog.fsf@gnu.org> (raw)
In-Reply-To: <868rpvaqdr.fsf@stephe-leake.org>

Stephen Leake <stephen_leake@stephe-leake.org> writes:

>> I think the real problem is that after `M-x em-v TAB' expands the
>> input to "emacs-v", typing TAB again completes it to "emacs-version"
>> instead of popping up a *Completions* buffer containing both
>> "emacs-news-view-mode" and "emacs-version".
>
> +1
>
> This behavior (on different but similar cases) bytes me quite often.

Indeed, that looks at least surprising.  When you do em-v<TAB> the basic
completion style cannot do anything and so the partial-completion style
completes to emacs-v which is the common prefix of both emacs-version
and emacs-news-view-mode for this style.  But when doing emacs-v<TAB>
afterwards, the basic style can complete and only to emacs-version.

Maybe there should be a way to "lock in" a completion style, i.e., when
a more fuzzy style has computed completions in a previous step, it
should not fall back to a more strict one later in the process.  Now of
course, there are more completion-styles than those in vanilla so the
level of fuzzyness is not known for all...

Bye,
Tassilo



  reply	other threads:[~2022-06-18  7:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13  1:48 emacs 29 expand command in minibuf hx
2022-06-13  4:57 ` Tassilo Horn
2022-06-13 11:06   ` Stephen Berman
2022-06-17 22:15     ` Stephen Leake
2022-06-18  7:37       ` Tassilo Horn [this message]
2022-06-18  7:58         ` Andreas Schwab
2022-06-18  8:32           ` Stephen Berman
2022-06-21 14:39             ` Andreas Schwab
2022-06-18 13:30           ` Stefan Monnier
2022-06-21 20:31         ` Stefan Monnier
2022-06-21 20:56           ` [External] : " Drew Adams
2022-06-18  8:39 ` Andreas Röhler

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=87v8syquog.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=silent2600@gmail.com \
    --cc=stephen.berman@gmx.net \
    --cc=stephen_leake@stephe-leake.org \
    /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).