unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Tassilo Horn <tsdh@gnu.org>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
	Stephen Berman <stephen.berman@gmx.net>,
	hx <silent2600@gmail.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: emacs 29 expand command in minibuf
Date: Tue, 21 Jun 2022 20:56:03 +0000	[thread overview]
Message-ID: <SJ0PR10MB54882CD13EC57E69F69B32DFF3B39@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <jwva6a5u5r4.fsf-monnier+emacs@gnu.org>

This is all a fundamental problem with the design,
which is to always fall back from one style to
another continuing to try to find a completion.

What's needed is to easily be able to choose one
or another style - during completion.

It's important to be able to know whether a given
style matches a candidate.  You may or you may not
want to try another style if the matches for one
style don't give you what you want/expect.

Better than that (being able to choose one style
at a time, on the fly) is to let you choose (again,
during completion) one or another such fallback 
list of styles.  Of course, that includes the case
of singleton fallback lists: one style at a time.

I argued for this decades ago.  And it's what
Icicles offers.

The choice to go with just one list of fallback
styles (per invocation or category of completion)
is, I think, based on the assumption that you
always want to maximize the possibility of getting
a match.  And that's far from the case, in many
contexts.



  reply	other threads:[~2022-06-21 20:56 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
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           ` Drew Adams [this message]
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=SJ0PR10MB54882CD13EC57E69F69B32DFF3B39@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=silent2600@gmail.com \
    --cc=stephen.berman@gmx.net \
    --cc=stephen_leake@stephe-leake.org \
    --cc=tsdh@gnu.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).