el 2019-02-17 a las 21:41 Thomas Morley escribió:
> Speaking only for myself I think the OP is correct saying flat-flags
> should behave like Beams, though I don't agree for
> modern/old-straight-flags.
And now I tend to agree with you... :-)
Both examples I mentioned in my other email (Boulez
el 2019-02-17 a las 21:41 Thomas Morley escribió:
> Speaking only for myself I think the OP is correct saying flat-flags
> should behave like Beams, though I don't agree for
> modern/old-straight-flags.
I forgot to mention that in the only example that I have at hand of
horizontal flags (Xenakis
el 2019-02-19 a las 11:30 Thomas Morley escribió:
> Did you already try my suggestion for flat flags?
>
> #(define-public (flat-flag grob)
> "Flat flag style. The angles of the flags are both 0 degrees"
> ((straight-flag 0.48 0.81 0 1.0 0 1.0) grob))
>
> Put it on top of your ly-file, you
el 2019-02-19 a las 22:05 Thomas Morley escribió:
> You could even do:
>
> #(define-public (my-flag grob)
> ((straight-flag 0.4 1 -70 3 -70 3) grob))
>
> {
> \override Flag.stencil = #my-flag
> a'8
> b'
> }
> %% or
> {
> \override Flag.stencil =
> #(lambda (grob) ((straight-flag 0
el 2019-02-20 a las 10:51 foxfanfare escribió:
> Does someone knows how to configure vim in order to have the access of
> the whole LP syntax and make suggestions like in frescobaldi?
it's fairly easy to have basic completion, you just need to define a
dictionary for lilypond.
http://vim.wikia.
el 2019-03-15 a las 09:44 Urs Liska escribió:
> Markups can't flow beyond the end of a score (horizontally) and widen
> the score if necessary:
>
> \version "2.19.82"
>
> {
>c'1 -"This is a long text that widens the score because it can't
> protrude." c'1
> }
>
> Is there a possibility to
el 2019-03-17 a las 11:33 Andrew Bernard escribió:
> Sorry, not the specific answer to your question.
hi, thank you for your answer, and excuse my delayed response.
leaving aside considerations if what i'm asking for is a good practice or
not, should i understand that there's no way to allow a
el 2019-03-16 a las 19:23 Saul Tobin escribió:
> I agree that when a long markup stretches the measure at the end of a
> line, it suggests that there may be better ways of laying out the line
> breaks.
>
> Perhaps there should be a penalty for stretched measures due to markup in
> Lilypond's lin
el 2019-03-29 a las 16:20 David Kastrup escribió:
> Agreement does not buy a whole lot when there is nobody who can or will
> do the job.
as someone who has been using free software for about 20 years now, i know
the situation. in fact, lilypond is perhaps the project with the highest
ratio betw
el 2019-03-30 a las 18:06 Andrew Bernard escribió:
> I don't think wordwrap is what the OP wanted.
you're right, that's not what i was asking.
> I still think this is a bad engraving choice
again, i don't want to discuss this issue. my question was strictly
related to the possibility of doing
el 2019-04-01 a las 11:37 Andrew Bernard escribió:
> Thanks so much. Now to learn Metafont then. Shouldn't be too hard
unlike valentin, i admire you already even if you don't succeed. i don't
know what admire the most: the determination of the "now to learn
metafont", or the optimism of the "sho
Hello, list.
It seems it's not possible to use \arpeggio in drummode, or am I missing
something?
The following code doesn't throw any errors but it doesn't show anything.
\version "2.21.0"
\new DrumStaff
\drummode {
2
\arpeggio
}
--
___
lily
el 2019-08-13 a las 22:36 Aaron Hill escribió:
> Try:
>
>
> \version "2.19.83"
>
> \new DrumStaff
> \with { \consists "Arpeggio_engraver" }
Excellent, thank you! Almost there... ;-)
I'm very close to what I want, but is there a way to tweak the length of
the brackets?
What I'm actual
el 2019-08-14 a las 18:34 Robin Bannister escribió:
> You can override the positions property.
> Try
>
> \new DrumStaff \with {
>\override NoteColumn.ignore-collision = ##t
>\override Arpeggio.thickness = #2.0
>\override Arpeggio.positions = #(lambda(grob)
> (interval-widen (ly
14 matches
Mail list logo
