[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Crash with simultaneous-duplicating music function and \once\offset
From: |
David Kastrup |
Subject: |
Re: Crash with simultaneous-duplicating music function and \once\offset |
Date: |
Wed, 18 Jul 2018 12:58:34 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Simon Albrecht <address@hidden> writes:
> On 18.07.2018 10:59, David Kastrup wrote:
>> basically one of the calls to \offset gets junked because of LilyPond
>> not being able to disentangle them (one could extend the code to handle
>> this case but it would still balk at more complex combinations).
>
> Great! This is exactly what would be needed in my use case, since I
> wouldn’t have wanted the offset to be applied twice. ly:expect-warning
> exists.
Well, don't rely on this sticking around. It may well end up at some
time without warning and double the offset since that is what you are
asking for.
> I suppose the better solution would be for the makeOctaves function to
> filter out overrides and \offset calls from the duplicate of the
> music?
Definitely. Also more future-proof.
--
David Kastrup
- Re: Crash with simultaneous-duplicating music function and onceoffset, (continued)
- Re: Crash with simultaneous-duplicating music function and onceoffset, James Lowe, 2018/07/16
- Re: Crash with simultaneous-duplicating music function and \once\offset, Aaron Hill, 2018/07/16
- Re: Crash with simultaneous-duplicating music function and \once\offset, David Kastrup, 2018/07/17
- Re: Crash with simultaneous-duplicating music function and \once\offset, Aaron Hill, 2018/07/17
- Re: Crash with simultaneous-duplicating music function and \once\offset, David Kastrup, 2018/07/17
- Re: Crash with simultaneous-duplicating music function and \once\offset, Simon Albrecht, 2018/07/17
Re: Crash with simultaneous-duplicating music function and \once\offset, David Kastrup, 2018/07/18