From: myglc2 <myglc2@gmail.com>
To: 24056@debbugs.gnu.org
Subject: bug#24056: `DATA and 'DATA look the same in Guile INFO in emacs on tty & X11
Date: Fri, 22 Jul 2016 16:09:37 -0400 [thread overview]
Message-ID: <cu7a8h977um.fsf@gmail.com> (raw)
Hello Guile,
You probably already know this, but, when viewing the Guile INFO on
emacs in tty or X11, the "Expression Syntax" part of the manual reads:
[...]
(quote DATA)
’DATA
[...]
(quasiquote DATA)
‘DATA
[...]
That is, the 'DATA and `DATA examples are both typeset with single
quote.
Upshot: One looks at things that are identical when one first reads how
they differ and wonders if one is going blind ;-)
I guess this is a problem with how @itemx handles backquote on these
platforms because the ./ref/api-evaluation.texi has a backquote ...
@itemx `@var{data}
... and is correctly typeset in the HTML doc.
Anyway, maybe the 'DATA & `DATA examples could be marked up differently
to overcome this?
next reply other threads:[~2016-07-22 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 20:09 myglc2 [this message]
2017-03-01 8:43 ` bug#24056: `DATA and 'DATA look the same in Guile INFO in emacs on tty & X11 Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7a8h977um.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=24056@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.
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).