alistair zaldua skrev:
I was curious to know whether it was possible to set up and define a percussion
clef from scratch.
Read the section about Percussion staves in the manual (section 7.4.3 in
stable version)
-Rune
___
lilypond-user mailing
Stefan Thomas skrev:
then no natural sign will be printed before the c,
How can I change it?
\set Staff.autoAccidentals = #'(
Staff
(same-octave . -1)
(same-octave . 0)
(any-octave . 0) )
-Rune
___
lilypond-user
Stephen Lavelle skrev:
So { c cs cs c } would, when rendered, have a sharps on the two middle
notes, and a natural on the fourth.
Something like this:
\version 2.10.20
myAccidentals = {
\set Staff.autoAccidentals = #'(
Staff
(same-octave . -1)
(same-octave . 0) )
}
Rune Zedeler skrev:
Something like this:
Btw, notice that this will probably break in 2.12 - but will be easily
repaired.
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Stephen Lavelle skrev:
(after remembering to put it in each voice)
Ofcourse, if you want it globally, you can do the setting once and for
all in the layout-block:
\version 2.10.20
\layout {
\context {
\Staff
autoAccidentals = #'( Staff (same-octave . -1) (same-octave . 0) )
Kevin Partington skrev:
http://www.nabble.com/file/p15998012/drum.ly drum.ly
You have:
\new DrumVoice = 1 { s1 *2 }
\new DrumVoice = 2 { s1 *2 }
You need to change the spacings to last for the whole duration of the
piece. If you have 20 measures, write s1*20, etc.
If you do not then
Graham Percival skrev:
moltorit = ... scheme that prints out molto rit, and tweaks
whatever options you want for your new midi code...
That won't work.
If I read the rules of the artemis context correctly, the solution must
work for any lilypond file.
I assume that the organizers are using
I have added a snippet that sets the beam grouping automatically.
Needs loads of cleanup, but works.
http://lsr.dsi.unimi.it/LSR/Item?u=1id=395
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
How do I move the text script below the cresc spanner?
Setting script-priority do not work.
\relative c'' {
f^\ g^Flying! c f\!
}
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Rune Zedeler skrev:
\relative c'' {
f^\ g^Flying! c f\!
}
Whoops forgot to attach image.
-Rune
inline: test.preview.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Mats Bengtsson skrev:
See section Vertical collision avoidance in the 2.11 manual.
Ah thanks!
Perhaps we should think about a better name for that section.
The title is correct - it describes how lilypond internally avoids
vertical collisions. But when you do not see a collision on your score
Mats Bengtsson skrev:
Or at least, add a see also 5.5.5 Vertical collision avoidance from
1.8.1.2 Text scripts.
I think that would do it, actually.
Then, you should add the corresponding links from all other
objects that appear outside staffs,
I don't agree.
Section 1.8.1.2 talks about how
Rune Zedeler skrev:
Section 1.8.1.2 talks about how to order scripts vertically.
Sorry, I was reading section 1.3.1.1 Articulations and ornamentations
thinking that I was reading 1.8.1.2.
Silly me.
In 1.3.1.1 we have The vertical ordering of scripts is controlled with
I think
Rune Zedeler skrev:
In 1.3.1.1 we have The vertical ordering of scripts is controlled with
I think that from /this/ explanation it would make sense to make a
reference to 1.8.1.2. Sorry for the confusion.
AAARGH, to 5.5.5. Good night. :-)
-Rune
Han-Wen Nienhuys skrev:
This is pretty obvious for single-voice notes; for chords it gets
hairier: which part of the chord notes do we use to decide this?
I think we should look at both top notes and bottom notes. We should
only make the beam horizontal if they agree that the pattern is
Ledocq-Boccart wrote:
By the way...what are these skills precisely?
The Feta font has been made in METAFONT.
See the .mf-files in the source.
http://metafont.tutorial.free.fr/
___
lilypond-user mailing list
lilypond-user@gnu.org
Citat Mats Bengtsson [EMAIL PROTECTED]:
- In Accidentals, I wouldn't refer to Nordic and Germanic languages,
since both Swedish,
Danish, Norwegian and German use -iss and -ess (admittedly the
same concept, but
a different spelling).
This is not correct.
In Danish we do not use -ss at
Ole Schmidt skrev:
thank you very much, now I understand how it works- unfortunatly I need
the note to be tied ~ like below
Hmm, that's a bug. I have reported it on the bug-list.
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
Ole Schmidt skrev:
is it a normal behaviour that the \clef percussion transposes like in
the following snippet?
It does not transpose. It behaves like a C clef.
What did you expect?
Did you read the section about percussion notation in the nr?
-Rune
Ole Schmidt skrev:
when I compile the following snippet I get what you can see in the pdf...
It does not transpose. It behaves like a C clef.
Yep.
As I said, it behaves as a C-clef (having central c on the middle line).
If you are using a tuned percussion instrument then you should not use
Citat Stefan Thomas [EMAIL PROTECTED]:
I've read Your messagea concerning the new accidental style and I
must say, this is exactly what I'm searching for. Could this problem
be solved? Or have You found another solution for Yourself?
We are working on a solution.
It will hopefully (and
Citat Stefan Thomas [EMAIL PROTECTED]:
could You be so kind to tell me, what this dev/rune from git means?
At the moment, I don't understand the meaning of it.
In this case unfortunately I don't think you will be able to use this approach.
You will need to be able to build lilypond yourself,
Kieren MacMillan skrev:
Maybe you mean G#m(add9) which is a minor chord with added ninth.
gs:m5.9/ds
I do not really like that the 5 must be there.
Not a bug, but definitely a missing feature.
-Rune
___
lilypond-user mailing list
Stefan Thomas skrev:
\score { \clef bass
\Stefan { c d e } \Stefan { d e f } \Stefan { e f g } }
Oh, sorry, that does not work. I should have seen it in the previous mail.
But it has nothing to do with the transformations being used.
If you try to just do
\score { \clef bass c' d' e' f }
Then
Valentin Villenave skrev:
In the LSR? Might be worth giving it a shot. I uncommented the code,
so users can see the full Prelude if they want to (besides, it's cool
to finally use the Large Snippet feature once in a while).
Dear valentin, Please test your code before you publish it to the
Stefan Thomas skrev:
as far as I understood this topic, one must have experiences with
writing programs.
Not at all.
But one of the great things about lilypond is that /if/ you do have
experience with writing programs then you can take the experience to a
whole new level.
The topic of this
Stefan Thomas skrev:
thanks for Your fast answer, but I think this stuff is a little bit
to complicated for me, at least at the moment.
Yeah, this is one of those old snippets that has been modified over time
as the lilypond syntax was changed - getting more and more messed up as
different
Thomas Scharkowski skrev:
is it possible to produce horizontal beams somehow?
\override Beam #'damping = #10 does not work, as already reported
last year:
The value #10 is not big enough
Try
\override Beam #'damping = #+inf.0
:-)
-Rune
Valentin Villenave skrev:
Gosh... the point is, my computer is broken (again) and I really had
*no* way to check the code.
Sorry. I forgot.
Thanks to your thorough work, I'll correct it right now. If I may ask
you one more favor, can you please check what *exactly* was messed up?
Probably
Valentin Villenave skrev:
scroll down to music-box.ly
Absolutely; you might as well have mentioned the LSR implementation of
the same trick:
http://lsr.dsi.unimi.it/LSR/Item?u=1id=289
I searched to LSR for music-box, and as it didn't show up anything I
assumed that the snippet had not been
Kieren MacMillan skrev:
\version 2.11.33
\paper{ ragged-right=##t }
drumStuff = \relative
{
\override TextSpanner #'dash-fraction = #1
\override TextSpanner #'bound-details #'left #'text = \markup {
\musicglyph #scripts.open \hspace #0.2 } c'4 c c c |
c\startTextSpan c c c |
stefan thomas skrev:
Dear lilypond-team,
I think I have a rather simple question, but I can't solve it by myself.
How can I move an ottava-bracket?
To move it upwards, insert
\once \override Staff.OttavaBracket #'padding = #2
before the #(set-octavation 1)
Replace #2 with a value of your
Graham Percival skrev:
I wouldn't be opposed to adding a
% added in 2.8.6
comment to snippets, though.
Will the original version be available somewhere, or is it lost forever
as soon as the convert-ly has been run?
If the original is lost I do not see a need for a comment on when the
Graham Percival skrev:
That's why we want a user to volunteer to check the regression tests. It
takes about 15 minutes a month, but it would drastically improve the
stability of lilypond.
Not all regressions are caught by the regression test. For instance we -
for obvious reasons - have no
Valentin Villenave skrev:
-- First rule of LSR is: do not add a \version line.
-- Second rule of LSR is: do NOT add a \version line.
What is the reason for this?
The version line might be good information to have - at least in a
comment. If a snippet stops behaving correctly, the
Mats Bengtsson skrev:
Regarding information on the original author, this would certainly be
useful
for the LSR maintainer, but there are also good reasons not to publish
names
on a public web page, at least not with an email address.
Of course we should not automatically publish real names
Ole Schmidt skrev:
I want to have both of the first two notes tied -the d and the f-sharp.
How do I achieve that?
The problem is, that the Tie_engraver - that generates ties - lives at
voice level. That means that the Tie_engraver can only see notes in
the same voice - and therefore cannot
Henk van Voorthuijsen skrev:
In chordmode I am trying to get g bes es in some kind of spelling
What's wrong with \chordmode { es/g } ?
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Father Gordon Gilbert skrev:
My question is this: As I arrange this, I want to have the chords I am
creating displayed
I am not sure I understand.
Something like this?
%%% BEGIN %%%
\version 2.10.0
sop = { g' a' }
alt = { e' f' }
bas = { c' d' }
{
\new ChordNames \sop \alt \bas
(going back on list)
Ben Fagin skrev:
I've revised my implementation to set up
variables using the make-pitch function instead of variables and it
works now. Thank you!
Now that I think about it, you do not have to use make-pitch. You can
extract the pitch information from a note, like this:
Ben skrev:
I thought I had this figured out, but now I'm stuck. My program generates midi
notes and converts them to lily variables (ie noteone = {ees'} ). What I need to
do next is add my durations onto them. It seems so simple but I get error after
error.
I don't understand what you are
Graham Percival skrev:
It's only fixed in 2.11, not 2.10.
I applied the 2.11 fix on the 2.10 branch. When (if) 2.10.34 comes out,
it should be fixed.
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
I am working on splitting the pitch into pitchclass and pitch. -
Pitchclasses not containing octave information.
I am not nearly finished with this, and perhaps the whole thing will be
rejected.
But I think it would be a shame to do a lot of work on the Pitch
documentation just before a change
[EMAIL PROTECTED] skrev:
Thanks for the suggestion, but glissandi go between the two notes,
whereas I'm needing the line to be above or below - exactly where a
slur would be.
I find it a bit difficult to understand what you want. Is it something
like this?
%%% BEGIN %%%
\new Staff \with {
Rune Zedeler skrev:
\hardbar ||
(And btw don't think it would be possible with current lilypond)
Well, inspired by Mats' latest post, I see that it indeed is possible:
%%% BEGIN %%%
increaseBarNumber = \applyContext
#(lambda (x)
(let ((measurepos (ly:context-property x 'measurePosition
anders stenberg skrev:
I'll nead to get the freet- numbers in TAB changed to
letters (a = 0, b=1, c=2, d=3, e=4, f=5, g=6, h=7, i= 8, k=9, l=10
et.c.).
http://lsr.dsi.unimi.it/LSR/Snippet?id=331
-Rune
___
lilypond-user mailing list
Rune Zedeler skrev:
http://lsr.dsi.unimi.it/LSR/Snippet?id=331
Whoops, what I meant was
http://lsr.dsi.unimi.it/LSR/Item?u=1id=331
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
steve berthiaume skrev:
\bar :| %this repeat won't show up
\break
\bar |:
\bar :|: \break
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Sandeep Gupta skrev:
I am trying to, for instance, show the accidental on the second a-sharp below.
...
\cadenzaOn
http://lsr.dsi.unimi.it/LSR/Item?id=327
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
Ted Walther skrev:
Rune, can you update your free meter code? I'd like to do this:
\hardbar || or \hardbar | and have it do the right thing, instead of
making a new function for each different type of barline.
I really do not see the need for this.
(And btw don't think it would be possible
Valentin Villenave skrev:
I am certainly not committing anything; Rune might be, but his current
work on the accidental code will probably change the whole thing in
weeks.
No I probably won't. I think having the example in lsr is enough.
If we were to include it in the distro officially we
Valentin Villenave skrev:
OK, it's corrected.
Sorry for the noise.
The snippet did not work with grace notes. (Am I the only one who think
that the representation of grace timing is a bit messy?)
Try with this:
%%% BEGIN %%%
increaseBarNumber = \applyContext
#(lambda (x)
(let
c.m.bryan skrev:
I'm working on a score where I am in cadenza mode, and inserting bar
lines manually (\bar |). It seems that accidentals don't reset
automatically on these barlines, i.e. a sharp isn't reprinted in the
next bar. Is this the intended behavior, and if so, is there any way
I can
Valentin Villenave skrev:
Thanks for the snippet Rune.
You're welcome
Approved (a few typos fixed, and HTML tags added).
Thanks.
Unfortunately I cannot modify the snippet after you approved it.
There was a bug in it so accidentals worked correctly but printed bar
numbers did not.
Will
Valentin Villenave skrev:
the SDPE!
(Smallest Documentation Project Ever -- it works with Silly too, for
what it's worth).
LOL :-)
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
After we dropped the Cello-Woman, we haven't really had a logo.
I suggest to use Valentin's happy LilyPond-note as a logo. I could start
arguing a lot, but hope that it won't be nessesary. The note is just
brilliant.
Comments?
http://valentin.villenave.info/lilypond/music_expression.png
Citat Valentin Villenave [EMAIL PROTECTED]:
Rune: I think it's possible with some JScript tweaking (at least, some
buzzword-compliant technologies allow to do this without frames).
Maybe. I have just never seen it.
Javadoc still uses frames, and about everything else I have encountered reloads
Graham Percival skrev:
LIMITED DISCUSSION
To keep discussion focused and as un-confused as possible, this is a
discussion *only* about the arrangement of subsections. Other parts of
GDP will be discussed later.
This means:
- propose new/changed chapter/sections
- propose renamings of
Citat Graham Percival [EMAIL PROTECTED]:
Just one general comment for the moment: I'd rather propose longer than
shorter subsections. I think that there already is too much fragmentation
at some places for the moment, which means that you never get the chance
to see the full picture as a
Graham Percival skrev:
Well, don't I feel like a complete newbie. :/Does anybody know how
to make Thunderbird treat text like pure bloody text, and not change the
displayed text when it sends an email out? thanks in advance. :(
I don't know what you did wrong.
I just copypasted the
Trevor Bac(a skrev:
As a first pass, I took a look at chapter 8 Advanced notation,
because I've never been very comfortable with the distinction between
basic, advanced and contemporary notation in the current
structure.
It seems like your comments are meant to the online 2.11 documentation,
Very first I comment on the stuff I wrote below: When I wrote it I
didn't really notice / think about the fact the the first five sections
are left out. Probably some of my comments are not totally valid. Well,
I will think some more, and post another message about the overall
structure of the
Graham Percival skrev:
I'm pretty certain that we won't have any stable releases for the next
two weeks, and 2.12 will be coming out soon after that. Therefore I
don't think it's worth re-opening this bug.
It worked in 2.8 so it is a regression.
Therefore I definitely think that it should be
David F. Place skrev:
1.) accidentals before every note (including naturals)
2.) transposition without creating a key signature
%%% begin %%%
\version 2.10.0
webernAccidentals = {
% the 5s are just a value different from any accidental
\set Staff.keySignature = #'((0 . 5) (1 . 5)
Citat Valentin Villenave [EMAIL PROTECTED]:
Here's my snippet; it's more detailed than the other one, but since
English isn't my native language, if someone can rewrite it somehow it
should get much better.
http://lsr.dsi.unimi.it/LSR/Item?u=1id=314
How do you manage to link to snippets so
Citat David F. Place [EMAIL PROTECTED]:
That does work, but it makes lilypond print a warning for every note.
Are you sure that you removed the key_engraver as specified in my snippet?
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
Citat Kieren MacMillan [EMAIL PROTECTED]:
Is there any way to have \RemoveEmptyStaffContext in a layout, but
specifically choose one Staff (or, better yet, section of measures of
a Staff) that would still display regardless of content?
Untested: Why not simply add an invisible note to each
Quoting Tao Cumplido [EMAIL PROTECTED]:
\key c \major
\transpose c a { music }
Should have been
\transpose c a {
\key c \major
... music ...
}
-otherwise the key signature would not be transposed.
-Rune
___
lilypond-user mailing list
Quoting Vasil Kadifeli [EMAIL PROTECTED]:
And by the way, is there a way to play the tunes from a *.ly* file ?
Yep, if you add a midi-block to the score, lilypond will create a midi-file that
you can play.
Read section 10.3 in the manual.
-Rune
Quoting Han-Wen Nienhuys [EMAIL PROTECTED]:
\paper {
blot-diameter = 2 \pt
}
Unfortunately it does not work with bar-lines, though.
Oh, but you could simply add
\override Score.BarLine #'thickness = #100
problem solved :-)
I am not really sure whether this was a joke, sorry.
(Was
Hehe, I found out there is a really simple solution of how to make stems
look nice in acroread.
In all its simplicity, add
\paper {
blot-diameter = 2 \pt
}
:-)
Now all stems appear to have same thickness in acroread.
Unfortunately it does not work with bar-lines, though.
-Rune
PabloZum skrev:
but D13 appears as D9/add13.
That looks like a bug.
I'll report it.
For now you can use d:11.13
What to do for A7b9?
a:9-
There should be a list somewhere, like:
I agree.
http://lilypond.org/web/devel/participating/documentation-adding
:-)
-Rune
Steve Schow skrev:
I use ghostscript to produce overture and finale PDF's
which look spectacular on screen on windows.
Would you please post a small pdf created by finale, so that we have
something to compare?
-Rune
___
lilypond-user mailing
Steve Schow skrev:
Ok, here is a short example.
snip loads of jpegs
Would you please post a /pdf/ (or ps)?
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Okay, I took a look.
I understand why the viewers have problems with lilypond's pdfs: For
some reason lilypond does loads of conversions to and from millimeters.
I think it has something to do with lily defining one point to be
1/72.27 inch, whereas a postscript (and pdf) point is 1/72 inch.
Rune Zedeler skrev:
I understand why the viewers have problems with lilypond's pdfs: For
some reason lilypond does loads of conversions to and from millimeters.
Oh, I never learn not to post comments late at night.
The above really had nothing (afaics) to do with the problem.
It should
Kieran Coulter skrev:
This one really has me stumped! I've tried everything, and the file
refuses to either a line or page break at the end of the 2nd last page
of the included pdf.
You have an error in one of the measures before - so the pageBreak
command is located not at the exact point
Neil Puttock skrev:
Unfortunately that's even worse - it produces output similar to what I
posted above, but with hemidemisemiquaver barring.
Yikes.
For now you can use
\once \override Beam #'gap-count = 3
c32.*4[ e32.*4]
which is also an ugly kludge though :-/
-Rune
Quoting Ziggy Leitner [EMAIL PROTECTED]:
I have spent a bit of time trying to get the beams for a
DrumStaff to stay parallel to the staff line instead of
following the stem.
Try reading the sections on tablatures. It contains some notes on how to make
the beams horizontal. The same
sdfgsdhdshd skrev:
In this link, i read how many systems you want before each fragment.
What does system mean? This word is present several times in the main
lilypond doc, but i can't figure its meaning related to lilypond.
Read the glossary, that can be found from the main documentation page
Romel Anthony S. Bismonte skrev:
Now, it would be nicer for the segue markup to be right-aligned to the
page, so I tried changing the markup to this:
Use fill-line for this.
\markup {
\fill-line {
\column {
\italic segue to
Something Else
Valentin Villenave skrev:
but I already made it
clear that in an independent \markup the text formatting *is* relative
to the entire page, so you can't say it isn't.
This is not true.
In this example, the text ends up in the left margin.
%%% BEGIN %%%
\version 2.10.25
{ c d e f }
\markup {
Trevor Bac(a skrev:
I'm picky about the spacing. So I want noteheads to align *vertically*
(between systems).
And I also want all barlines to align vertically between systems.
As Mats suggests: Use a multistaff-score.
%%% BEGIN %%%
\version 2.11.25
\include english.ly
\layout {
indent =
Eric Knapp skrev:
I want the numbers 7, 7, 3, 5, 3, and 5 to be the same vertically.
Lily has hugeproblems with vertical alignment - it usually takes a lot
of hacking.
In your case, the easiest is probably to put the numbers into a
lyrics-context:
\new Staff {
\set
sdfhsdfhsdfhs skrev:
I did not find anything in the forum about it.
Did you read manual section 10.1.4: Multiple scores in a book?
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Rune Zedeler skrev:
But what you /can/ do is to use a StaffGroup and then make the span bars
transparent apart from at the end of the measure
You could also automatically make single bars (|) invisible but still
show all other kind of bars - like this:
\version 2.10.25
mus = { \clef F c d
Dewdman42 skrev:
Hi everyone. I can't seem to figure out how to make a square looking group
bracket.
I also can't seem to figure out how to put a staff group bracket around only a single staff.
This is a bit weird, but I cannot find a way to solve both your problems
simultainously.
The
Steve Schow skrev:
Here is what I used for first two staffgroups in one system and I have
attached resulting image.
You made a simple typo that is why it did not work:
\new StaffGroup
\override StaffGroup.SystemStartBracket #'style = #'bar-line
\override
Rune Zedeler skrev:
\new StaffGroup {
\new Staff {
\override StaffGroup.SpanBar #'transparent = ##t
\clef F c d e f c d e f \bar |.
\revert StaffGroup.SpanBar #'transparent
}
\new Staff {
\clef F c d e f c d e f
}
}
Sorry, a typo.
Try this:
\new StaffGroup
Morten Lemvigh skrev:
Is it possible to connect the bar lines of different staffs on the very
end of a piece using ChoirStaff?
No because a ChoirStaff contains no span bars.
But what you /can/ do is to use a StaffGroup and then make the span bars
transparent apart from at the end of the
Germain G. Ivanoff-Trinadtzaty skrev:
Hi,
In the following code:
before = 14
after = 10
\markup { \with-dimensions #'(0 . 0) #'(-10 . 14) AZERTY }
The easiest is probably to use explicit cons instead of the shorthand
'-notation:
\markup { \with-dimensions #(cons 0 0) #(cons (- after)
\version 2.10.25
\layout {
\context {
\GrandStaff
\accepts RhythmicStaff
}
}
\new GrandStaff
\new Staff { c'4 }
\new Staff { c'4 }
\new RhythmicStaff { c'4 }
\new RhythmicStaff { c'4 }
-Rune
___
lilypond-user mailing list
Francois Planiol-Auger skrev:
I would be pleased to know how to put more short fragments on one line,
\version 2.10.25
musa = \markup \score {
{ c d e f }
\layout{ ragged-right = ##t }
}
musb = \markup \score {
\new Staff { c' d' e' f' } \new Staff { c' d' e' f' }
\layout{
Francois Planiol-Auger skrev:
Thanks. Unfortunately, it doesnt work well.
Ich just copy-pasted this source. The result ist not on a line but every
fragment is under the last.
I use 2.10.20
That is weird - it works fine here (2.10.25).
Can others reproduce?
Otherwise I suggest you update to
Francois Planiol-Auger skrev:
I upgraded, but it is the same.
This is sooo weird.
What do others say?
Anyone?
-Rune
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Adam Good skrev:
and here's what I use in Lilypond to show that key signature:
\override Accidental #'glyph-name-alist = \makamGlyphs
\override Staff.KeySignature #'glyph-name-alist = \makamGlyphs
\set Staff.keySignature = #'(
(1 . 4/9)(-3 . 4/9)(3 . 1/9))
You do not
Germain G. Ivanoff-Trinadtzaty wrote:
Thank you Rune,
You are welcome.
% Here, the 'title' is output _almost_ at the center of the page
% (with a little shift to the right) while the 'index' is put
% 'gap' spaces away from 'title', on the left side.
Oh yeah, you are right.
This
Sorry I missed the simple solution.
This one REALLY should work :-)
\version 2.10.1
\header
{
myIndex = No 210
myGap = #8.0
myTitle = |AZERTYUIOP|
mySubtitle = |AZERTYUIOP|
title = \markup {
\override #`(word-space . ,myGap)
\line \large {
Germain G. Ivanoff-Trinadtzaty wrote:
ragged-bottomto stretch down all pages
ragged-last-bottom to stretch down last page
ragged-rightto stretch right all systems
Is there a way to stretch all systems right BUT the very last one ?
ragged-last
(It's in section 11.5.4 of
Germain G. Ivanoff-Trinadtzaty wrote:
. I want to get title and subtitle centered on the page,
while index is placed on the left of title.
. I could not place index at a _fixed_ position from the _variable_
position of title's first character.
\version 2.10.1
\header {
thetitle = This is
1 - 100 of 241 matches
Mail list logo
