all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, 9591@debbugs.gnu.org
Subject: bug#9591: 24.0.50; buffer name completion
Date: Fri, 30 Sep 2011 09:42:46 +0300	[thread overview]
Message-ID: <83bou2edjt.fsf@gnu.org> (raw)
In-Reply-To: <jwv8vp7ui7y.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 29 Sep 2011 18:02:25 -0400
> Cc: rms@gnu.org, 9591@debbugs.gnu.org
> 
> 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.

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 ;-)

> confirm-nonexistent-file-or-buffer already found resistance when
> I introduced it

I don't understand the resistance: that feature saved my a$$ a few
times, when my fingers were faster than my brain.





  parent reply	other threads:[~2011-09-30  6:42 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 [this message]
2011-09-30 19:39       ` Stefan Monnier
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bou2edjt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9591@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.