From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 24897@debbugs.gnu.org
Subject: bug#24897: 24.5; doc for `M' in Dired
Date: Fri, 11 Oct 2019 08:42:21 -0700 (PDT) [thread overview]
Message-ID: <b7a7de08-ab3c-4b47-ba36-f5c2856d495d@default> (raw)
In-Reply-To: <CADwFkmmtroWL2iVhE+pZgGkab8uOBc8zVVdOi_DWE1hu5ezBqQ@mail.gmail.com>
> > I don't suggest that we "explain the w bit", for Windows users.
> >
> > My suggestion is to:
> >
> > 1. State that `chmod' does not apply, in general, to MS Windows.
> > (If you want to say why - no such bits etc., fine, but that's
> > not really needed, IMO.)
> > 2. State that you can use `chmod' to make a file writable or
> > read-only. And say how to do so.
>
> How about the attached patch?
Thanks for looking at this enhancement request. But,
sorry, that's not it at all.
1. It's definitely not the case that "This command
is generally not relevant on MS-Windows."
`M' _is_ relevant for MS Windows. I use it all the
time - every day. What's the case is that on Windows
you can't distinguish the different parts of the
permissions string: you can only change them for all
users at once.
But you can certainly change, for all users, from
read-only to writable, etc.
Admittedly, the text from me that you quote above
can give the impression that `M' is not relevant
for MS Windows. But reading all of the report
makes clear that it is very relevant. For example:
It is reasonable for a user on Windows to use `M'
to make files read-only or writable.
2. The main point of the request is to ask that the
doc for `M' say something about the permissions, that
it _not_ just point to a `man' page (which typically
won't be available for MS Windows users anyway).
It's good for the doc to _also_ mention the `chmod'
command and its `man' page, but this bug report asks
that the `M' doc itself provide at least a minimum of
help about this - the possible user inputs and their
effects.
The doc currently says, e.g., "Symbolic modes like
`g+w' are allowed." But that means nothing by itself.
This is the point of the bug report - what it says
at the outset:
[The user might] not know the UNIX command `chmod',
and might not know about file and directory permissions.
S?he might not even have what it takes locally to use
`M-x man', to find out.
And the doc for `M' - both the doc string and the Emacs
manual, does not really explain `chmod' or what kind of
input a user can type to the prompt from `M'.
I think it would be helpful, for at least some users,
to add some more explanation. In particular, it could
explain about u, g, o, and a, and about the permissions
fields rwx and their values.
next prev parent reply other threads:[~2019-10-11 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 18:52 bug#24897: 24.5; doc for `M' in Dired Drew Adams
2016-11-07 19:22 ` Eli Zaretskii
2019-10-11 14:43 ` Stefan Kangas
2019-10-11 14:51 ` Eli Zaretskii
2019-10-11 14:56 ` Eli Zaretskii
2019-10-13 22:37 ` Stefan Kangas
2019-10-14 6:40 ` Eli Zaretskii
2019-10-14 14:01 ` Stefan Kangas
2019-10-11 15:42 ` Drew Adams [this message]
2019-10-13 22:38 ` Stefan Kangas
2019-10-13 23:21 ` Drew Adams
2019-10-14 6:46 ` Eli Zaretskii
[not found] <<b7cf8a94-afca-47b4-8d4a-3356a70c8b2b@default>
[not found] ` <<83shr3gkn1.fsf@gnu.org>
2016-11-07 19:28 ` Drew Adams
2016-11-07 19:50 ` Eli Zaretskii
[not found] <<<b7cf8a94-afca-47b4-8d4a-3356a70c8b2b@default>
[not found] ` <<<83shr3gkn1.fsf@gnu.org>
[not found] ` <<106ca6bc-ecf5-439f-853b-63331a41d4b8@default>
[not found] ` <<83oa1rgjdf.fsf@gnu.org>
2016-11-07 20:39 ` Drew Adams
[not found] <<CADwFkmmtroWL2iVhE+pZgGkab8uOBc8zVVdOi_DWE1hu5ezBqQ@mail.gmail.com>
[not found] ` <<83ftjzpc7g.fsf@gnu.org>
[not found] ` <<83d0f3pbzu.fsf@gnu.org>
2019-10-11 15:45 ` Drew Adams
2019-10-11 15:57 ` Eli Zaretskii
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=b7a7de08-ab3c-4b47-ba36-f5c2856d495d@default \
--to=drew.adams@oracle.com \
--cc=24897@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).