it is not easy to decide whether the bar number should be moved to
the non-ossia staff.
I see no application where it would make sense to keep it above.
Here's the only solution (already in the notation reference) which
works correctly without abusing \RemoveEmptyStaves. IMHO, the example
Werner LEMBERG wl at gnu.org writes:
it is not easy to decide whether the bar number should be moved to
the non-ossia staff.
I see no application where it would make sense to keep it above.
Here's the only solution (already in the notation reference) which
works correctly
The
A different score is at http://k-ohara.oco.net/Lilypond/ chosen to show off
the improvements made since version 2.16 (even the skyline-spacing of text that I
tried to throw out) and with source that complies both with version 2.16 and current
(which took some effort).
There are workarounds in
Dear LilyPond community,
my apologies for having disappeared these days. I have important
issues at end of every semester, along with taxes, family, and own
studies.
Especially Federico, please forgive me for ignoring your request of
more information on a lilypond-book-related matter.
I will
The temporary staff is more natural, but sometimes we need to use a
continuous staff with \startStaff \stopStaff in order to convince
LilyPond that it goes on the same line
http://code.google.com/p/lilypond/issues/detail?id=1449
But #1449 is a bug IMHO...
Werner
Werner LEMBERG w...@gnu.org writes:
The temporary staff is more natural, but sometimes we need to use a
continuous staff with \startStaff \stopStaff in order to convince
LilyPond that it goes on the same line
http://code.google.com/p/lilypond/issues/detail?id=1449
But #1449 is a bug IMHO...
2013/5/29 Francisco Vila paconet@gmail.com
Dear LilyPond community,
my apologies for having disappeared these days. I have important
issues at end of every semester, along with taxes, family, and own
studies.
Especially Federico, please forgive me for ignoring your request of
more
Hi,
Few months ago, I suggested Mike Solomon (which was asking for work
during flight time) to add the regular recorder in the woodwind
diagram module, but for some reasons the request remained unanswered.
Having myself recently some travel time to spend, I managed to make it
myself, but the
On 29 mai 2013, at 17:30, Dominique Faure dominique.fa...@gmail.com wrote:
Hi,
Few months ago, I suggested Mike Solomon (which was asking for work
during flight time) to add the regular recorder in the woodwind
diagram module, but for some reasons the request remained unanswered.
Having
- Original Message -
From: Dominique Faure dominique.fa...@gmail.com
To: lilypond-devel lilypond-devel@gnu.org
Sent: Wednesday, May 29, 2013 3:30 PM
Subject: Woodwind diagram for recorder
Hi,
Few months ago, I suggested Mike Solomon (which was asking for work
during flight time) to
Le 29/05/2013 10:13, Francisco Vila disait :
Dear LilyPond community,
my apologies for having disappeared these days. I have important
issues at end of every semester, along with taxes, family, and own
studies.
That's a full score with too many staves in one system!
Do your best, I'll
Hi,
2013/5/29 Dominique Faure dominique.fa...@gmail.com:
Having myself recently some travel time to spend, I managed to make it
myself, but the code nature (non-public module scheme functions),
prevent me to deliver it as a regular snippet.
Despite not having a computer configuration
12 matches
Mail list logo
