Nick Payne wrote:
I have no idea why a different override is required just for that one
Oh dear!. More queer things going on.
The picture may give you an idea why (to a certain extent).
I have the impression you missed my suggestion in the last thread.
Nick Payne wrote:
How can I increase the length of the arpeggio bracket on seconds and
thirds, which at their default lengths are ridiculously short.
You can lengthen an arpeggio using the workaround given in
http://code.google.com/p/lilypond/issues/detail?id=794q=arrow
which
Nice :-)
I think this deserves a NEWS entry.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Kieren MacMillan wrote:
in the second bar, using the same override does nothing to
increase the spacing between the arpeggio and the preceding note.
Hmmm... that's probably because of the multiple-voices... but seems
like maybe a bug?
It is as if Lilypond thinks the span
When the connectArpeggios mode includes an arpeggio on a single note,
the resultant span arpeggio may collide with a previous note.
%%
\version 2.12.1
d = { d'16 d'16 d'16 d'16 d'4 \arpeggio } % single note
sdf = { s4 d' f'4
Marc Hohl asked:
why lilypond still (at least sometimes) displays stems
You probably haven't enabled no-stem-extend
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Stefan Thomas wrote:
I don't understand why the distance between the barline and the cis
is better if it is a whole note but not, if it is a quarter note.
Well, the whole note has more room because it isn't sharing the measure
with any other notes.
But the barline
Stefan Thomas wrote:
cis cis cis cis | % the sharp sign is too much left!
gis' gis gis gis | % the note and the sharp sign are too much right!
Well, erm, how far do we want to get into fine-tuning?
OK, it looks like you only want one glyph at a time.
fiëé visuëlle wrote:
Would you move the eights in the second measure to the right
or combine the different note heads or what else?
Would you change the stem direction?
I think your specific readability criteria should determine whether
you combine noteheads or change the stem direction
MarcHohl wrote:
Is there a different approach I can use?
If the three-part \fill-line is so dominant,
I suppose you have to cope using ordinary lines.
But \concat and \with-dimensions might make this easier to twiddle:
maintain total \hspace by hand.
matrix = \markup {
Andrew Giddings wrote:
I've searched the manual, the mailing list archive,
and the web, but I couldn't see anything directly relevant.
Did you see these?
http://lists.gnu.org/archive/html/lilypond-user/2007-07/msg00127.html
http://lsr.dsi.unimi.it/LSR/Search?q=semichoirstaff
Tim McNamara wrote:
The first coda glyph should be at the end of bar 28
See LSR 432.Before the \break, add
\once \override Score.RehearsalMark
#'break-visibility = #begin-of-line-invisible
LilyPond won't put the coda glyph at the beginning of bar 31.
At
Convert rule 2.11.23 replaces _any_ break-align-symbol and its symbol
with a break-align-symbols list containing just that symbol.
This is reported in the NEWS as a syntax change.
So presumably break-align-symbols is no more than a generalisation
of break-align-symbol, simply catering
Jonathan Wilkes wrote:
I've tried zigzag-width, thickness [...] but with no results.
These work if you use the zigzag style (which is not built from glyphs).
\override TrillSpanner #'style = #'zigzag
Cheers,
Robin
___
lilypond-user
Patrick Schmidt wrote:
How can I center the text vertically
Texts added as in NR 1.8.1 are kept above (or below) the staff.
You will find it difficult to persuade Lilypond to move these inside.
[And as regards c' c' c' c' c' c' c' see \textLengthOn]
[And afterstencil = ##fsay
Jeroen Heijmans wrote:
But I'm not content with the results.
It fills the page better if you don't zero between-system-space.
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Patrick Schmidt wrote:
is it possible to align the coda signs underneath D.S. al?
Well, this makes the markup narrower
and then you start to see that we had no horizontal centering.
Using a breathing sign instead of a note head makes it easy to
anchor the markup in the middle of the
Torsten Anders wrote:
I really owe you something :)
Well, it's Mark Polesky we both owe.
Without him, all small-time Schemers like me would still be
believing the very plausible explanation in (the 2.12) NR 5.3.4
of why \tweak cannot be used to modify accidentals.
Cheers,
Robin
Trevor Daniels wrote:
it seems like you're suggesting NR 5.3.4 is not correct.
I was talking about the 2.12 NR.
I understood its unqualified cannot to be the well-meaning advice:
- don't waste your time trying.
So I didn't.
But Mark questioned this in July,
and you updated the
Torsten Anders wrote:
Now, there is only a minor flaw now: the distance between a note and
the related accidentals is rather big. In fact, accidentals are more
close to the preceding note than the note they belong to.
I'm way out of my depth here,
but it looks like markup is appending
Torsten Anders wrote:
Lilypond does not know about multiple-sign accidentals, so I
somehow have to create more horizontal space for these manually.
The following code tries to adjust this spacing automatically.
But I haven't tested it with your font.
Have a look at
filled: http://lists.gnu.org/archive/html/lilypond-user/2008-10/msg00516.html
hollow: http://lists.gnu.org/archive/html/lilypond-user/2009-05/msg00593.html
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Torsten Anders wrote:
However, I failed to do the same for chord tones.
Something like this?
%%
tweakAccidental =
#(define-music-function (parser location mkup mus) (markup? ly:music?)
(set! (ly:music-property mus 'tweaks)
(acons 'before-line-breaking
Jonathan Wilkes wrote:
I tried fooling around with tieWaitForNote
You didn't show your code, so it's not easy to guess what you tried.
I have no cross-staff experience, but it looks to me like
the cross-staff run is a lot better supported than
the cross-staff chord (where you have to
Jonathan Wilkes wrote:
I see a cross-staff property for grobs
But this doesn't mean that every sort of grob has it, or uses it.
The file define-grob-properties.scm lists about a dozen grobs which do:
Beam, Stem, Slur, TupletBracket, among others, but not TieColumn.
So your TieColumn
Patrick Schmidt wrote:
is there a way to achieve repeated ties of selected notes of a chord ... ?
This is rather like Nick Payne's LaisserVibrer question in
http://lists.gnu.org/archive/html/lilypond-user/2009-04/msg00313.html
because both are what Lilypond calls semi-ties.
Maybe you
James E. Baileywrote:
for example ə?
Here is a rather inconvenient way:
\markup { X:\postscript # -1 1 scale (_e) show }
\markup { Y:\postscript # 1 -1 scale (_e) show }
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Alex Shanin wrote:
The workaround recommended therein doesn't help.
It probably only worked for collisons with notes, like in the first case,
and not for collisions with things like time signatures and clefs.
You could override the time signature like
\once \override
David Stocker wrote:
Any hints on forcing the arpeggio line to the right
to make the placement more natural would be appreciated.
For the first case, fiddle with the padding.
Negative works too, e.g.
\override Staff.Arpeggio #'padding = #-0.4
For situations where this doesn't work, see
Trevor Daniels wrote:
like this:
And staffName wants symbol? notstring?
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
And staffName wants symbol? notstring?
Sorry; forget that.
The parameter given to \ossia should be #main not #'main
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Denis Roegel wrote:
I am trying to center a markup under a bracket
This was discussed recently here:
http://lists.gnu.org/archive/html/lilypond-user/2009-03/msg00426.html
But, instead of OUHM, you could perhaps do it like the Expressive marks
snippet Center text below hairpin dynamics (cf
Christian Henning wrote:
I'm struggling with sus4 chords.
...
unexpected STRINGsus4
This is notemode complaining.
It is the default input mode:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Input-modes
sus4 is meant only for chord mode.
But note mode is digesting your
Maybe it used to read -\tweak #'extra-offset #'(6.2 . -5.6)
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
lelangir wrote:
Running a search for roman numeral on the one big page
If you don't find things in the documentation,
try searching this mailing list and the snippet repository too.
Have a look at this (the example from Matthew Durell):
Look for swing in the LSR.
http://lsr.dsi.unimi.it/LSR/Search?q=swing
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Tim Walters wrote:
Is there any way to [...] leave the same amount of white space
as would be used if lyrics/chords were present?
This amount can vary.
The vertical space allotted depends on what is being typeset;
e.g. Cm needs less height than Cm7
Based on a discussion last September
A phrasing slur goes all the way.
(Don't ask me why!)
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
David Bobroff wrote:
for some reason the rs of GFirst is coming out italicized as is.
This is because the voltas use the music font
and it has special letters for doing dynamics like sfz and rfz.
The way described in NR.1.4.1. at Text can be included ...
would in your case define markup
Marc Hohl wrote:
This worked fine with ties, but when I try the same with slurs,
it simply shows no difference.
(display right-bound) says
- Tie: #Grob TabNoteHead
- Slur: #Grob NoteColumn
Cheers,
Robin
___
lilypond-user mailing list
Mark Polesky wrote:
Does anyone have a suggestion?
Some time back I chose this missing bracket as a theme for a Scheme exercise.
Nothing revolutionary, just to get some practice in Scheme.
It has the limitations arising from misusing Arpeggio.
I found it needed a lot of different tweaks
flamingspinach wrote:
would it be possible for lilypond to just
recklessly try to modify the file
I imagine it was Risto's post
http://lists.gnu.org/archive/html/lilypond-devel/2008-06/msg00051.html
which tipped the balance in favour of inaction on windows.
I work differently now
Werner wrote:
% innerhalb des score-Blockes („neben“ dem layout-Block)
% Ausgabe einer Mididatei (zum Anhören/Abspielen)
This bit of comment describes how to get Midi and PDF coming out the same.
When you want them coming out differently, you use _two_ score blocks:
- one score block has
Adam Good wrote:
I vaguely remember an example
That would be the 'easy play' noteheads mentioned in NR 1.1.4.
But you probably want something more like this:
cabbage = { c a b b a g e }
\score {
\new NoteNames \cabbage
\new Staff { \clef bass \cabbage }
}
Cheers,
Robin
Jesús Guillermo Andrade wrote:
How can I put it below the chord symbol?
These marks, i.e. RehearsalMark, are normally put above everything else.
This is done by having the corresponding engraver in the Score context.
You can move the engraver down to where your melody is by doing
\layout {
Karenee Herman wrote:
Somehow, the bass line ends up offset from the treble
The second bar of lower should beR2. (for a 3/4 bar).
So it's not really the triplets giving trouble.
please forgive me if this seems simple!
Forgiven.
Cheers,
Robin
For starters,
have a look at these snippets in the LSR:
http://lsr.dsi.unimi.it/LSR/Search?q=coda+segno
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Have a look at LSR 402:
http://lsr.dsi.unimi.it/LSR/Item?id=402
(The \mark command makes a RehearsalMark.)
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
\version 2.12.1
\paper { ragged-right = ##t }
{
f' g'4. s8 \small f' g'4. s8 g' a'4. s8 a' b'4. s8
}
% The augmentation dots are not shifted away from some chords
% when the notehead size is reduced
% this is a regression error (2.10.33 is ok)
Cheers,
Robin
Kalirren wrote:
In general, is it possible to create a laissez-vibrer tie that
lasts a certain length of time, or until a certain note?
Probably not, because IR 3.2.85 [1] says it is
A tie which is only on one side connected to a note head.
You could however make it _look_ longer, but then
Kalirren wrote:
Does anyone know of some other workaround?
It's rather crude, but the following override makes your slur horizontal:
\relative c' {
\once \override Slur #'positions = #'(-3 . -3)
\slurDown e8 ( r16 r8.)
}
Cheers,
Robin
Lewis Overton wrote:
I'm curious about what others are doing to print a scoop
I have an occasional need for this when transposing saxophone parts,
and then I use brackettips as you do/did [1].
I first did such bends in a clumsy beginners way and had to put the
brackettips in a dedicated
Chip wrote:
but no matter what numbers I put in the positions parameters the slur
does not move.
The \once makes this override act only on the c'2 and the c'2 has no slur.
The override acts on the slur if it comes after the c'2,
but it moves the slur vertically; not what you wanted.
Mark Austin wrote:
Is it possible to enclose a note in brackets?
Use \parenthesize
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Inside-the-staff#Parentheses
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Does anyone have an idea why the fourth system is put on the second page
I'm out of my depth here, but if your title is done
the normal Lilypond way, with bookTitleMarkup,
it counts as a system too.
So might the pagebreaker be putting 4 systems on all pages?
And have you tried
Nick Payne wrote:
If I have one note each bar that requires a direction change, then
it's actually simpler to use the \once command,as \stemUp requires
the corresponding \stemDown or \stemNeutral after the note.
I found it quite a disappoinment to discover that apparently
similar things
Boris Lau wrote:
I thought it would be quite natural if this would do the job:
\override Staff.BarLine #'break-visibility = #'#(#t #t #t)
but it doesn't.
Certainly a reasonable expectation.
This is normally #'#(#t #t #f), but there are cases when Lilypond
switches over to #'#(#t #t #t)
Mark Austin wrote:
I'm putting the finishing touches on a book of English folk tunes,
but have a few problems.
I suppose it's rather crude, but I like using \null for things like this.
So, for the footer:
\markup { Engraved ... }
becomes
\markup \fill-line { \null
Carl D. Sorensen wrote:
the markup appeared different when created in what
appeared to us to be two equivalent ways
In the tabClef* markups there is a baseline-skip override
just before the final \column.
But customTabClef is different; it sets baseline-skip via new-props.
If you make
Jonathan Townes wrote:
the use of fingerings would be much faster and require less typing
This nice aspect of fingerings is due to the parser knowing what a
fingering looks like. But this is defined as being a single digit,
so you only have ten things you can ask for (corresponding to 0 ..
Miklos Vajna wrote:
First, currently the output has Bm for my chord,
but actually I would like to have it as 'Bm \super omit3/A'.
Like this? (verbatim)
replaceCN = #(define-music-function (parser location new) (markup?)
#{\once \override ChordNames.ChordName #'stencil =
#(lambda
\version 2.12.1
workaround = \override Arpeggio #'positions =
#(lambda (grob) (interval-widen (ly:arpeggio::calc-positions grob) 0.5))
{
\override Arpeggio #'arpeggio-direction = #DOWN
c' g'4 \arpeggio c' f'4 \arpeggio
% \workaround
c' e'4 \arpeggio c' d'4 \arpeggio % arrow too long
Nick Payne wrote:
the laissezVibrer tie specified in the bass voice also appears
on the two simultaneous notes in the treble voice.
This is because of the names you gave your voices.
They happen to be the same as those automatically chosen by
the { } \\ { } construct.
So at this point
Nick Payne wrote:
Is this possible without faking the chord by creating two voices?
Is this more what you are looking for?
It is not all that easy to use:
- you have to work out the position, e.g. -9, by yourself
- and it won't move when you transpose.
See IR 3.2.84.
Nick Payne wrote:
Is this possible without faking the chord by creating two voices?
Sometimes I like to show in my piano fingering that
one finger of a chord should temporarily act as a pivot
while the other fingers are moving to the the next chord.
Maybe there is a recognised symbol for
Kieren MacMillan wrote:
This function should be good at least as far back as v2.10.
\draw-line was introduced after 2.10.
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Wei-Wei Guo wrote:
I still have no idea how to input some music symbols, such as a short
piece of pure staff, timesignature, keysignature, and so on.
Search the snippet repository for engravers.
In particular, try out the (complete) snippet in
http://lsr.dsi.unimi.it/LSR/Item?id=280
Marek Klein wrote:
I tried it using the commented line, but it didn't work
You can make the cantus more approachable.
Adjust the -2 to taste.
\include gregorian.ly
\score {
\new VaticanaVoice = cantus {
\override Staff.VerticalAxisGroup #'minimum-Y-extent = #'(-2 . 4)
\[
Joe Neeman wrote:
so we move still more text below more text
By all means extend the regression test if it is incomplete
with regard to still more text.
But how is this relevant?
Your illustration shows text and more text ordered in the same
way as inner up and outer up of the current
Ossie Wilson wrote:
I have attached the Ly file
After a cursory look, I would say this file is
badly mangled as regards key signatures.
In part one at bar 29 it helps to say
\key dfinstead of\key cs
because the subseqent notes are e.g. df, gf, ...
Also part one should declare
Roel Spruit wrote::
somehow the order in the output is reversed
That's queer.
With me (2.12) they both read R L from top to bottom.
However, with 2.10 they both read L R from top to bottom.
Are you using an intermediate version? ;-)
Is this suitable as a workaround?
LR = \markup
Kees Serier wrote:
Looks good, but how to use it, I'm only a beginning Lilypond user :-(
I have a vague feeling you may not have received
my reply diagnosing your arabic percent problem:
Kees Serier wrote:
I get Guile errors
GUILE signaled an error for expression started here:
markup
Here is the regression test script-stack-order.ly
in a slightly lengthened version.
\version 2.12.1
\relative c'' { c4^inner up^outer up_inner down_outer down
\repeat unfold 2 c4 }
The assertion Objects specified first are closest to the note.
is false
Neil Puttock wrote:
it's possible to duplicate its code in Scheme:
Or its appearance in markup ;-)
simile = \markup {
\combine \translate #'(0.3 . 1.5) \draw-circle #0.2 #0 ##t
\combine \translate #'(1.7 . 0.5) \draw-circle #0.2 #0 ##t
\rotate #90 \translate#'(0 . 2) \beam #2 #-1 #0.5
Kees Serier wrote:
I get Guile errors
GUILE signaled an error for expression started here:
markup #
:bold #:fontsize 1 #:char #x066A
Well, it works at my end. Something is corrupted.
My best theory is that your version now ends
#'stencil = markup #:bold #:fontsize 1 #:char
Nick Payne wrote:
What I want is the fingering just to the left of the notes
and the arpeggio just to the left of the fingering.
I'm pretty sure you ought to change the order in which
these things are hung onto the side of the notes.
But I'm afraid I can't help you with that.
As regards
Trevor Daniels wrote:
I prefer to use Unicode hexadecimal value.
There are too many sorts of Unicode hexadecimal values
for this to be reliably unambiguous.
I think the hexadecimal bit is a red herring
and only needs mentioning once, as in:
where is the hexadecimal code for the
Trevor Danielswrote:
I prefer to use Unicode hexadecimal value.
There are too many sorts of Unicode hexadecimal values
for this to be reliably unambiguous.
I think the hexadecimal bit is a red herring
and only needs mentioning once, as in:
where is the hexadecimal code for the
Kees Serier wrote:
but it is the normal percent sign with open zeros,
where the repeat sign has filled zeros
Yes, well, those repeat signs are site-mixed as it were,
and I have no idea how to persuade the contractor to do
an unscheduled job in unfamiliar surroundings.
But I did find
Where NR 3.3.3 is talking about \char it says
The following example shows UTF-8 coded characters being used
which got me typing in a UTF-8 byte pair after the ##x.
But, of course, it is more like UTF-32.
In fact, referring to UTF-32 would make it easier
to google for these high code
Francisco Vila. wrote:
the right googleable word is Unicode, do you agree?
Well, not fully.
When I google for unicode arabic percent
I certainly end up at a relevant place
http://www.fileformat.info/info/unicode/char/066a/index.htm
But I am not done.
I need to collect whatever it is \char
Francisco Vila wrote:
Does \char accept full hex Unicode code points
or rather variable-length utf-8 multibyte characters?
In the source for 2.12.1
the \char markup definition at define-markup-commands.scm line 2423
calls ly:wide-char-utf-8 at general-scheme.cc line 271.
This routine is
Kees Serier wrote:
I want to have the percent sign for a duplicate chord
in the next measure (in \chordmode).
I don't know how particular you are. Would this be good enough?
percentCN = \once \override ChordNames.ChordName #'stencil =
#(lambda (grob)
Benjamin Smedberg wrote:
the tr mark is still there.
Yes, you can't easily tell how near you are to getting it right.
Try
\override TrillSpanner #'(bound-details left text) = ##f
Cheers,
Robin
___
lilypond-user mailing list
Chip wrote:
it just resulted in messed up measures
A judicious use of time distortion may help you here.
\transpose c c'{
\hideNotes g,32\glissando \unHideNotes c'4*7/8 c'4 c'4 r4 |
\hideNotes c''32\glissando \unHideNotes c'4*7/8 c'4 c'4 r4 |
a1*3/4\fermata \hideNotes d'4\glissando
Hu Haipeng wrote:
I don't know whether this gives two stems
No, it doesn't.
It is just a chord, and a chord (in one voice) has only one stem.
In this case the still active \stemUp makes its stem go in a
different direction to the following \stemDown notes and so the
accompanying
Stefan Thomas wrote:
I can't reduce the distance between the TimeSig and
the first Staff of the Score. How can I do it?
Um, - don't override max-stretch?
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Robin Bannister wrote:
As addBrackets it wrapped only a single chord, but you could
derive a left_only and a right_only version easily enough.
I wanted to see if I could make such a pair deliver something close
to what the OP illustrated, and managed this using \put-adjacent.
This itself
Tim McNamara wrote:
Rather than writing a separate ending, I'd like to just parenthesize
the last three chords over the final two bars so they would render:
F(Ab7Dbmaj7C7)
ChordName outputs via text-interface, so the easiest way should be
\once \override
Joseph Haigwrote:
I get the text under the fermata. How can I force it above?
Use
\once \override Script #'script-priority = #-100
as mentioned in Controlling the vertical ordering of scripts in NR 1.3.1.
Cheers,
Robin
___
lilypond-user
Kees van den Doel wrote.
on 2.12.2 it does *not* work. The output is attached. Bug?
It seems to me that LSR 258 is demonstrating only whiteout.
It is not demonstrating how to deal with the concomitant
horizontal layout problems, because it cheats here:
- uses ragged-right = ##f (with only
Mats Bengtsson wrote:
try to nail down which conversion rule
The rule for 2.1.27 (re tuning) prints this.
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Tim McNamara wrote:
Is there a correct way to do this that I haven't been able to figure out?
No. Not yet.
But see the recent thread at
http://lists.gnu.org/archive/html/lilypond-user/2009-02/msg00028.html
Cheers,
Robin
___
lilypond-user
Chip wrote:
Lily still breaks lines where it wants to.
You are fighting something very powerful and don't know it.
All that blank space on those pages!
It is reasonable to think that saying \pageBreak means that you
are quite happy with whatever blank space is needed to skip the rest
of
Thomas Scharkowski wrote:
Since Lilypond 2.11. this does not work anymore
I have a lot of single sheets based on a 2.10 template which ensured
I had enough vertical space for pencilling in fingering.
The vertical spacing rework in 2.11 gave me the same problem.
This is probably to do with
Nick Payne wrote:
I couldn't find anything in the documentation.
This comment in the rest collision source code might be relevant.
TODO: look at horizontal-shift to determine ordering between rests
for more than two voices.
So maybe you just have to ignore it?
Or do something like this
Zbyněk Burget wrote:
Splitting it onto two lines is unavailing. Therefore i want way to expanding
width of
this line.
The default layout puts poet, instrument and composer all on one line.
This is not compatible with the length of your composer text.
Even if instrument is unused, its
Zbyněk Burget wrote:
How I can write long text to composer to header?
Try
composer = \markup \right-align Some long text ...
If this isn't what you want, have a look at NR 3.2.1 where
the demo splits the composer text onto two lines using \center-column.
Why don't hide TimeSignature?
I
Jayaratna wrote:
This does not seem to work:
{\stemUp c2^~ c4}\\{\stemDown g4 \stemUp a4_~ a}
Well, this looks like (part of) what you want!
Or is it that you then don't see how to cope with the d2.?
The manual mentions connecting ties across voices
( Snippets / Rhythms / Making an object
Carl D. Sorensen wrote:
Please file a bug report
Already started, now done.
http://lists.gnu.org/archive/html/bug-lilypond/2009-02/msg00014.html ?
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
401 - 500 of 570 matches
Mail list logo