unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@ORACLE.COM>
To: <rms@gnu.org>, <9598@debbugs.gnu.org>
Subject: bug#9598: 24.0.50; completion goes too far
Date: Sun, 25 Sep 2011 11:47:46 -0700	[thread overview]
Message-ID: <5D4CCB828585430D8AB4FD61EAEAC5C0@us.oracle.com> (raw)
In-Reply-To: <E1R7saj-00020h-QX@fencepost.gnu.org>

> This is totally surprising and unhelpful.
> ...and did not mention *mail* at all.  That is confusing
> and unhelpful too...
> 
> I surmise it is treating the input as a wildcard pattern.
> I think that is a misguided feature.  The *'s should be
> treated literally.  And the current buffer should not be
> excluded from a completion list, when a completion list is displayed.

1+

Yes, the default matching uses wildcard patterns.  In fact, the default matching
uses several different matching schemes, in sequence, until one of them results
in matches.

See my reply to your post today about bug #9591.

And we have been over this before[*].  People, including you, have pointed out
the user-oriented problems with this UI design, but Stefan really wants it this
way.  So you and other users will continue to be surprised.


[*] I cannot find appropriate emacs-devel threads to cite here, because it is
impossible to search at http://lists.gnu.org/archive/html/emacs-devel/ etc. for
`+from:rms@gnu.org', because of too many hits.  That limitation sounds
reasonable at first, until you realize that you cannot even combine such a
filter by ANDing it with a small set of hits from another pattern - e.g.
`:subject:complet' (regardless of AND order).  Similarly, I couldn't find a way
to search at http://debbugs.gnu.org/ for bug-list postings (not submittals) from
rms@gnu.org with subject-line matches.  Poor GNU.






  reply	other threads:[~2011-09-25 18:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-25 17:34 bug#9598: 24.0.50; completion goes too far Richard Stallman
2011-09-25 18:47 ` Drew Adams [this message]
2011-09-26  1:00   ` Richard Stallman
2011-09-26  1:53     ` Drew Adams
2011-09-26  6:09     ` Eli Zaretskii
2011-09-26 10:42       ` Richard Stallman
2011-09-26 11:34         ` Eli Zaretskii
2011-09-26 21:12           ` Richard Stallman
2022-02-06  0:05             ` bug#12916: 24.2; Completion for "C-x b" does not include current buffer Lars Ingebrigtsen
2011-09-26  2:45 ` bug#9598: 24.0.50; completion goes too far Stefan Monnier
2011-09-26 10:42   ` Richard Stallman
2011-09-27  2:25     ` Stefan Monnier
2011-09-27 16:34       ` Richard Stallman
2011-10-11  2:52         ` Stefan Monnier
2011-10-11 22:01           ` Richard Stallman
2016-01-31 14:30 ` bug#9598: Status: C-x b completion should also display current buffer Marcin Borkowski
2016-01-31 16:18   ` bug#12916: " Drew Adams
2016-01-31 16:56   ` Eli Zaretskii

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=5D4CCB828585430D8AB4FD61EAEAC5C0@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=9598@debbugs.gnu.org \
    --cc=rms@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).