David Kastrup writes:
> thomasmorle...@gmail.com writes:
>
>> I then would have expected the following to work (with a warning):
>>
>> { \voicify 1 << a' \\ c' >> }
>>
>> instead I get:
>>
>> $ lilypond-git atest-54.ly
>> GNU LilyPond 2.19.59
>> Processing `atest-54.ly'
>> Parsing.../home/hermann
thomasmorle...@gmail.com writes:
> I then would have expected the following to work (with a warning):
>
> { \voicify 1 << a' \\ c' >> }
>
> instead I get:
>
> $ lilypond-git atest-54.ly
> GNU LilyPond 2.19.59
> Processing `atest-54.ly'
> Parsing.../home/hermann/lilypond-git/build/out/share/lilypon
On 2017/04/09 15:13:32, dak wrote:
mailto:thomasmorle...@gmail.com writes:
> Great!
>
> Two thoughts:
>
> (1)
> it's a common request on the user list how to continue a tie into
the <<
> \\ >> - construct.
> I'm aware we explain it at the lines of "don't use the
> double-backslash".
> Also,
On 2017/04/09 15:15:47, dak wrote:
mailto:thomasmorle...@gmail.com writes:
>
https://codereview.appspot.com/320820043/diff/40001/scm/music-functions.scm
> File scm/music-functions.scm (right):
>
>
https://codereview.appspot.com/320820043/diff/40001/scm/music-functions.scm#newcode968
> scm
2017-04-09 18:23 GMT+02:00 Trevor Daniels :
>
> David Kastrup wrote Sunday, April 09, 2017 5:14 PM
>>
>> Harm brought a few points, one concerning different warning/error
>> behavior (and with regard to the _text_ of the existing warning, I will
>> cede the point thought there isn't yet a proposal
> So how to proceed? [...]
+1 for \voices.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
David Kastrup wrote Sunday, April 09, 2017 5:14 PM
>
> Harm brought a few points, one concerning different warning/error
> behavior (and with regard to the _text_ of the existing warning, I will
> cede the point thought there isn't yet a proposal for \voices as far as
> I can see). He also point
What now? I have a few suggestions I don't agree with really and don't
know whether there is more of a discussion warranted now.
Harm brought a few points, one concerning different warning/error
behavior (and with regard to the _text_ of the existing warning, I will
cede the point thought there
thomasmorle...@gmail.com writes:
> https://codereview.appspot.com/320820043/diff/40001/scm/music-functions.scm
> File scm/music-functions.scm (right):
>
> https://codereview.appspot.com/320820043/diff/40001/scm/music-functions.scm#newcode968
> scm/music-functions.scm:968:
> On 2017/04/08 12:02:45,
thomasmorle...@gmail.com writes:
> Great!
>
> Two thoughts:
>
> (1)
> it's a common request on the user list how to continue a tie into the <<
> \\ >> - construct.
> I'm aware we explain it at the lines of "don't use the
> double-backslash".
> Also, how to use named voices is explained, iirc.
>
>
Carl Sorensen writes:
> How about
>
> \voiceOrder
>
> and
>
> \defaultVoiceOrder
>
> ?
The first is even less likely to suggest that it applies only to the
following single music expression rather than several ones than just
\voices would be.
--
David Kastrup
__
Hello,
Here is the current patch countdown list. The next countdown will be on
April 12th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
5114 Add a \voicify command - David Kastrup
https://sourceforge.net/
12 matches
Mail list logo
