From: Robert Pluim <rpluim@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 55984@debbugs.gnu.org
Subject: bug#55984: 26.3; Doc string of `chmod' / `set-file-modes'
Date: Wed, 15 Jun 2022 11:03:32 +0200 [thread overview]
Message-ID: <87r13qz4bf.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488C1464066DB3A53BE8D9BF3AA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Tue, 14 Jun 2022 21:36:37 +0000")
>>>>> On Tue, 14 Jun 2022 21:36:37 +0000, Drew Adams <drew.adams@oracle.com> said:
Drew> Please consider mentioning in the doc string that the command prompts
Drew> for the file name and (then for) the modes. The doc currently says how
Drew> the modes are read, but it doesn't say that the command reads the file
Drew> name.
Passive voice as well. How about the following for emacs-28
diff --git a/src/fileio.c b/src/fileio.c
index 7d392e0de7..a240216dea 100644
--- a/src/fileio.c
+++ b/src/fileio.c
@@ -3510,8 +3510,9 @@ DEFUN ("set-file-modes", Fset_file_modes, Sset_file_modes, 2, 3,
Only the 12 low bits of MODE are used. If optional FLAG is `nofollow',
do not follow FILENAME if it is a symbolic link.
-Interactively, mode bits are read by `read-file-modes', which accepts
-symbolic notation, like the `chmod' command from GNU Coreutils. */)
+Interactively, prompts for FILENAME, and reads MODE with
+`read-file-modes', which accepts symbolic notation, like the `chmod'
+command from GNU Coreutils. */)
(Lisp_Object filename, Lisp_Object mode, Lisp_Object flag)
{
CHECK_FIXNUM (mode);
Robert
--
next prev parent reply other threads:[~2022-06-15 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 21:36 bug#55984: 26.3; Doc string of `chmod' / `set-file-modes' Drew Adams
2022-06-15 9:03 ` Robert Pluim [this message]
2022-06-15 12:19 ` Lars Ingebrigtsen
2022-06-15 12:32 ` Robert Pluim
2022-06-15 13:08 ` Eli Zaretskii
2022-06-15 13:19 ` Robert Pluim
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=87r13qz4bf.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=55984@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.