all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 34372-done@debbugs.gnu.org
Subject: bug#34372: 27.0.50; Quoting problem in (elisp) Documentation Tips
Date: Thu, 07 Feb 2019 19:51:17 +0200	[thread overview]
Message-ID: <83pns3qyga.fsf@gnu.org> (raw)
In-Reply-To: <87mun7ttgw.fsf@gmx.net> (message from Stephen Berman on Thu, 07 Feb 2019 18:10:39 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Thu, 07 Feb 2019 18:10:39 +0100
> 
> 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.

I used the @example method.

Thanks.





      reply	other threads:[~2019-02-07 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 17:10 bug#34372: 27.0.50; Quoting problem in (elisp) Documentation Tips Stephen Berman
2019-02-07 17:51 ` Eli Zaretskii [this message]

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=83pns3qyga.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34372-done@debbugs.gnu.org \
    --cc=stephen.berman@gmx.net \
    /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.