[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Macro introduces \par in Table of Contents

From: Christopher Dimech
Subject: Re: Macro introduces \par in Table of Contents
Date: Sat, 3 Oct 2020 20:27:33 +0200

Have done some more tests and the \par problem extends also to multiline
titles for @chapter, @section, @subsection, and @subsubsec.

For users, using @ at the end of each line is acceptable. It also gets
the correct title alignments.  Using  DEL character is not a good strategy
for users.

@chapter{Amplitude Asymmetry in the Empirical Green Function Amplitude@

@section{Strong amplitude asymmetries between the Retarded Causal Branch@
and the Advanced Anti-Causal contribution to the Coherence Function}

Allowing Multiline titles would be a good improvement to Texinfo, especially
for users to write on complicated topics, books, etc.

One possible solution could include the addition of a Title Construction
Function one can call, which would allow multiline titles to be properly
passed to sections and subsections, including the unnumbered versions.

I have previously constructed macros with several arguments. My experience has
been that parameter values are being passed correctly even if they continue for
several  lines.  Might need to write some small examples and send them, to see
that works and what does not.


> Sent: Saturday, October 03, 2020 at 6:02 PM
> From: "Gavin Smith" <>
> To: "Christopher Dimech" <>
> Cc: "help-texinfo gnu" <>
> Subject: Re: Macro introduces \par in Table of Contents
> On Sat, Oct 3, 2020 at 2:32 PM Christopher Dimech <> wrote:
> >
> >
> > With the following code it worked
> >
> > @uSubSec{@value{SecLb}, Probabilistic Characterisation of@
> > Microseismicity}
> Yes, that would look like it would work, as there is a single letter
> control sequence "@NL" where NL is a newline character (see info node
> "(texinfo)Multiple Spaces").
> > But you are saying that it code breaks using a macro
> > inside an environment like @example.
> >
> > However, relating to sections and subsections, @uSubSec
> > won't be called in side an example.
> Yes, but other macros may be.
> > Can one do multiline titles using @unnumberedsec?
> This is not supported and if it works, it works by accident.
> > Does the multiline thing fail when using macros, or is the problem
> > only related to defining sections?
> It is because the @unnumberedsec command takes its argument on a single line.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]