From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22300@debbugs.gnu.org, jwiegley@gmail.com, esq@lawlist.com
Subject: bug#22300: 25.1.50; Dired -- renaming folders/files to CamelCase/UPPERCASE/lowercase.
Date: Mon, 4 Jan 2016 08:15:19 -0800 (PST) [thread overview]
Message-ID: <c0d60d98-3525-4ec7-9844-1a249c0db5d0@default> (raw)
In-Reply-To: <83twmt73g6.fsf@gnu.org>
> > Okay. But (1) he _is_ able to do it using `mv foo Foo', and
> > (2) MS Windows is also case-insensitive for files and folders,
> > and I can easily use `R' to rename a directory `foo' to `FOO',
> > and vice versa. (Emacs asks me to confirm that I want to rename,
> > but that's all.)
>
> For some value of "easily", yes. On the C source level, Emacs works
> very hard (a.k.a. "jumps through hoops") to allow you doing that
> easily, and it does that only for MS-Windows and MS-DOS, whose
> filesystems are known to be case-insensitive. OS X doesn't have that
> privilege.
Ah, so that's the bug, then. Emacs does not know that OS X is
case-insensitive and it doesn't have code to special-case it as it
does for MS Windows.
> If OS X filesystems are always case-insensitive, perhaps the same code
> should also be compiled on that system. If some of OS X filesystems
> are case-sensitive, we can only do that if Emacs can know which one is
> it.
That sounds right to me.
next prev parent reply other threads:[~2016-01-04 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 20:57 bug#22300: 25.1.50; Dired -- renaming folders/files to CamelCase/UPPERCASE/lowercase Keith David Bershatsky
2016-01-03 21:10 ` John Wiegley
2016-01-04 0:47 ` Drew Adams
2016-01-04 1:11 ` John Wiegley
2016-01-04 1:37 ` Drew Adams
2016-01-04 15:46 ` Eli Zaretskii
2016-01-04 16:15 ` Drew Adams [this message]
2016-01-04 19:22 ` John Wiegley
2016-01-04 19:27 ` Drew Adams
2016-01-04 19:45 ` Eli Zaretskii
2016-01-04 19:44 ` Eli Zaretskii
2016-01-04 19:48 ` John Wiegley
2016-01-04 20:31 ` Eli Zaretskii
2016-01-04 15:44 ` Eli Zaretskii
2016-01-04 3:31 ` Eli Zaretskii
2016-01-04 4:19 ` Keith David Bershatsky
2016-01-04 15:50 ` Eli Zaretskii
2016-01-04 17:41 ` Keith David Bershatsky
2016-01-04 19:12 ` Eli Zaretskii
2016-01-04 19:45 ` Keith David Bershatsky
2016-01-04 20:24 ` Eli Zaretskii
2016-01-04 20:51 ` Keith David Bershatsky
2016-01-05 16:46 ` Eli Zaretskii
2016-01-05 17:27 ` Keith David Bershatsky
2016-01-05 18:28 ` Eli Zaretskii
2016-01-06 3:56 ` Keith David Bershatsky
2016-01-06 15:40 ` Eli Zaretskii
2016-01-06 19:57 ` Keith David Bershatsky
[not found] <<m2a8oml6tk.wl%esq@lawlist.com>
[not found] ` <<m24meutlmk.fsf@newartisans.com>
[not found] ` <<a936bee4-3375-45cf-ab35-62e36a21f003@default>
[not found] ` <<83vb7973iy.fsf@gnu.org>
2016-01-04 16:14 ` Drew Adams
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=c0d60d98-3525-4ec7-9844-1a249c0db5d0@default \
--to=drew.adams@oracle.com \
--cc=22300@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=esq@lawlist.com \
--cc=jwiegley@gmail.com \
/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).