On 11/6/21, 3:24 PM, "lilypond-user on behalf of Lukas-Fabian Moser"
wrote:
> \relative {
>\alterBroken #'padding #'(1 7) Staff.OttavaBracket
>\ottava 1 c1 \break
> c2 2
> }
I continue my lonely crusade against the hash-tick-combinations that I
Le 07/11/2021 à 00:07, Paolo Prete a écrit :
is it possible to set max-systems-per-page = X on the first page of
the score and = Y on the remaining pages?
It isn't. The page breaker is not prepared to
handle this currently. You should insert explicit
breakpoints for the first page and define
Hello,
is it possible to set max-systems-per-page = X on the first page of the
score and = Y on the remaining pages?
thanks!
P
Le 2021-11-01 18:26, Stefan Thomas a écrit :
Dear community,
I would like to do with arranger.ly something similar to
Key = { \key f \major }
music =
{ \Key c'4 d' e' f'2.}
artiA = { s2.( s) }
music = { \context Voice << {\music} {\artiA } >> }
I tried in in the following way, without
Hi Lukas,
> I continue my lonely crusade against the hash-tick-combinations
I generally remove them — I’m on the crusade with you! — tho’ on this
“fast-cut-and-paste job”, I didn’t. =(
That being said, there are certain circumstances in which I prefer keeping the
hashes, as they (IMO) help
On 2021-11-06 2:45 pm, Lukas-Fabian Moser wrote:
Since #'(1 7) is a list of numbers, you could write it this way:
\relative {
\alterBroken padding 1,7 Staff.OttavaBracket
\ottava 1 c1 \break
c2 2
}
Right, thanks! I had a feeling there was a way to do this using dak's
Since #'(1 7) is a list of numbers, you could write it this way:
\relative {
\alterBroken padding 1,7 Staff.OttavaBracket
\ottava 1 c1 \break
c2 2
}
Right, thanks! I had a feeling there was a way to do this using dak's
syntax enhancements but couldn't remember what it
On 2021-11-06 2:23 pm, Lukas-Fabian Moser wrote:
\relative {
\alterBroken #'padding #'(1 7) Staff.OttavaBracket
\ottava 1 c1 \break
c2 2
}
I continue my lonely crusade against the hash-tick-combinations that I
found so daunting when I learned LilyPond and which are needed much
less
\relative {
\alterBroken #'padding #'(1 7) Staff.OttavaBracket
\ottava 1 c1 \break
c2 2
}
I continue my lonely crusade against the hash-tick-combinations that I
found so daunting when I learned LilyPond and which are needed much less
often today:
\relative {
\alterBroken
Le 06/11/2021 à 22:01, Knute Snortum a écrit :
Hello again,
I have a situation where I need to adjust the padding of an ottava
bracket after a line break. That is, I want to affect the bracket on
the second line, but not the first.
I know you can do something like this with the \shape
p.s.
> Does \afterBreak not work with OttavaBracket.padding?
um… \alterBroken (as in the snippet).
Sorry! — K
> \relative {
> \alterBroken #'padding #'(1 7) Staff.OttavaBracket
> \ottava 1 c1 \break
> c2 2
> }
Hi Knute,
> I have a situation where I need to adjust the padding of an ottava
> bracket after a line break. That is, I want to affect the bracket on
> the second line, but not the first.
Does \afterBreak not work with OttavaBracket.padding?
\relative {
\alterBroken #'padding #'(1 7)
Hello again,
I have a situation where I need to adjust the padding of an ottava
bracket after a line break. That is, I want to affect the bracket on
the second line, but not the first.
I know you can do something like this with the \shape function, but
what about brackets?
I tried this solution
Hi,
I think that's too optimistic.
That's the gist; just some tiny corrections to make
sure Kieren knows what he will work on:
#686 certainly involves a bit of C++ programming (the command line is
evaluated in C++).
Not necessarily, options passed with -d and never
used in C++ are
Hi Kieren,
Am 06.11.21 um 20:58 schrieb Kieren MacMillan:
Hello all,
Now if what you want is really coding, there are
heaps of open issues waiting for you. Here are a
few that I believe (NB no warranty) would be feasible
for a power user with some minimal understanding of
Scheme:
Le 06/11/2021 à 20:58, Kieren MacMillan a écrit :
Hello all,
Now if what you want is really coding, there are
heaps of open issues waiting for you. Here are a
few that I believe (NB no warranty) would be feasible
for a power user with some minimal understanding of
Scheme:
Hello all,
> Now if what you want is really coding, there are
> heaps of open issues waiting for you. Here are a
> few that I believe (NB no warranty) would be feasible
> for a power user with some minimal understanding of
> Scheme:
> https://gitlab.com/lilypond/lilypond/-/issues/794
>
I’ve done some work to clean up my code and also modified the interface to be
fairly intuitive and non-intrusive. Hopefully I’ll have some time this week to
integrate this into my project, but if anyone sees anything that could be
improved, I’d love to hear about it.
No more needed. Thanks.
‐‐‐ Original Message ‐‐‐
Il venerdì 5 novembre 2021 20:25, Thomas Morley ha
scritto:
> Am Fr., 5. Nov. 2021 um 09:50 Uhr schrieb Mahanidhi
> :
>
>> Hello,
>> I'm triyng to have the second line open at the end as the first. But with
>> repeats bar at the third
Le 06/11/2021 à 14:47, Kieren MacMillan a écrit :
[...]
Is there some gain to be had by considering the three related concepts —
“context pushing”, cross-staff items, and part-combining — together, to see
where a single mechanism might help all three? Put another (OOP-ish) way: Are
On 06/11/2021 14:06, Kevin Cole wrote:
I click Learning Manual. Still good. https remains. I am now at
https://lilypond.org/doc/v2.20/Documentation/learning/index#top
I click the search bar at the bottom of the green sidebar table of
contents... And get a pop-up in red text:
"This form is not
> Am 06.11.2021 um 15:06 schrieb Kevin Cole :
>
> I click Learning Manual. Still good. https remains. I am now at
> https://lilypond.org/doc/v2.20/Documentation/learning/index#top
>
> I click the search bar at the bottom of the green sidebar table of
> contents... And get a pop-up in red
I' m using Brave. Version 1.31.88 Chromium: 95.0.4638.69 (Official
Build) (64-bit)
I enter https://lilypond.org/doc/v2.20/ and am redirected to
https://lilypond.org/doc/v2.20/Documentation/web/index.html
So far, so good. https: redirects to https:
I click Manuals and again, am taken to
Hi Jean,
> In an ideal world of 'pushing' grobs, that would
> be written as something like
> ^\p
YES!!!
> but the \p should also be pushed or something
> should be done about it because of its direction.
For sure, there are potential complications…
> it's worth noting that the part combiner,
Le 05/11/2021 à 23:09, David Kastrup a écrit :
I think one change should be that cross-staff needs to be more than a
flag. It rather needs to be a pair of staves identified in some manner
where distancing of any staff pairs in that interval will not involve
the cross-staff material, but it
25 matches
Mail list logo
