[Top][All Lists]

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

Re: headers, and what include doesn't do

From: David Wright
Subject: Re: headers, and what include doesn't do
Date: Thu, 15 Oct 2020 19:33:32 -0500
User-agent: Mutt/1.10.1 (2018-07-13)

On Thu 15 Oct 2020 at 19:23:36 (-0400), Molly Preston wrote:
> Thank you guys. I tried the way Mark suggested before and I get the same
> result of III. being shown on the first page. So still not seeming to
> understand.

Perhaps you could start with an example like the attached, and just
remove everything that you don't need. The "default" behaviour of LP
is shown by the first attachment, where you wouldn't expect to have
all the titling repeated before the second and third movements
(unless you manage to chart with your delightful slow movement:) ).

The second attachment shows the effect of print-all-headers = ##t,
which you might use where, for example, the lyrics of each movement
come from a different source.

After you've modified and pruned one of these to show whichever headings
you need, you could then distribute the contents amongst your sonata files.

> > > I am trying to use \include to compile my sonata. The score block and
> > headings are in each file.
> > >
> > > I basically just have this:
> > >
> > > \include ""
> > > \pageBreak
> > > \include ""
> > > \pageBreak
> > > \include ""
> > >
> > > The third movement's heading is what's being shown on the first page.
> > That is why I ask about the hierarchy of headings. I tried putting the
> > headings in this file instead of in each individual file.

It's seems very likely from the way you've expressed your problem that
you think LP attaches some meaning to \include. It doesn't. Writing
\include ""   just pastes the contents of into the source
at that point. After all the \include files have been copied in, then
LP processes the resulting big/gigantic file that results. (You could
perfectly well do the same assembly job with cut&paste in an editor.)


Description: Text document

Description: Text document

reply via email to

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