From: Eli Zaretskii <eliz@gnu.org>
To: monnier@iro.umontreal.ca
Cc: 18040@debbugs.gnu.org
Subject: bug#18040: 24.4.50; "@acronym" in "(emacs) Intro"
Date: Sat, 19 Jul 2014 10:24:59 +0300 [thread overview]
Message-ID: <83mwc56cac.fsf@gnu.org> (raw)
In-Reply-To: <83oawl6cnn.fsf@gnu.org>
> Date: Sat, 19 Jul 2014 10:17:00 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 18040@debbugs.gnu.org
>
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Cc: Dani Moncayo <dmoncayo@gmail.com>, 18040@debbugs.gnu.org
> > Date: Fri, 18 Jul 2014 23:02:05 -0400
> >
> > > Evidently, Texinfo 4.x doesn't support recursive @acronyms.
> >
> > Sounds like a major bug for GNU's official documentation system!
>
> Since 5.x solved it, we don't have a case here.
Btw, using the inner @acronym is obviously wrong here, it's just a
pun. So one way of fixing this for those who still use Texinfo 4.x
for whatever reasons is to remove the inner @acronym, leaving just
"GNU" there.
The Texinfo manual has the same problem, FWIW.
next prev parent reply other threads:[~2014-07-19 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 12:20 bug#18040: 24.4.50; "@acronym" in "(emacs) Intro" Dani Moncayo
2014-07-17 14:48 ` Eli Zaretskii
2014-07-17 15:27 ` Dani Moncayo
2014-07-19 3:02 ` Stefan Monnier
2014-07-19 7:17 ` Eli Zaretskii
2014-07-19 7:24 ` Eli Zaretskii [this message]
2014-07-21 3:32 ` Glenn Morris
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=83mwc56cac.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18040@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).