unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 24897@debbugs.gnu.org
Subject: bug#24897: 24.5; doc for `M' in Dired
Date: Mon, 7 Nov 2016 10:52:13 -0800 (PST)	[thread overview]
Message-ID: <b7cf8a94-afca-47b4-8d4a-3356a70c8b2b@default> (raw)

This: http://emacs.stackexchange.com/q/28504/105, asks how to make files
read-only using Dired.  Besides using wdired, the obvious answer is to
use `M'.

However, in answering that, it becomes clear that the questioner does
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.


In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'





             reply	other threads:[~2016-11-07 18:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 18:52 Drew Adams [this message]
2016-11-07 19:22 ` bug#24897: 24.5; doc for `M' in Dired 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
     [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=b7cf8a94-afca-47b4-8d4a-3356a70c8b2b@default \
    --to=drew.adams@oracle.com \
    --cc=24897@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).