From: Ivan <ivannedr@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: switch-to-EXISTING-buffer
Date: Wed, 7 Jan 2009 01:33:44 -0800 (PST) [thread overview]
Message-ID: <95aff5c3-4c3e-4c29-95b4-297608643d39@g1g2000pra.googlegroups.com> (raw)
switch-to-buffer will on a unknown buffer create a new buffer. But for
my use I usually want an existing buffer. It would save me time and
frustration to make a simple enter try to autocomplete the rest of the
buffer name.
Does such a functionality exist?
next reply other threads:[~2009-01-07 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 9:33 Ivan [this message]
2009-01-07 10:15 ` switch-to-EXISTING-buffer Peter Dyballa
2009-01-07 10:21 ` switch-to-EXISTING-buffer Sven Bretfeld
2009-01-07 10:29 ` switch-to-EXISTING-buffer Xavier
2009-01-07 13:21 ` switch-to-EXISTING-buffer Ivan
2009-01-07 17:38 ` switch-to-EXISTING-buffer B. T. Raven
2009-01-08 12:02 ` switch-to-EXISTING-buffer Ivan
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=95aff5c3-4c3e-4c29-95b4-297608643d39@g1g2000pra.googlegroups.com \
--to=ivannedr@gmail.com \
--cc=help-gnu-emacs@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.
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).