unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 54470@debbugs.gnu.org
Subject: bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion
Date: Thu, 31 Mar 2022 10:19:05 +0300	[thread overview]
Message-ID: <83k0ca7fo6.fsf@gnu.org> (raw)
In-Reply-To: <ba2464ee-2b95-47c2-bbcf-0a9c55e98572@gmail.com> (message from Jim Porter on Sun, 20 Mar 2022 13:57:26 -0700)

> Cc: 54470@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Sun, 20 Mar 2022 13:57:26 -0700
> 
> >> +@table @code
> >> +
> >> +@item *
> >> +Matches any string (including the empty string).  For example,
> >> +@samp{*.el} matches any file with the @file{.el} extension.
> > 
> > You use @code in the @table, but @samp in the body, which will look
> > inconsistent in the printed version of the manual.  Please use one of
> > them (I think @samp is better).
> 
> Done. I only did this for the glob section though. Should I change the 
> items in the predicates/modifiers to use @samp too? They're different 
> enough that I'm not quite sure.
> 
> 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.

Thanks.





  parent reply	other threads:[~2022-03-31  7:19 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 [this message]
2022-04-01  4:11       ` Richard Stallman
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=83k0ca7fo6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54470@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 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).