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 12:39:11 -0800 (PST) [thread overview]
Message-ID: <0a992327-fdb6-4c5a-8d97-63bb697fa56f@default> (raw)
In-Reply-To: <<83oa1rgjdf.fsf@gnu.org>>
> But there's no "write" bit on Windows, at least not on the level on
> which the 'M' command in Dired works on Windows. So you cannot
> really explain the w bit, either.
>
> You need a completely separate description for Windows users.
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.
next parent reply other threads:[~2016-11-07 20:39 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>
[not found] ` <<106ca6bc-ecf5-439f-853b-63331a41d4b8@default>
[not found] ` <<83oa1rgjdf.fsf@gnu.org>
2016-11-07 20:39 ` Drew Adams [this message]
[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 ` bug#24897: 24.5; doc for `M' in Dired Drew Adams
2019-10-11 15:57 ` 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
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
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=0a992327-fdb6-4c5a-8d97-63bb697fa56f@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 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).