all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: bzg@altern.org, eggert@cs.ucla.edu, michael.albinus@gmx.de,
	emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r111840: Port documentation to Texinfo 5.0.
Date: Fri, 22 Feb 2013 22:12:12 +0200	[thread overview]
Message-ID: <83zjywkt0j.fsf@gnu.org> (raw)
In-Reply-To: <20bobc171p.fsf@fencepost.gnu.org>

> From: Glenn Morris <rgm@gnu.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>,  Michael Albinus <michael.albinus@gmx.de>,  bzg@altern.org,  emacs-devel@gnu.org
> Date: Fri, 22 Feb 2013 14:29:22 -0500
> 
> Eli Zaretskii wrote:
> 
> > 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.
> 
> If it turns out to needs a non-trivial fix like this, I think it can go
> in trunk only.

The fix, if it is accepted, involves changing some of the calls to
trampfn into calls to on of 2 or 3 other (new) macros.  I don't see
anything non-trivial here, certainly not something that could
potentially destabilize the branch.  But it's your call.

> The manuals are pre-built in the release tarfile, so it's
> not a big deal if one doesn't build with the latest Texinfo.

This argument goes both ways: since they are pre-built, any problems
with the non-trivial fix will be solved before the release is tarred.
The advantage is that users can modify the manual and still produce
the Info files.



  reply	other threads:[~2013-02-22 20:12 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 [this message]
2013-02-22 20:34               ` Michael Albinus
2013-02-22 20:50                 ` Eli Zaretskii
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=83zjywkt0j.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 \
    --cc=rgm@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.