GNU bug report logs - #54470
29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion

Previous Next

Full log

Message #23 received at 54470 <at> debbugs.gnu.org (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: jporterbugs <at> gmail.com, 54470 <at> debbugs.gnu.org
Subject: Re: bug#54470: 29.0.50;
 [PATCH] Add documentation/tests for Eshell argument expansion
Date: Fri, 01 Apr 2022 00:11:29 -0400

[[[ 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)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.