unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: 22300@debbugs.gnu.org, esq@lawlist.com
Subject: bug#22300: 25.1.50; Dired -- renaming folders/files to CamelCase/UPPERCASE/lowercase.
Date: Mon, 04 Jan 2016 22:31:49 +0200	[thread overview]
Message-ID: <83oad15bnu.fsf@gnu.org> (raw)
In-Reply-To: <m2vb792kie.fsf@newartisans.com> (message from John Wiegley on Mon, 04 Jan 2016 11:48:57 -0800)

> From: John Wiegley <jwiegley@gmail.com>
> Cc: drew.adams@oracle.com,  22300@debbugs.gnu.org,  esq@lawlist.com
> Date: Mon, 04 Jan 2016 11:48:57 -0800
> 
> >>>>> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Is there a C-callable API that could establish which one is it? Something
> > like the Posix 'pathconf', perhaps, with some magic _PC_something argument?
> 
> It looks like getattrlist(2) is what you need:
> 
> https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man2/getattrlist.2.html
> 
> Specifically, the volume attribute VOL_CAP_FMT_CASE_SENSITIVE.

Thanks.  Patches are welcome to use this in rename-file.  I would
suggest a Darwin-specific version of string-equal that would compare
case-insensitively or case-sensitively as the volume requires that.
Then we could call that function from rename-file, like we do with
string-equal in the DOS_NT part there.





  reply	other threads:[~2016-01-04 20:31 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
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 [this message]
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=83oad15bnu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22300@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 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).