From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, 54470@debbugs.gnu.org
Subject: bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion
Date: Fri, 01 Apr 2022 00:11:29 -0400 [thread overview]
Message-ID: <E1na8dF-0006Q3-0d@fencepost.gnu.org> (raw)
In-Reply-To: <83k0ca7fo6.fsf@gnu.org> (message from Eli Zaretskii on Thu, 31 Mar 2022 10:19:05 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Or would @kbd be better to use here? These are things meant to be typed
> > by the user into an interactive prompt, after all...
> For something that user should type, @kbd is appropriate, yes. But
> since these all are portions of file names, perhaps @file is the best
> markup.
@kbd is right for things that are meant specifically and only as
keyboard input.
All sorts of syntactic entities can be entered as input in certain contexts,
but that doesn't mean they should always be written in @kbd.
For instance, you can enter a file name as keyboard input.
Any file name can be entered that way.
But file names are used in many other contexts too.
Thus, in general a file name should not be written in @kbd,
not even whe you're talking about giving a file name as keyboard input.
Perhaps when you're talking about the act of typing a command
containing a file name you might use @kbd for that.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-04-01 4:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:34 bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion Jim Porter
2022-03-20 7:05 ` Eli Zaretskii
2022-03-20 20:57 ` Jim Porter
2022-03-28 2:29 ` Jim Porter
2022-03-30 4:47 ` Jim Porter
2022-03-31 7:19 ` Eli Zaretskii
2022-04-01 4:11 ` Richard Stallman [this message]
2022-04-02 5:10 ` Jim Porter
2022-04-15 12:56 ` Eli Zaretskii
2022-04-16 4:57 ` Jim Porter
2022-04-16 10:30 ` Eli Zaretskii
2022-04-16 17:14 ` Jim Porter
2022-04-17 7:32 ` Eli Zaretskii
2022-04-17 18:38 ` 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
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=E1na8dF-0006Q3-0d@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=54470@debbugs.gnu.org \
--cc=eliz@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 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).