From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 24897@debbugs.gnu.org
Subject: bug#24897: 24.5; doc for `M' in Dired
Date: Mon, 7 Nov 2016 11:28:52 -0800 (PST) [thread overview]
Message-ID: <106ca6bc-ecf5-439f-853b-63331a41d4b8@default> (raw)
In-Reply-To: <<83shr3gkn1.fsf@gnu.org>>
> Since the original question was about "making the file read-only",
> I'm guessing the OP is on Windows,
That the user might be on Windows is a good guess. Or s?he could just
be a beginner wrt UNIX (or GNU/Linux).
> and if that is so, explaining the
> Unix-style permission bits won't help a bit.
True enough for r and x, but not for w. It is reasonable for a user
on Windows to use `M' to make files read-only or writable.
A little bit more help from the doc for such users could help, I think.
next parent reply other threads:[~2016-11-07 19:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<b7cf8a94-afca-47b4-8d4a-3356a70c8b2b@default>
[not found] ` <<83shr3gkn1.fsf@gnu.org>
2016-11-07 19:28 ` Drew Adams [this message]
2016-11-07 19:50 ` bug#24897: 24.5; doc for `M' in Dired Eli Zaretskii
[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
[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
2016-11-07 18:52 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
2019-10-14 6:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=106ca6bc-ecf5-439f-853b-63331a41d4b8@default \
--to=drew.adams@oracle.com \
--cc=24897@debbugs.gnu.org \
--cc=eliz@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 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.