From: Stephen Berman <stephen.berman@gmx.net>
To: 34372@debbugs.gnu.org
Subject: bug#34372: 27.0.50; Quoting problem in (elisp) Documentation Tips
Date: Thu, 07 Feb 2019 18:10:39 +0100 [thread overview]
Message-ID: <87mun7ttgw.fsf@gmx.net> (raw)
Prompted by the current thread "Quoting t and nil in docstrings" on
emacs-devel, I noticed a display problem in the Info node (elisp)
Documentation Tips, line 99, in the following sequence of characters:
‘CODE can be ‘lambda’, nil, or t’
The sequence
CODE can be ‘lambda
is displayed with Info-quoted face, all the other characters with the
default face. I supposed this is a texinfo (or makeinfo) bug triggered
by the nested quoting in the display (in the texinfo source the above
sequence of characters is enclosed in @samp{}, except for the uttermost
quote signs, which are only in the Info display). In lieu of a fix for
this bug I see two workarounds for the Emacs tips.texi file: (a) use the
"older single-quoting convention", i.e. `lambda', which is also used in
other examples in this very node; (b) use the @example environment
instead of @samp, which does not add the outer quotes and displays the
entire sequence in the default face (but then this example would look
different from the other examples in this node that use the "older
single-quoting convention", so maybe both (a) and (b), or change the
quoting in the other examples). I haven't tried to check whether there
are other instances of this display issue in the Emacs doc.
In GNU Emacs 27.0.50 (build 33, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
of 2019-02-02 built on rosalinde
Repository revision: 2f55b971b42d13188157331a1e514949f20ced4f
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12001000
System Description: 8.3
next reply other threads:[~2019-02-07 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 17:10 Stephen Berman [this message]
2019-02-07 17:51 ` bug#34372: 27.0.50; Quoting problem in (elisp) Documentation Tips 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=87mun7ttgw.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=34372@debbugs.gnu.org \
/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.