From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 9591@debbugs.gnu.org
Subject: bug#9591: 24.0.50; buffer name completion
Date: Fri, 30 Sep 2011 15:39:32 -0400 [thread overview]
Message-ID: <jwv7h4pu8rx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83bou2edjt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Sep 2011 09:42:46 +0300")
>> Having looked a bit more into it, I'm undecided:
>> we could go like you suggest and force users to type a leading space,
>> but at least for my own use this would be inconvenient, since I pretty
>> often need to get at hidden buffers, and often don't know the exact name
>> of the buffer I want (and I don't even always know whether it's a hidden
>> buffer or not, since Elisp authors aren't always very consistent about
>> it). So I find it very handy to just say "C-x b *foo TAB" (or indeed
>> just "C-x b foo TAB" in Emacs-24) and see all buffers that contain
>> "foo", regardless of whether they're hidden or not.
>> So it seems that both behaviors are desirable and I'm not sure how to
>> tell which to use when.
> There's what Lars suggested, which sounds like it can cater to both
> use cases.
[ Going back to re-read it. ]
Ah, now I see what he meant.
I guess we could provide an ad-hoc completion style for buffers, but
that's kind of ugly: completion styles are supposed to be agnostic to the
underlying completion table and vice-versa.
> Failing that, add some non-default completion style which behaves like
> you want. I hope _you_ have no problems with customizing for
> non-default behavior ;-)
Indeed, I don't have a problem with that, tho I always prefer a solution
where no configuration is necessary (i.e. find a middle ground).
Stefan
next prev parent reply other threads:[~2011-09-30 19:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 12:28 bug#9591: 24.0.50; buffer name completion Richard Stallman
2011-09-24 18:44 ` Chong Yidong
2011-09-24 23:52 ` Richard Stallman
2011-09-25 0:19 ` Lars Magne Ingebrigtsen
2011-09-25 8:35 ` Andreas Schwab
2011-09-25 17:34 ` Richard Stallman
2011-09-25 17:52 ` Lars Magne Ingebrigtsen
2011-09-26 1:00 ` Richard Stallman
2011-09-25 18:45 ` Drew Adams
2011-09-25 1:04 ` Chong Yidong
2011-09-25 17:34 ` Richard Stallman
2011-09-29 22:02 ` Stefan Monnier
2011-09-29 22:39 ` Lars Ingebrigtsen
2011-09-30 21:03 ` Richard Stallman
2011-09-30 6:42 ` Eli Zaretskii
2011-09-30 19:39 ` Stefan Monnier [this message]
2011-10-01 14:05 ` Richard Stallman
2011-10-01 14:15 ` Eli Zaretskii
2011-10-01 20:54 ` Richard Stallman
2011-10-02 0:27 ` Stefan Monnier
2011-09-26 1:18 ` Stefan Monnier
2011-09-26 5:35 ` Eli Zaretskii
2011-09-26 7:56 ` Stephen Berman
2011-09-26 8:42 ` Eli Zaretskii
2011-09-27 17:45 ` Drew Adams
2011-09-27 18:52 ` 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=jwv7h4pu8rx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9591@debbugs.gnu.org \
--cc=eliz@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).