all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: John Wiegley <jwiegley@gmail.com>,
	Keith David Bershatsky <esq@lawlist.com>
Cc: 22300-done@debbugs.gnu.org
Subject: bug#22300: 25.1.50; Dired -- renaming folders/files to CamelCase/UPPERCASE/lowercase.
Date: Sun, 3 Jan 2016 16:47:32 -0800 (PST)	[thread overview]
Message-ID: <a936bee4-3375-45cf-ab35-62e36a21f003@default> (raw)
In-Reply-To: <m24meutlmk.fsf@newartisans.com>

> Since this is not an Emacs bug, I'm closing this report, but here is what I
> do that should work for you:
> 
>   1. Rename the file to 'x'.
>   2. Rename 'x' to the correctly cased name.
> 
> Copy the name to the kill-ring before #1, so that you can paste it in when
> asked by #2.

Hm.  I'm curious.  How do we know that this is not an Emacs bug?

I do not understand why this is his error msg:

    Move '/Users/HOME/Desktop/FOO' to '/Users/HOME/Desktop/foo/FOO' failed:
                              ^^^                          ^^^^^^^
      (file-error Renaming Invalid argument 
       /Users/HOME/Desktop/FOO/Users/HOME/Desktop/foo/FOO)

That looks peculiar, if all he did was hit `R' on a directory name.
That message seems to be saying that Emacs asked the OS to move
directory .../FOO to .../foo/FOO.  That doesn't seem like the right
thing for Emacs to do.  Seems like Emacs should have asked the OS
to move .../FOO to .../foo (without the trailing /FOO).

Am I missing something?

Also, I see from Keith's StackExchange question about this that
he is able to use `mv FOO foo' to do the renaming without a problem.
http://emacs.stackexchange.com/q/19234/105





  reply	other threads:[~2016-01-04  0:47 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a936bee4-3375-45cf-ab35-62e36a21f003@default \
    --to=drew.adams@oracle.com \
    --cc=22300-done@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.