From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu,
npostavs@gmail.com
Subject: bug#31636: 27.0.50; lockfile syntax searchable from info manual
Date: Fri, 01 Jun 2018 16:00:15 +0300 [thread overview]
Message-ID: <83k1rifyqo.fsf@gnu.org> (raw)
In-Reply-To: <87h8mmu6jp.fsf@gmail.com> (message from Robert Pluim on Fri, 01 Jun 2018 12:47:54 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: mail@bradyt.com, 31636@debbugs.gnu.org, eggert@cs.ucla.edu, npostavs@gmail.com
> Date: Fri, 01 Jun 2018 12:47:54 +0200
>
> > This should use @var{user}, @var{host} etc. for the components of the
> > target file name, and it should explain shortly what each component
> > stands for.
>
> I donʼt see any difference in the visual appearance from using @var,
In Info format, you won't see any difference, because @var up-cases
its argument in that format. But in the printed manual the visual
appearance of @var is very different: it gives the argument the
slanted typeface and doesn't up-case it.
> (I noticed that texinfo.el has no bindings for inserting @ref,
> @xref, and @pxref, should I add some? C-cC-c[rp] are free, but x is
> already used for @example, so 'C-cC-cX'? Or maybe 'C-cC-cC-x' for
> @xref?)
How about using just "C-c C-c r" and letting it intuit the exact form
from the context? @xref is only used at the beginning of a sentence,
and @pxref should normally follow an open paren.
In any case, adding this to texinfo.el would be a welcome addition, I
think.
The patch LGTM, thanks.
next prev parent reply other threads:[~2018-06-01 13:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 7:33 bug#31636: 27.0.50; lockfile syntax searchable from info manual Brady Trainor
2018-05-29 8:40 ` Robert Pluim
2018-05-29 11:24 ` Noam Postavsky
2018-05-29 13:17 ` Robert Pluim
2018-05-29 16:46 ` Eli Zaretskii
2018-05-29 19:06 ` Robert Pluim
2018-05-30 2:42 ` Eli Zaretskii
2018-05-31 10:29 ` Robert Pluim
2018-06-01 8:52 ` Eli Zaretskii
2018-06-01 10:47 ` Robert Pluim
2018-06-01 13:00 ` Eli Zaretskii [this message]
2018-06-01 13:24 ` Robert Pluim
2018-06-01 13:25 ` Robert Pluim
2018-06-01 13:42 ` Robert Pluim
2018-06-04 9:41 ` Robert Pluim
2018-06-04 10:39 ` Andreas Schwab
2018-06-04 14:02 ` Robert Pluim
2018-06-04 16:06 ` Eli Zaretskii
2018-06-04 15:55 ` Eli Zaretskii
2018-06-04 17:17 ` Robert Pluim
2018-06-05 15:07 ` Eli Zaretskii
2018-06-05 19:51 ` Robert Pluim
2018-06-05 20:08 ` Noam Postavsky
2018-06-06 7:43 ` Robert Pluim
2018-06-06 13:13 ` Noam Postavsky
2018-06-06 13:51 ` Robert Pluim
2018-06-06 14:41 ` Noam Postavsky
2018-06-06 14:51 ` Robert Pluim
2018-05-29 19:20 ` Paul Eggert
2018-05-30 2:42 ` Eli Zaretskii
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=83k1rifyqo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31636@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=mail@bradyt.com \
--cc=npostavs@gmail.com \
--cc=rpluim@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.