From: Drew Adams <drew.adams@oracle.com>
To: MickeyFerguson@alumni.cmu.edu,
"Emacs Help (help-gnu-emacs@gnu.org)" <help-gnu-emacs@gnu.org>
Subject: RE: buffer name selection not case sensitive
Date: Wed, 18 Sep 2013 11:08:59 -0700 (PDT) [thread overview]
Message-ID: <d2fae1ee-5680-45ee-b370-f7dca9cbdf28@default> (raw)
In-Reply-To: <B67C92F68785104E8816FEEE2B44C9344E139DB1@TEMCAS01.peinet.peinc.com>
> I'm now using emacs 24.3.1 for Windows. With the old version I was using
> (21.x?), when I went to switch to another buffer (C-x b), I could type the
> name of the buffer in lower case and it would find it even if the buffer
> name was in upper or mixed case. Now it doesn't find it unless I get the
> case correct. Is there a way to change it so that the buffer name matching
> is case insensitive?
You can customize option `read-buffer-completion-ignore-case' to non-nil.
prev parent reply other threads:[~2013-09-18 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 18:06 buffer name selection not case sensitive Mickey Ferguson
2013-09-18 18:08 ` Drew Adams [this message]
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=d2fae1ee-5680-45ee-b370-f7dca9cbdf28@default \
--to=drew.adams@oracle.com \
--cc=MickeyFerguson@alumni.cmu.edu \
--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).