From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 63221@debbugs.gnu.org
Subject: bug#63221: 30.0.50; [PATCH] Eshell should get user (and group) IDs in a connection-aware fashion
Date: Tue, 02 May 2023 14:58:39 +0300 [thread overview]
Message-ID: <83bkj3ndw0.fsf@gnu.org> (raw)
In-Reply-To: <473147ec-87a1-8a2a-9062-bbdef41da3ac@gmail.com> (message from Jim Porter on Mon, 1 May 2023 22:42:53 -0700)
> Date: Mon, 1 May 2023 22:42:53 -0700
> From: Jim Porter <jporterbugs@gmail.com>
>
> -(defcustom eshell-rm-interactive-query (= (user-uid) 0)
> - "If non-nil, `rm' will query before removing anything."
> - :type 'boolean
> +(define-widget 'eshell-interactive-query 'lazy
> + "When to interatively query the user about a particular operation."
This terse sentence needs to be explained in the rest of the doc
string, because, unlike "If non-nil", "When" does not explain itself.
The doc string should explain how to specify "when". It should also
explain the different supported values.
> + :tag "Query"
> + :type '(choice (const :tag "Never" nil)
> + (const :tag "Always" t)
> + (const :tag "When root" root)))
Also, the default value is not one of the possible optional values.
Same comment to the other similar defcustoms where you changed a
boolean option to something else: their doc strings are now
obfuscated.
> +(defun eshell-interactive-query-p (value)
> + "Return non-nil if a command should query the user according to VALUE.
> +If VALUE is `root', return non-nil when evaluated as root (see
> +`file-user-uid'). Otherwise, simply return VALUE."
You assume here that "evaluated as root" explains itself? I wouldn't
rely on that.
Thanks.
next prev parent reply other threads:[~2023-05-02 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 5:42 bug#63221: 30.0.50; [PATCH] Eshell should get user (and group) IDs in a connection-aware fashion Jim Porter
2023-05-02 11:58 ` Eli Zaretskii [this message]
2023-05-02 18:36 ` Jim Porter
2023-05-02 18:44 ` Eli Zaretskii
2023-05-03 4:30 ` Jim Porter
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=83bkj3ndw0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63221@debbugs.gnu.org \
--cc=jporterbugs@gmail.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.