From: Andreas Schwab <schwab@suse.de>
To: Brady Trainor <brady@bradyt.com>
Cc: 24441@debbugs.gnu.org
Subject: bug#24441: 24.5; rename directory in dired to change case
Date: Thu, 15 Sep 2016 11:28:25 +0200 [thread overview]
Message-ID: <mvmeg4la4w6.fsf@hawking.suse.de> (raw)
In-Reply-To: <m2poo5u9c9.fsf@bradyt.com> (Brady Trainor's message of "Wed, 14 Sep 2016 20:32:06 -0700")
On Sep 15 2016, Brady Trainor <brady@bradyt.com> wrote:
> If I have a directory `a', and try to rename it `A' in dired, it errors.
>
> `(file-error Renaming Invalid argument /tmp/a /tmp/A/a)'.
That's because your filesystem is case-insensitve, thus /tmp/A already
exists.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2016-09-15 9:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 3:32 bug#24441: 24.5; rename directory in dired to change case Brady Trainor
2016-09-15 9:05 ` Tino Calancha
2016-09-15 9:28 ` Andreas Schwab [this message]
2016-09-15 13:43 ` Drew Adams
2016-09-15 14:49 ` Eli Zaretskii
2016-09-15 14:31 ` Eli Zaretskii
2016-11-14 20:33 ` Paul Eggert
2016-11-15 19:59 ` Ken Brown
2016-11-15 20:30 ` Eli Zaretskii
2016-11-30 22:22 ` Ken Brown
2017-05-21 6:17 ` Paul Eggert
[not found] <<m2poo5u9c9.fsf@bradyt.com>
[not found] ` <<mvmeg4la4w6.fsf@hawking.suse.de>
[not found] ` <<3c49fbe5-9ae0-4ae2-8fa0-3c44fa85c981@default>
[not found] ` <<83d1k56wwt.fsf@gnu.org>
2016-09-15 14:57 ` Drew Adams
2016-09-15 15:20 ` Eli Zaretskii
2016-09-15 16:03 ` Ken Brown
2016-09-15 16:36 ` Eli Zaretskii
2016-11-10 22:25 ` Ken Brown
2016-11-11 1:42 ` Ken Brown
2016-11-11 8:27 ` Eli Zaretskii
2016-11-11 16:23 ` Michael Albinus
2016-11-11 21:42 ` Ken Brown
2016-11-12 7:29 ` Eli Zaretskii
2016-11-13 13:14 ` Ken Brown
2016-11-15 19:58 ` Michael Albinus
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=mvmeg4la4w6.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=24441@debbugs.gnu.org \
--cc=brady@bradyt.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).