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: Sun, 13 Oct 2019 23:21:51 +0000 (UTC) [thread overview]
Message-ID: <7e2e7d39-fa26-4970-b816-355165f862f1@default> (raw)
In-Reply-To: <CADwFkmkn+mQS10EG9BcE7ibN8dvf7RoNcFhJeAieRUWUQ0SHCg@mail.gmail.com>
> Are you suggesting that we fully document how both symbolic and octal
> modes work on Unix-like systems here?
How they work? No.
Everything about them ("fully")? No.
Something about them - a simple example? Why not?
I suggest something like this: Instead of
"symbolic modes like `g+w'" we say
"symbolic modes like `a+w' and `a-w'".
`a+w' and `a-w'o are likely the most useful for users on
MS Windows. And I think it helps to show both + and -.
(I wouldn't mind if we even indicated that +w adds write
permission and -w takes it away. But I don't push for that.)
> If so, I think it's outside the
> scope of this doc string. Linking to separate documentation seems
> more sensible, and the new patch I suggested does that.
Linking to complete doc (which is necessarily outside
Emacs, as you say), is helpful, of course. It's even
necessary.
But the Emacs doc can provide at least a little help -
something simple that even an MS Windows user can use.
A simple example can go a long way.
> +Note that on MS-Windows only the `w' (write) bit is meaningful:
> +resetting it makes the file read-only. Changing any other bit
> +has no effect on MS-Windows
I'm not sure "resetting" is as clear as this can be.
How about something like this?
Note that on MS-Windows only the `w' (write) bit is
meaningful. Adding it (`a+w') makes a file writable.
Removing it (`a-w') makes a file read-only. Changing
any other bit has no effect on MS-Windows.
(I also think, but Eli will correct me - and this might
depend on one's setup, that the use of `g',`u', and `o'
is useless on MS Windows. At least in my case there's
no distinction between `g', `u', `o', and `a'. But I
think I recall Eli saying that it is possible on Windows
for these to make a difference.)
Anyway, what you have already is an improvement. Thx.
next prev parent reply other threads:[~2019-10-13 23:21 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
2019-10-13 22:38 ` Stefan Kangas
2019-10-13 23:21 ` Drew Adams [this message]
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=7e2e7d39-fa26-4970-b816-355165f862f1@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).