unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: 9362@debbugs.gnu.org
Subject: bug#9362: 24.0.50; Explain in manual(s) Dired/ls permissions listing on Windows
Date: Wed, 24 Aug 2011 09:05:02 -0700	[thread overview]
Message-ID: <1EEEDDB70B5C4007B90959E3E5F2E5E5@us.oracle.com> (raw)

emacs -Q
 
I see no explanation in the Emacs manual (for Dired) or in the Elisp
manual (wrt file attributes or somewhere else) about what `ls' (hence
Dired) lists wrt file permissions on Windows.
 
The doc string of `file-attributes' is also pretty silent about this -
it says simply "file modes" (doesn't even use the word "permissions").
 
Some explanation should be given about permissions.  I'm using FAT32,
for instance, and I see `x' for all directories and for no files.
`chmod' with `+x' or `-x' has no effect, and with no message.  No doubt
this is due to Windows not supporting this.  But that should be
explained - documented.
 
In Dired we show some permissions that apparently have no real meaning
on Windows (FAT, at least), and we provide a command (`chmod') which on
Windows does not do everything its doc says.  OK, I'm using Cygwin for
the UNIX `chmod', but regardless, there should be some explanation of
these things in the manual(s).
 

In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
 of 2011-08-22 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt'
 






             reply	other threads:[~2011-08-24 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 16:05 Drew Adams [this message]
2011-09-11  2:12 ` bug#9362: 24.0.50; Explain in manual(s) Dired/ls permissions listing on Windows Lars Magne Ingebrigtsen
2011-09-11  2:25   ` Lennart Borgman
2011-09-11 14:44     ` Drew Adams
2016-04-28 11:14     ` Lars Ingebrigtsen

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=1EEEDDB70B5C4007B90959E3E5F2E5E5@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=9362@debbugs.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).