unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Paul Wallington <jpw@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: add read-file-name-completion-ignore-case user variable ?
Date: 25 Jun 2004 11:28:53 +0100	[thread overview]
Message-ID: <dgsmckq6ca.fsf@filth.shootybangbang.com> (raw)
In-Reply-To: <x5zn6svv9p.fsf@lola.goethe.zz> (message from David Kastrup on 25 Jun 2004 11:31:30 +0200)

> > > How about having a `read-file-name-completion-ignore-case' user
> > > variable rather than hard-coding a value according to system type?
> > > We could still set its default value according to system type.
> > 
> > Which your change does not seem to do.

Yeah.  I think this would be a neat feature to add but am not sure
whether the default value should be t for any system type.
 
> Anyway, I am not sure this is the right approach.  After all, case
> insensitivity is not as much an operating system, but a file system
> feature.  When doing file name completion on a Windows partition
> mounted on a typical Linux root file system, the "natural" behavior
> would be case sensitive completion in the path components up to the
> mount point, and case insensitive after that.

As you note, case insensitivity doesn't map cleanly to system type.
For example, Mac OS X's standard filesystem HFS+ is case-insensitive
whilst preserving the case of filenames but it can use traditional
case-sensitive UFS instead/as well and it supports NFS too.

Also, rhe users' preference for case sensitivity/insensitivity in
completions when reading a file name need not correspond to the
characteristics of particular filesystems.

  reply	other threads:[~2004-06-25 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 22:24 add read-file-name-completion-ignore-case user variable ? John Paul Wallington
2004-06-25  9:20 ` David Kastrup
2004-06-25  9:31   ` David Kastrup
2004-06-25 10:28     ` John Paul Wallington [this message]
2004-07-04  3:55 ` John Paul Wallington
2004-07-04 17:47   ` Steven Tamm

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=dgsmckq6ca.fsf@filth.shootybangbang.com \
    --to=jpw@gnu.org \
    --cc=emacs-devel@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).