On Thu, Jul 19, 2012 at 06:56:10PM +0300, Eli Zaretskii wrote:
>
> > > Yes, @if* are the problem.
> >
> > And you think it is not fixed by calling makeinfo with --iftex
> > --no-ifinfo?
>
> First, there are also @ifset and @ifclear.
Ok, but then there is -D/-U and this is not different than in
On Wed, Jul 18, 2012 at 09:25:41PM +0300, Eli Zaretskii wrote:
>
> Macros never worked well with TeX, so -E was a band-aid that not
> always worked.
I don't understand. If macro do not work well with TeX, -E is a way to
avoid expanding macros in TeX. To me, it may be the way to go.
> > > also
On Wed, Jul 18, 2012 at 01:35:26PM -0600, Eric Blake wrote:
>
> >
> > As a side note, there is also another item, still in limitations
> > of @macros in TeX that says
> >
> >* Macro arguments cannot cross lines.
>
> Is that restriction limited to a per-argument basis (but you can have
> ne
On Tue, Jul 17, 2012 at 10:46:58AM -0600, Eric Blake wrote:
>
> tool and therefore which semantics will be encountered). My preference
> would be for preserving the existing semantics, so that the autoconf
> manual does not have to change what it already has in place.
Here is a patch for the aut
On Tue, Jul 17, 2012 at 08:51:18PM +0300, Eli Zaretskii wrote:
>
> Yes, AFAIR using the comment is a common trick to prevent a newline
> from being emitted after the macro.
I had a look at the manual, and I can see that touched upon in
'Macro Details and Caveats':
* It is (usually) best to av
On Wed, Jul 18, 2012 at 08:02:34PM +0300, Eli Zaretskii wrote:
>
> "makeinfo -E" was never used too much, so I'm not surprised. It is
I have no information about that, however I guess this was useful when
used as part of texi2dvi -e, -E, --expand as TeX has many
limitations/bugs in macro expansi
On Tue, Jul 17, 2012 at 08:51:18PM +0300, Eli Zaretskii wrote:
> >
> > You mean that it is intended that the comment is removed as part of the
> > user defined macro expansion?
>
> Yes, AFAIR using the comment is a common trick to prevent a newline
> from being emitted after the macro.
I don't s
On Tue, Jul 17, 2012 at 10:46:58AM -0600, Eric Blake wrote:
>
> What does this mean to the end user? Autoconf needs to have a macro
> whose expansion does not end with the current line, and where the manual
> can be compiled with both old and new tools (that is, I do not want to
> force autoconf
On Tue, Jul 17, 2012 at 06:44:31PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 17 Jul 2012 10:19:15 +0200
> > From: Patrice Dumas
> > Cc: stefano.lattar...@gmail.com, bug-autoconf@gnu.org, bug-texi...@gnu.org
> >
> > My wild guess is that this strange behaviour of ma
On Mon, Jul 16, 2012 at 09:18:07PM +0300, Eli Zaretskii wrote:
>
> This is wrong, the newline at the end of the macro (after the @c)
> should be part of the macro expansion. AFAIR, this is how the C
> makeinfo worked, because the newline was collected as part of the
> macro body when the @macro..
On Mon, Jul 16, 2012 at 12:14:01PM +0200, Stefano Lattarini wrote:
> Here are the errors that I'm getting:
>
> autoconf.texi:8018: Misplaced }
I think that this is correct (and my guess is that the other are in fact
consequences and similar other issues). Indeed, there is a @macro:
@macro ovar{
On Mon, Jun 14, 2010 at 09:35:33PM +, Karl Berry wrote:
> Hi Ralf,
>
> Thanks for the report, as always.
>
> need to double backslashes in the macro definition, but is silent
> about macro arguments.
> I think it is makeinfo that is doing the wrong thing here.
I don't think so, be
12 matches
Mail list logo
