Am 30.03.2015 um 07:58 schrieb David Kastrup:
Kevin Barry writes:
For sure the voice context limitations are a pain, and if I knew how, I
would write a function for starting and finishing slurs without the need
for creating a hidden voice, but I don't even know if it is possible. In my
own h
>> This would warrant a better mechanism to transplant spanners to a
>> different context: basically one would want a mechanism to listen
>> to slur endings in a different context than to slur starts.
>> Possibly optionally with a \once qualification.
>
> I think the idea of an analogy to \change
Am 30.03.2015 um 09:31 schrieb Werner LEMBERG:
This would warrant a better mechanism to transplant spanners to a
different context: basically one would want a mechanism to listen
to slur endings in a different context than to slur starts.
Possibly optionally with a \once qualification.
I think
Am 30.03.2015 um 09:47 schrieb Urs Liska:
Am 30.03.2015 um 09:31 schrieb Werner LEMBERG:
This would warrant a better mechanism to transplant spanners to a
different context: basically one would want a mechanism to listen
to slur endings in a different context than to slur starts.
Possibly op
>>in voiceA: c4
>>\connect #'Slur #'voiceB #'myanchor
>>d e f
>>
>>in voiceB: e4 f g
>>\anchor #'myanchor
>>a
>
> You mean instead of writing "(", or "\<" or "\startTrillSpan" one
> would write "\connect" and that would insta
> Thinking a little more about this: Wouldn't it even be possible to
> implement this as a pair of comparably simple Scheme functions?
> They would instantiate a hidden temporary Voice (of course using
> \omit not \hide) and add the respective spanner to that?
Sounds reasonable, but this is beyon
Am 30.03.2015 um 10:05 schrieb Werner LEMBERG:
Thinking a little more about this: Wouldn't it even be possible to
implement this as a pair of comparably simple Scheme functions?
They would instantiate a hidden temporary Voice (of course using
\omit not \hide) and add the respective spanner to t
>>> Any advice anyone?
>> Would you show me the whole ghostscript.log and
>> /home/gub/NewGub/gub/target/darwin-ppc/build/soobj/arch.h ?
>>
>
> Attached.
Thank you.
It seems 32 bit hosts cross compiling issue.
I've updated the branch.
https://github.com/trueroad/gub/commit/27a90b6b8c6d2f2acb1062
On 2015/03/29 20:33:33, pwm wrote:
Please review, thanks.
Could you provide an example where this would be useful?
Thanks,
David
https://codereview.appspot.com/219460043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/
On 2015/03/30 16:36:20, david.nalesnik wrote:
On 2015/03/29 20:33:33, pwm wrote:
> Please review, thanks.
Could you provide an example where this would be useful?
Thanks,
David
OK, drat. Ignore that!! See Issue 3615, of course :)
https://codereview.appspot.com/219460043/
__
Werner LEMBERG writes:
>>> This would warrant a better mechanism to transplant spanners to a
>>> different context: basically one would want a mechanism to listen
>>> to slur endings in a different context than to slur starts.
>>> Possibly optionally with a \once qualification.
>>
>> I think the
Thank you so much for bringing this up! This is a very annoying limitation
that should be fixed. I only wish I knew how to program enough to help.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Reasons-for-cross-voice-limitations-tp173845p173898.html
Sent from the Dev ma
>> What about defining anchors? Having a slur ending in a different
>> voice makes the `(' ... `)' notation extremely hard to read (if it
>> works at all). Instead, I can imagine something like the following
>> to get a slur between voiceA and voiceB, starting on the second and
>> ending on the
13 matches
Mail list logo
