unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bug Emacs 21.3: write-file downcasing
Date: 11 Feb 2003 23:02:43 +0000	[thread overview]
Message-ID: <m2lm0ma0a4.fsf@nyaumo.jasonr.f2s.com> (raw)
In-Reply-To: <m3znp2sway.fsf@cicero.benny.turtle-trading.net>

Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de> writes:

> As I see it, it's not a question of OS but of supported file systems
> these days.

I am not aware of any standard way to find out whether a file-system
is case-sensitive or not, and the standard Linux kernel drivers for
FAT and SMB based filesystems are case-sensitive even though the
underlying filesystem is case-insensitive (although patches are
available to make the drivers case insensitive where applications do
not prevent it).  So yes, unfortunately it is a question of OS these
days.

  reply	other threads:[~2003-02-11 23:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  5:38 Bug Emacs 21.3: write-file downcasing Dhruva Krishnamurthy
2003-02-07  8:07 ` Juanma Barranquero
2003-02-07 15:23   ` Eli Zaretskii
2003-02-07 15:50     ` Juanma Barranquero
2003-02-07 17:16       ` Eli Zaretskii
2003-02-07 17:33         ` Juanma Barranquero
2003-02-07 17:57           ` Stefan Monnier
2003-02-07 18:19             ` Eli Zaretskii
2003-02-09 12:39               ` Richard Stallman
2003-02-09 15:52                 ` Eli Zaretskii
2003-02-10  4:41                   ` Dhruva Krishnamurthy
2003-02-10  5:46                     ` Eli Zaretskii
2003-02-10 10:03                       ` Dhruva Krishnamurthy
2003-02-10  8:21                     ` Jason Rumney
2003-02-10 10:44                       ` Juanma Barranquero
     [not found]               ` <m2smuxcwba.fsf@primate.xs4all.nl>
2003-02-10 22:39                 ` Richard Stallman
2003-02-10 22:52                   ` Andreas Schwab
2003-02-11 22:25                     ` Richard Stallman
2003-02-12  8:28                       ` Jason Rumney
2003-02-12 10:26                         ` Kim F. Storm
2003-02-12 19:36                           ` Jason Rumney
2003-02-12 17:50                         ` Kevin Rodgers
2003-02-12 22:19                           ` Andreas Schwab
2003-02-14 22:29                             ` Kevin Rodgers
2003-02-11 14:53                   ` Benjamin Riefenstahl
2003-02-11 23:02                     ` Jason Rumney [this message]
2003-02-12 13:37                       ` Benjamin Riefenstahl
2003-02-12 13:49                         ` Andreas Schwab
2003-02-12 14:57                           ` Benjamin Riefenstahl
2003-02-12 19:40                         ` Jason Rumney
2003-02-07 18:18           ` Eli Zaretskii
2003-02-07 20:19             ` Juanma Barranquero
2003-02-07 23:03               ` Eli Zaretskii
2003-02-07 18:31         ` Jason Rumney

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=m2lm0ma0a4.fsf@nyaumo.jasonr.f2s.com \
    --to=jasonr@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).