On Tue, 5 Oct 2021 at 10:51, Lukas-Fabian Moser wrote:
>
> Thanks for that explanation, which goes on the heap of things I have to
> try to wrap my head around. :-)
Hello,
We have just had the question on the French list and from what I see the
documentation still mentions \skip 1 and is less go
hoping that this would meet my needs and that
I could replace the code snippets I currently use to format "Da Capo" and
other such indications that currently require the use of the
multi-mark-engraver that is not included in LilyPond).
Many thanks for taking the time to answer me and especially for developing
LilyPond to such a high quality.
Best regards,
Xavier
--
Xavier Scheuer
Hello,
While replying to a query on the French-speaking list I realized that in
the latest versions of LilyPond the instrumentCueName property was
considered deprecated (as well as the engraver
"Instrument_switch_engraver", the grob "InstrumentSwitch" and the music
functions instrumentSwitch and a
ackage cfr-lm does provide LatinModern
monowidth typewriter italic, bold and bold italic.
https://ctan.org/pkg/cfr-lm
Cheers,
Xavier
--
Xavier Scheuer
On Tue, 25 May 2021 at 19:36, Werner LEMBERG wrote:
>
>
> Please have a look at
> https://gitlab.com/lilypond/lilypond/-/issues/6142
>
> Is there a workaround?
Hello Werner,
\once \override Score.MetronomeMark.X-offset = #5
works in this case.
Cheers,
Xavier
--
Xavier Scheuer
could trigger some discussions for LilyPond as well, I think.
Cheers,
Xavier
--
Xavier Scheuer
Cheers,
Xavier
--
Xavier Scheuer
> boolean values but also the symbol 'if-text.
>
> I chose the name tempoShowParentheses instead of tempoHideParentheses
> because this property also allows parenthesizing text-less
> MetronomeMarks.
>
> Contains regtests.
>
> Please review this at https://codereview
On 26 June 2017 at 09:32, Xavier Scheuer wrote:
>
> Hello,
>
> Sorry, I come after the push.
>
> A. In order to give this nice and long-wanted (also by users other
> than me) feature some visibility, could it be documented in the
> Notation Reference as well (NR 1.8.3 F
--
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______
> Testlilyissues-auto mailing list
&g
ectively for tabular numbers,
superior numbers, stylistic alternates, etc.?
Thank you Jay, you are adding nice and useful features to lily!
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e I need to do there. Thanks.
Thank you very much Jay for working on this.
I have used your code for many years and it works really great.
It is really nice to see it coming into lilypond.
Thanks again.
Cheers,
Xavier
--
Xavier Scheuer
__
oogle.com/p/lilypond/issues/detail?id=3978
Is there something to modify in the make-dynamic-extra function
in order to make it centered on the dynamic again?
So that the "mp dolce" and "più f" indications in my scores are
correctly aligned again with latest lily version.
Thank
google.com/p/lilypond/issues/detail?id=1494
http://code.google.com/p/lilypond/issues/detail?id=1388
Maybe this could be added as a special Google Summer of Code project
(in the spirit of Google free webfonts), or some kind of
Kikstarter(-like) project?
Cheers,
Xavier
--
Xavier Scheuer
_
ng pitch"?
The shape of a slur c( f) is different from slur g( f) , so should be
the broken version. If so, why not a command like LaTeX \phantom?
\phantom { c( } f) d( \phantom { c( }
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel maili
is is
now one of the most starred issue of the tracker (many French users
would like this).
http://code.google.com/p/lilypond/issues/detail?id=3166
Otherwise, yes, I think this is a bug but I think Mike is already
taking care of it (IIUC last mails about skylines etc.), with the help
of David and Kei
u use existing "break-alignable-interface",
"break-aligned-interface" and "break-alignment-interface" and
*expand* a property like "break-align-symbols" to support grobs like
NoteColumn, NoteHead, Stem, StaffSymbol, XYparent, etc.?
\override LyricText #&#x
urprises for 2.18 as well, but that
> does not mean that we should not strive for the best 2.18 we can
> deliver while the game is still on.
Very nice!
Thank you and good continuation.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
d snippets from the LSR
beats by far this "barline issue".
And since IIRC these are both 2.17 "improvements", I expect "surprises"
from users to come frequently again when 2.18 will be released.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
trument parts
with lots of MMR and tempo indications still needs careful thinking).
Since it seems "single Whole Measure Rest" and "compressed MMR"
are usually treated similarly, sorry for the noise.
Thank you for your consideration.
Cheers,
Xavier
--
Xavier Scheuer
___
ary 2013 01:37, Thomas Morley wrote:
>
> BTW, you could print the MultiMeasureRestNumber on a "single Whole
> Measure Rest", too:
>
> { \set restNumberThreshold = #0 R1 }
Yes I knew that (and already used it).
One point in favor of the fact that "single Whole Measu
grobs to handle these two
with different properties settings ?
Thank you for your attention.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
,
hence before submitting a feature request to bug-lilypond, I would like
to know your thoughts about this.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ml
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
tp://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00019.html
Should Trevor's report be added to the tracker?
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ur should be changed accordingly.
But only the figures. Accidentals, +, etc. should not be taken into
account in the "centering", contrary to Bertrand's first "workaround".
If someone possessing a reference book could confirm this, th
take more horizontal space
than with 2.15.7, but still less than a whole note!
Could you make full measure rests take as much horizontal space as
the equivalent note for every measure/FMR duration?
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
whole-measure-rest-horizontal-space.ly
Desc
On 23 December 2012 17:47, Xavier Scheuer wrote:
>
> What a nice proposal!
Actually the known issue that "\set associatedVoice = #"lala" must
be placed one syllable before the one to which the change in voice is
to apply" is really really annoying.
This is registe
French users mailing list and got
6 feature requests, involving baroque and renaissance recorder
fingering charts (woodwind diagrams), old French style tablatures,
jazz chords, baroque oboe fingering.
I'll make sure these feature requests make their way to the tracker.
Thank you very much M
t;)
also?
Currently the doc says
Markup texts may be used for finger changes.
c4-1 d-2 f-4 c^\markup { \finger "2 - 3" }
but of course by doing so they are engraved as TextScript,
not Fingering.
Could you add a feature request for this?
Thank you in advance.
Cheers,
Xavier
--
Xav
w if "repeatCountVisibility" property should be divided
into "percentRepeatCountVisibility" and "unfoldRepeatCountVisibility"
or if they could both share "repeatCountVisibility".
Example of how it would work
\relative c'' {
\set countUnfoldRe
staves as well.
This features has been asked in the French users mailing list and is
tracked as issue #2779.
http://code.google.com/p/lilypond/issues/detail?id=2779
Wouldn't it be for help for you "really smart system engraver"?
Cheers,
Xavier
--
Xavier Scheuer
___
p://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00157.html
Thank you for you attention.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
s automatic subdivision beaming feature has been asked regularly
http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00062.html
(also on the French users mailing list) and it is tracked as issue 2361
http://code.google.com/p/lilypond/issues/detail?id=2361
I can't remember what was Carl&
is is also true for many beginners).
But let's give it a try.
If everybody agrees with Janek's short survey in English I'll send a
translation on the French users mailing list in a few days and report
back the results a dozen of days later.
Cheers,
Xavier
--
Xavier Scheuer
__
?
Ugh, maybe that is more logical (for you) but the postfix syntax has
been used for many many years. That sounds to me like people wanting
to change the electric current convention so that it is the same
direction as the electron flow.
http://x
nds
dolce = -\markup \italic "dolce"
pSubito = #(make-dynamic-extra "p" "subito")
\score {
\new Staff {
\relative c' {
\Allegro
c2\dolce d |
\SegnoMark
e2\pSubito f |
\Solo
g1\f
\bar "|."
}
}
}
End of lily code
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
taves.
Many thanks for your consideration.
If you have questions, do not hesitate to ask.
Please do not forget to cc: Loïc and Jean-François as they asked for
this feature on the French users mailing list, so they could also say
how they would see this new feature work.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
W the three Licenses for Fonts mentioned on GNU.org are:
– GNU GPL with Font Exception
– Arphic Public License
– SIL Open Font License 1.1 (aka OFL)
http://www.gnu.org/licenses/license-list.html#Fonts
Dual (multi) licensing is also possible: GNU GPL Font Exc. + OFL ?
Chee
I recognize it (sorry if that was not clear enough).
I just wanted to make sure all this was intended.
I'm reassured and really grateful for that.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e, I think the following article could be really insightful
(TUG March-May 2004 Annual Meeting):
http://www-hep2.fzu.cz/~piska/TUG2004/piskatb2.pdf
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e solved by forbidding 8th beaming to start
("begin" rules again) on the 4th quaver of 3/4.
Is there something wrong with this approach?
Sorry for "late awakening", I'm following LilyPond development more and
more scarcely and the code usually goes way over the top of my
m")?
But there might be some hope:
https://bugzilla.wikimedia.org/show_bug.cgi?id=33193
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
tp://www.kickstarter.com/projects/293573191/open-goldberg-variations-setting-bach-free
AFAIK LilyPond has not been "involved" in such kind of projects.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
to fight with some developers. I think we all have the
same objective: to improve LilyPond. And each one has its own way to
"contribute", at different levels and different implications.
I would be delighted to offer our finest Belgian beer to LilyPond
developers which I could meet at FOS
h LilyPond, these same developers simply ignore it!
Emilio, I guess you can ask for advise directly at Simon Tatham (the
author of Gonville), I cc him in this reply.
I would be pleased to hear about how you manage with this.
Cheers,
Xavier
--
Xavier Scheuer
___
here)
We could add something about the horizontal line that means
"keep the finger", "keep the position" or "stay on the same string".
What do you think?
I could help with that after February.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
this "shortened" (due to the presence of the DynamicText) hairpin
% does not have a _real_ minimum-length of #8 !
c1\ppp\<^"too short!" |
\override Hairpin #'minimum-length = #12
c\fff\> |
c\> |
\revert
t;
\music
}
\new Staff {
\music
}
>>
}
>>
\layout {
\context {
\Score
\remove "Mark_engraver"
\remove "Staff_collecting_engraver"
}
\context {
Xavier
On 10 December 2011 00:04, Xavier Scheuer wrote:
> Hello,
>
> NR 4.5.1 Horizontal spacing overview says
>
> The most common shortest duration is determined as follows: in every
> measure, the shortest duration is determined. The most common
> shortest duratio
>> | }
> { << { e''1 } \\ { e'1 } >> | }
>
> { << { e'1 } \\ { e1 } >> | }
> { << { e1 } \\ { e'1 } >> | }
>
> I don't understand why the notes are not aligned in all cases.
>
> Is this expe
uot; of horizontal spacing?
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
sent a clearer request to bug-lilypond (before I got you reply).
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
the bug squad was waiting for a "green light" from
the devs.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
n.
I am just wondering: Reinhold, are you still working on this?
I am aware of the workaround of LSR 473 (and already used it although
it is a "bad trick" and still does not print number 1, thus requiring
another even worse trick).
Cheers,
Xavier
--
Xavier Scheuer
__
r your attention.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
documentation outdated? In that case where can
I find the most common shortest duration?
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ot; this statement).
A similar request was also made a few days ago on lilypond-user:
http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00117.html
"Advanced users" are used to have such file containing their own
definitions, predefined settings, that they include for every of their
s
lilypond/issues/detail?id=1798
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ersion?
Anyway, I think that would be a nice new feature.
Dear bug squad, could you add this request on the tracker ?
Thanks!
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/li
%%
\version "2.15.20"
\score {
<<
\new Staff \with {
instrumentName = #"OK"
} {
c'1
}
\new Staff \with {
instrumentName = #"OK"
} {
\grace b8 c'1
}
alternatives of
different measures duration are open to discussion.
But keep in mind that in 90% of the cases there are only 2 alternatives
which have the same measures duration. In the remaining cases
the first alternative is often the shortest.
Thanks for your attention.
Cheers,
Xavier (and man
but I hope it will work with "2.14." and "2.15". Please let me
> know.
Thanks!
That works, and that works great AFAICS. I have sent in the the French
users mailing list.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
hack!
http://codereview.appspot.com/4005046/
http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00291.html
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e restores my scores,
because these scores look good with 2.14.2 (which has fixed-space,
isn't it?)!! Maybe it is the conjunction of different changes in the
horizontal spacing that lead to a bigger change in my particular
scores, what do you think?
Thank you for your interest. Please let m
Neil gave you a hack to tweak this
particular issue (Neil gave me some hacks too, that are really great
and that I am using very often). Too bad there is no simple and clean
solution that could be implemented directly!
Cheers,
Xavier
--
Xavier Scheuer
__
ional (and
maybe it could be interesting to find the commit responsible for this
change and see if we could get back to the behaviour where some scores
(mine) look better)?
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel maili
nature.
I hope this information is relevant (it would be great if that could
help solving this issue). :)
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
nd I'm happy to see there is already a patch attached to it!
So I think my scores will look even better once this patch would have
been reviewed and finally pushed.
Thank you Joe, thank you everybody.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-
have seen in many scores cues with normal ("neutral")
% stem directions (idem for ties, slurs, etc. -> equiv. \oneVoice).
} { R1 }
Maybe Reinhold would have better thoughts about this.
> The smaller size does not come from instrument s
} {
s4\p s s\mp s |
s4\mf s s\f s
}
>>
}
}
\new Staff = "down" {
\clef bass
\repeat unfold 16 c4
}
>>
>>
}
End of snippet
--
Xavier Scheuer
_
define them manually:
>
> {
> R1\fermata
> R1\longfermata
> }
>
> As an added bonus, \displayLilyMusic works properly with the above,
> whereas the original \fermataMarkup caused it to crash.
That would be a nice improvement in syntax simplification and better
accessibility
usic university don't have any)
Hi,
That has been registered as issue #1774, isn't it?
http://code.google.com/p/lilypond/issues/detail?id=1774
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
ad (unexpected) output, whereas the
input was good should be given a "higher consideration".
The same for issues that give a poor output and that are likely to
happen in almost every score produced.
Thanks!
Cheers,
Xavier
--
Xavier Scheuer
__
slurs to a maximum height, please also make some tests
to check the effect on *cross-staff* slurs (they can have an huge
height, but in this case that would be **normal**).
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel
measure rest
should take more horizontal space (as much horizontal space as a note
of the same duration), could someone open a new issue for this on the
tracker?
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
full bar rest width"
\test
}
}
\score {
\new Staff {
c'1^"new (expected) full bar rest width"
\test
}
\layout {
\context {
\Voice
\override MultiMeasureRest #'minimum-length = #8
}
}
}
End of snippet
Cheers,
Xavier
--
Xavie
k stating this issue is effectively (and
finally!) fixed would be appreciated.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
e, I hope to schedule GOP stuff for all of
> August and even reaching into Sep. Once that's done, I'll do more
> preparation for GLISS, but I would be surprised if we start that
> in August. Depends a lot of how many release issues there are for
> 2.16.
Thanks for the an
at should be default tremolo slashes
settings).
http://code.google.com/p/lilypond/issues/detail?id=1735#c5
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo
future LilyPond
releases and "Grand Projects" roadmaps?
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 20 July 2011 21:15, m...@apollinemike.com wrote:
>
> I ran into the exact same thing in a score I'm working on and proposed
> a patch to devel - lemme know what ya'll think!
Thanks a lot Mike (and Neil too, of course)!
Cheers,
Xavier
nfidence in above-mentioned
people to take the right decision. I was just afraid because this
change seemed to me to have been considered as a small, almost trivial,
change, which shouldn't IMHO. Glad to see a frank discussion about it.
Thanks for
{
\repeat unfold 4 {
% comment the pedal and the DynamicTextSpanner are well
% aligned in the Dynamics context above!
s1\sustainOn s1\sustainOff
}
}
>>
>>
}
Cheers,
Xavier
--
Xavier Scheuer
_
rts spanner-interface but it
failed).
Is there a simple way to print the \sustainOff at the very end of the
measure (just before the bar line)?
Thanks in advance.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
y) see noticeable change between them.
Waiting for GLISS to see a proposal of official integration into
LilyPond.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 19 June 2011 22:50, Xavier Scheuer wrote:
>
> Decrease the value of StaffGrouper #'staffgroup-staff-spacing for
> your GrandStaff (containing the violins).
>
> By default StaffGrouper #'staffgroup-staff-spacing has bigger values
> of 'basic-d
ing))
))
ffdolce = #(make-dynamic-extra "ff" "dolce")
{ a1 a\ffdolce a }
%%
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
first part ...
\context { \GrandStaff
\override StaffGrouper #'staff-staff-spacing #'stretchability = #3.5
\override StaffGrouper #'staffgroup-staff-spacing = #'((basic-distance . 9)
(minimum-distance . 7)
.
I'm not used to the new "stable-unstable" policy, but this should be
"cherry-picked" in the upcoming 2.14, isn't it?
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
x27;springs-and-rods = #ly:spanner::set-spacing-rods
\once \override Glissando #'minimum-length = #4
\hideNotes
s1*0\glissando
}
stopGlissandoGraceMusic = {
\unHideNotes
s1*0
}
glissandoGrace = #(def-grace-function startGlissandoGraceMusic
stopGlissandoGraceMusic
(_i "Create
On 18 April 2011 13:31, Valentin Villenave wrote:
>
> How about restarting the staff, as in http://lsr.dsi.unimi.it/LSR/Item?id=700
> ?
Indeed, it works.
Thanks!
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilyp
ug-lilypond
%% It is not possible to change the color of ledger lines in the middle
%% of a score.
%%
\version "2.13.60"
\score {
\new Staff {
c c' c'' c'''
\override Staff.LedgerLineSpanner #'color = #red % no effect!
c c' c&
ranslations available, but right now stable release does not appear
often (more than 15 month between 2.12.3 and upcoming-2.14).
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 27 March 2011 00:44, Xavier Scheuer wrote:
>
> Would rather be 47-hour notice, due to daylight saving time that starts
> this night in Europe (and you said UK time).
> We will loose one hour of sleep tonight.
>
> Good night anyway. ;D
OK, no, forget.
I saw you sent your e
> http://codereview.appspot.com/4313047/
Would rather be 47-hour notice, due to daylight saving time that starts
this night in Europe (and you said UK time).
We will loose one hour of sleep tonight.
Good night anyway. ;D
Cheers,
Xavier
--
Xavier Scheuer
_
= ##f
is part of the definition of "improvisationOn" but not
\override AccidentalCautionary #'stencil = ##f
May I suggest to add it?
You'll find this change as PATCH in attachment.
Thanks in advance!
Cheers,
Xavier
--
Xavier Scheuer
From f51968b9d3d3dbea3b7277dc86cce60fa794bff2 M
gt; a note head in the music.
I'm not a dev but it should be possible to scale all the note heads
(i.e. not only the mi) by using ly:stencil-scale , I think.
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypon
2011/2/9 Neil Puttock :
>
> Like this?
>
> \layout {
> \context {
>\Dynamics
>\RemoveEmptyStaves
> }
> }
Exactly!
Now of course it seems so obvious, I'm wondering *why* I did not think
about this.
Many thanks.
Ch
Staff {
R1*48
}
>>
\new Staff {
\repeat unfold 48 c'1
}
>>
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
}
Cheers,
Xavier
--
Xavier Scheuer
___
lilypond-devel mailing list
lilypond-dev
1 - 100 of 183 matches
Mail list logo
