From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, bzg@altern.org
Subject: Re: /srv/bzr/emacs/trunk r111840: Port documentation to Texinfo 5.0.
Date: Fri, 22 Feb 2013 22:50:05 +0200 [thread overview]
Message-ID: <83wqu0kr9e.fsf@gnu.org> (raw)
In-Reply-To: <87bobc3x5r.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, rgm@gnu.org, bzg@altern.org, emacs-devel@gnu.org
> Date: Fri, 22 Feb 2013 21:34:40 +0100
>
> > I think the best way to fix this would be to introduce several macros,
> > one each for every number of non-empty arguments, and then use each
> > one as needed. A bit less convenient, perhaps, but much more
> > straightforward.
> >
> > The question is would Michael accept this solution.
>
> I haven't played with texinfo 5 yet, so I cannot say too much. But the
> idea of @trampfn was to have just one unique macro with plays for
> all.
That part is clear from the macro definition and its use.
> Before changing this, I would like to check with texinfo 5 whether
> it is still possible.
What do you mean by "possible"? That macro is the only reason of the
error messages tramp.texi triggers from Texinfo 5.0. The new makeinfo
clearly does NOT support @set/@clear in the middle of text, and it
also doesn't support the @c trick of removing the newline from the
expansion of a macro.
While it is possible that Texinfo 5.0.1 or some such will be augmented
to support these tricks, it is IMO better to avoid them in the first
place: that way, the manual will build correctly with any Texinfo
version. But it's your decision, eventually.
> If I understand Glenn correctly, we have no rush for the emacs-24
> branch (please correct me if I'm wrong).
Texinfo 5.0 is out, so if we release Emacs 24.3 with tramp.texi as it
is now, people who have Texinfo 5.0 installed will be unable to
rebuild the manual if they need to change it for some reason. Not a
catastrophe, obviously, but IMO not nice, either: this is, after all,
Free Software.
next prev parent reply other threads:[~2013-02-22 20:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1U8Mer-0006Zn-J7@vcs.savannah.gnu.org>
2013-02-21 8:14 ` /srv/bzr/emacs/trunk r111840: Port documentation to Texinfo 5.0 Bastien
2013-02-21 17:25 ` Eli Zaretskii
2013-02-21 17:35 ` Paul Eggert
2013-02-21 18:35 ` Eli Zaretskii
2013-02-21 19:03 ` Glenn Morris
2013-02-21 21:35 ` Paul Eggert
2013-02-22 19:16 ` Eli Zaretskii
2013-02-22 19:29 ` Glenn Morris
2013-02-22 20:12 ` Eli Zaretskii
2013-02-22 20:34 ` Michael Albinus
2013-02-22 20:50 ` Eli Zaretskii [this message]
2013-02-24 18:21 ` Michael Albinus
2013-02-24 19:25 ` Glenn Morris
2013-02-24 20:13 ` Michael Albinus
2013-02-24 21:02 ` Eli Zaretskii
2013-02-25 8:33 ` Michael Albinus
2013-02-24 21:01 ` Eli Zaretskii
2013-02-21 19:14 ` Michael Albinus
2013-02-21 21:56 ` Bastien
2013-02-21 21:58 ` Bastien
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=83wqu0kr9e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bzg@altern.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.