From: Bruza <benruza@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Configure case insensitive filename auto-complete
Date: Tue, 25 Dec 2007 01:01:01 -0800 (PST) [thread overview]
Message-ID: <a4132fbf-3d78-4b04-9ffe-4de7e5ab09b4@a35g2000prf.googlegroups.com> (raw)
In-Reply-To: 87wsr4783c.fsf@gmx.de
On Dec 24, 1:30 am, Sven Joachim <svenj...@gmx.de> wrote:
> On 2007-12-24 09:57 +0100, Bruza wrote:
>
> > Is there a way to make my min-buffer filename auto-complete case
> > sensitive? I personally think it's really annoying having to remember
> > the case of the first letter of your file (is it "MySQL.txt" or
> > "mysql.txt"??) when using filename auto-complete search. After all,
> > the auto-complete is meant to help you so that you don't have to
> > remember exactly what the filename is...
>
> Set read-file-name-completion-ignore-case to t.
>
> Sven
Sven,
It works! Thanks a lot :-)...
Ben
prev parent reply other threads:[~2007-12-25 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 8:57 Configure case insensitive filename auto-complete Bruza
2007-12-24 9:30 ` Sven Joachim
2007-12-25 9:01 ` Bruza [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=a4132fbf-3d78-4b04-9ffe-4de7e5ab09b4@a35g2000prf.googlegroups.com \
--to=benruza@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).