Hi Valentin, thank you this is super interesting. There's a lot of
information in there I want to read more carefully,
but for the moment I have one question: when is after-line-breaking invoke?
Or actually, better question: where do I go to discover when (and I guess
by what) after-line-breaking i
Am So., 20. Feb. 2022 um 22:41 Uhr schrieb Luca Fascione :
> a) I'm looking for a way to get the fingerings where I want them without
> using one-note-chord tricks
Well, for Fingerings not in chord, like b-1 or -2-1 X-parent
is NoteColumn _not_ NoteHead, Y-parent is VerticalAxisGroup.
There is
Hello,
our problem here is that such things like the positioning of beams are not
known for quite some time. But we could use something like after-line-breaking
to adjust the results. Somewhat like here.
Valentin
Am Sonntag, 20. Februar 2022, 21:17:31 CET schrieb Luca Fascione:
> So... would a
Thanks Jean,
I thought a somewhat more complete example of the configurations I'm
looking at would help get a sense of the scope of the problem,
and also that the solution would be an easy "do this" or "look here" kind
of answer.
My concern with a tiny example is that it risks to create a rather lo
Le 20/02/2022 à 21:17, Luca Fascione a écrit :
So... would anybody be able to lend a hand here please?
Many thanks
Luca
It would be helpful if you provided smaller examples.
I'm not saying this as a reprimand, but as friendly
advice on how to get people to help you. Personally,
I had started
So... would anybody be able to lend a hand here please?
Many thanks
Luca
On Sat, Feb 12, 2022 at 7:49 PM Luca Fascione wrote:
> Hello,
> sorry for the double-post, I'm unsure whether this should go to -user or
> -devel.
>
> I'm looking for some guidance to set up fingering on classical guitar
>
Dan Eble writes:
> ASSIGN_EVENT_ONCE(cur, new) does this:
>
> - if cur is nullptr: assign cur = new, return true
> - if *cur and *new are equal: quietly return false
> - if *cur and *new are unequal: warn and return false
>
> Would a Scheme analog of ASSIGN_EVENT_ONCE be used like this,
>
Le 20/02/2022 à 19:46, Dan Eble a écrit :
ASSIGN_EVENT_ONCE(cur, new) does this:
- if cur is nullptr: assign cur = new, return true
- if *cur and *new are equal: quietly return false
- if *cur and *new are unequal: warn and return false
Would a Scheme analog of ASSIGN_EVENT_ONCE be use
ASSIGN_EVENT_ONCE(cur, new) does this:
- if cur is nullptr: assign cur = new, return true
- if *cur and *new are equal: quietly return false
- if *cur and *new are unequal: warn and return false
Would a Scheme analog of ASSIGN_EVENT_ONCE be used like this,
(let ((my-foo-event #f))
Am Samstag, dem 19.02.2022 um 23:21 +0100 schrieb Jonas Hahnfeld via
Discussions on LilyPond development:
> Am Samstag, dem 19.02.2022 um 23:05 +0100 schrieb Jean Abou Samra:
> > > Plus, your plan of keeping code for Guile 1.8 doesn't work / make sense
> > > without keeping GUB working. That is far
> Am 20.02.2022 um 10:16 schrieb Jean Abou Samra :
>
>
>
> Le 20/02/2022 à 10:13, Thomas Scharkowski a écrit :
>> Sorry, couldn’t get the patched lily.scm to run - certainly a mistake on my
>> side.
>> If you like you can send a correct patched lily.scm to me?
>>
>> Thomas
>
> Here you go.
Hi Thomas,
maybe this can be handy: the `moreutils` package has a utility called `ts`,
that will prepend a timestamp to each line of output.
If you pipe the output of your compilation into it, you can get timing
information quite easily, here's an example:
% ls | ts -s "%H:%M:%.S"
00:00:00.13
Quick answer: I can notice the speed difference in the terminal output from the
very start.
I will try the diff later.
Thomas
> Am 19.02.2022 um 20:12 schrieb Jean Abou Samra :
>
> Le 19/02/2022 à 16:41, Thomas Scharkowski a écrit :
>> One more test:
>> I installed both versions on a 2013 iMac
13 matches
Mail list logo
