Hi everyone,
I've written a LilyPond syntax highlighter for pygments. It's not perfect
but it's mostly working. Is there anyone out there who could test it?
https://github.com/craigdab/pygments/tree/LilyPond
I'm sure there is lots that could be improved on it. It is running without
errors, but
Am 25. Januar 2020 08:17:05 MEZ schrieb Werner LEMBERG :
>
>>> I think it is necessary to somehow keep the staff line alive – I
>>> guess I can probably fake a solution by adding another bar with a
>>> suppressed bar line that contains some invisible music. Not sure
>>> yet whether this is
>> I think it is necessary to somehow keep the staff line alive – I
>> guess I can probably fake a solution by adding another bar with a
>> suppressed bar line that contains some invisible music. Not sure
>> yet whether this is sensible, and if yes, how to make the width of
>> this extra bar
Am 25. Januar 2020 07:30:01 MEZ schrieb Werner LEMBERG :
>
>> \once \override Score.BreakAlignment #'break-align-orders =
>> #(make-vector 3 '( staff-bar
>> clef
>> span-bar
>> breathing-sign
>> ...
>>
> \once \override Score.BreakAlignment #'break-align-orders =
> #(make-vector 3 '( staff-bar
> clef
> span-bar
> breathing-sign
> ...
> key
> time-signature)),
>
> To
Werner,
Perhaps using
\once \override Score.BreakAlignment #'break-align-orders = #(make-vector 3
'( staff-bar clef span-bar breathing-sign . . key time-signature)),
To insert the key change before the bar.
Mark
-Original Message-
From: lilypond-user
I have to typeset a snippet that is an excerpt of a longer piece, and
this snippet ends with a key change:
\relative c' {
\key d \major
d1
\key c \major
}
However, the staff stops right before the key change, see attached
image. What can I do to avoid that?
Werner
On Saturday, January 25, 2020, Knute Snortum wrote:
> You didn't say what version you were using, but it looks like 2.18.2
> and 2.19.83 do the same thing.
>
>
I tried it with both 2.18.2 and 2.19.83
You didn't say what version you were using, but it looks like 2.18.2
and 2.19.83 do the same thing.
---
Knute Snortum
(via Gmail)
On Fri, Jan 24, 2020 at 12:33 PM Paolo Prete wrote:
>
> Hello,
>
> From what I see, Y-offset gives weird results on a TupletBracket
>
> fakeRulerUp = { \once \hide
On January 24, 2020 at 4:50 PM David Kastrup <
d...@gnu.org> wrote:
Bric <
b...@flight.us> writes:
i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS
had to build
David Kastrup writes:
> Werner LEMBERG writes:
>
some publishers repeat accidentals not only if a tie gets broken
between staves but also if it crosses a bar line:
|||
#o| #o
\/
Is there a property in LilyPond to
Werner LEMBERG writes:
>>> some publishers repeat accidentals not only if a tie gets broken
>>> between staves but also if it crosses a bar line:
>>>
>>> |||
>>>#o| #o
>>> \/
>>>
>>> Is there a property in LilyPond to automatically activate this?
>>
>> probably:
Thomas Morley writes:
> Am Fr., 24. Jan. 2020 um 22:42 Uhr schrieb Werner LEMBERG :
>>
>>
>> Folks,
>>
>>
>> some publishers repeat accidentals not only if a tie gets broken
>> between staves but also if it crosses a bar line:
>>
>> |||
>>#o| #o
>> \/
>>
>> Is
>> some publishers repeat accidentals not only if a tie gets broken
>> between staves but also if it crosses a bar line:
>>
>> |||
>>#o| #o
>> \/
>>
>> Is there a property in LilyPond to automatically activate this?
>
> probably:
>
> {
> \override
Am Fr., 24. Jan. 2020 um 22:42 Uhr schrieb Werner LEMBERG :
>
>
> Folks,
>
>
> some publishers repeat accidentals not only if a tie gets broken
> between staves but also if it crosses a bar line:
>
> |||
>#o| #o
> \/
>
> Is there a property in LilyPond to
Bric writes:
> i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS
>
> had to build guile-1.8.8, after which lilypond ./configure was happy, and
> finished (posted
> about my guile struggles a few days ago)
>
> But "make" errors out with:
>
> cat Documentation/out/generate-documentation.log
i am building lilypond-2.19.83 on Ubuntu 18.04.2 LTS
had to build guile-1.8.8, after which lilypond ./configure was happy, and finished (posted about my guile struggles a few days ago)
But "make" errors out with:
cat
Folks,
some publishers repeat accidentals not only if a tie gets broken
between staves but also if it crosses a bar line:
|||
#o| #o
\/
Is there a property in LilyPond to automatically activate this?
Werner
Hello,
>From what I see, Y-offset gives weird results on a TupletBracket
fakeRulerUp = { \once \hide NoteHead \once \hide Stem c'}
{
%doesn't do anything
\override TupletBracket.Y-offset = 5
\tuplet 3/2 { c' c' c' } \fakeRulerUp
% not only the middle line of the staff is ignored; it
On Jan 24, 2020, at 5:22 AM, Mark Knoop wrote:
> At 20:27 on 23 Jan 2020, Daniel Rosen wrote:
>> Does anyone have any ideas for a workaround for Issue #5538 “bendAfter
>> broken by chords”?
>> (https://sourceforge.net/p/testlilyissues/issues/5538/)
>
> No, sorry. After reporting this bug I ended
On Wed, Jan 22, 2020 at 11:56 PM Aaron Hill
wrote:
> On 2020-01-22 7:26 am, Paolo Prete wrote:
> > The problem is associated with:
> >
> > https://lists.gnu.org/archive/html/lilypond-user/2020-01/msg00467.html
> >
> > Sorry if I insist again with this: is there a fix (or work-around) for
> > it?
On 2020-01-24 3:03 am, David Kastrup wrote:
Aaron Hill writes:
If you do this enough, putting it in a music function will make your
score much more readable:
cueName = #(define-music-function (parser location name) (markup?)
#{ \tag #'cueName \set CueVoice.instrumentCueName = #name #})
Aaron Hill writes:
> On 2020-01-23 8:00 pm, Aaron Hill wrote:
>>
>> \tag #'cueName <>_\markup \tiny \italic "Bsn."
>> \cueDuring #"bassoon" #DOWN { R1}
>>
>
> If you need to use instrumentCueName or would simply prefer not to use
> text scripts, then you can do this:
>
>
>
At 20:27 on 23 Jan 2020, Daniel Rosen wrote:
> Does anyone have any ideas for a workaround for Issue #5538 “bendAfter
> broken by chords”?
> (https://sourceforge.net/p/testlilyissues/issues/5538/)
No, sorry. After reporting this bug I ended up using a TextSpanner instead.
--
Mark Knoop
Hi Davide,
On Fri, Jan 24, 2020 at 10:32 AM Davide Liessi
wrote:
>
> they are right: indeed python-poppler-qt5 (Python bindings for the Qt5
> frontend of poppler) does not depend on python-poppler (Python
> bindings for the glib frontend of poppler).
>
> thanks for the clarification. I'm using
> -Ursprüngliche Nachricht-
> Von: lilypond-user bounces+sir.teddy.the.first=gmail@gnu.org> Im Auftrag von Aaron Hill
> Gesendet: Freitag, 24. Januar 2020 09:51
> An: lilypond-user@gnu.org
> Betreff: Re: AW: Odd Behaviour: \break after \repeat
>
> On 2020-01-24 12:32 am,
Dear Andrew,
Il giorno ven 24 gen 2020 alle ore 09:12 N. Andrew Walsh
ha scritto:
> The dev there asserts that python-poppler-qt5 does not require python-poppler,
they are right: indeed python-poppler-qt5 (Python bindings for the Qt5
frontend of poppler) does not depend on python-poppler
Good morning,
@David thank you for the reference to the Guile Manual, and @Urs thank you for
your
introduction!
Bests,
Amir
lilypond-user-requ...@gnu.org writes:
> Send lilypond-user mailing list submissions to
> lilypond-user@gnu.org
>
> To subscribe or unsubscribe via the World Wide
On 2020-01-24 12:32 am, sir.teddy.the.fi...@gmail.com wrote:
Thank you for your answer, David.
It does make sense that way.
Guess I'll just use "Te_- st" in this case to get rid of the extra
hyphen.
You shouldn't have to do that. Rather, change how far apart you want
LyricHyphens:
Thank you for your answer, David.
It does make sense that way.
Guess I'll just use "Te_- st" in this case to get rid of the extra hyphen.
> -Ursprüngliche Nachricht-
> Von: David Wright
> Gesendet: Freitag, 24. Januar 2020 02:38
> An: sir.teddy.the.fi...@gmail.com
> Cc: 'lilypond-user'
Hi List, Hi Wilbert,
I just want to check something. According to this bug:
https://bugs.gentoo.org/706030
gentoo will be removing python-poppler from its tree. The dev there asserts
that python-poppler-qt5 does not require python-poppler, and the version in
the gentoo repo does not. Wilbert,
31 matches
Mail list logo
