Pierre Perol-Schneider writes:
> Hi again,
>
> I've seen that the snippet's still there :
> http://lsr.di.unimi.it/LSR/Item?id=732
>
> Shall I keep it or ?
It's rubbish. Rests don't consult Stem.direction now but
Rest.direction, obviously the sane choice.
It turns out that this was fixed as la
Hi again,
I've seen that the snippet's still there :
http://lsr.di.unimi.it/LSR/Item?id=732
Shall I keep it or ?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi James,
Hi Harm,
Hi David,
On 2014-02-13 22:47 GMT+01:00 James wrote:
*Isn't there a standard practice for making a snippet shown as deprecated?*
Never heard of.
On 2014-02-14 0:10 GMT+01:00 Harm wrote:
*Did you succed contacting Seba already? *
No I don't. No answer up to now.
On 2014-02-14
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:87y51e5h6e@fencepost.gnu.org...
>> Thomas Morley writes:
>>
>>> Regarding the snippet:
>>> Because it is _not_ tagged docs I'd simply delete it.
>>
>> Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
>> on
"David Kastrup" wrote in message
news:87y51e5h6e@fencepost.gnu.org...
Thomas Morley writes:
Regarding the snippet:
Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them from Documentation/sn
James writes:
>> Actually 2.16 is what we want, so we get lucky here. But the point is
>> that most snippets will not be what is wanted. What one can do for any
>> particular snippet is something like
>>
>> git log -S '\version "2.16.0"' -p
>> Documentation/snippets/new/chant-or-psalms-notation
On 14/02/14 08:27, David Kastrup wrote:
James writes:
On 14/02/14 06:42, David Kastrup wrote:
Thomas Morley writes:
Regarding the snippet:
Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them
James writes:
> On 14/02/14 06:42, David Kastrup wrote:
>> Thomas Morley writes:
>>
>>> Regarding the snippet:
>>> Because it is _not_ tagged docs I'd simply delete it.
>> Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
>> one should just take them from Documentation/snipp
On 14/02/14 06:42, David Kastrup wrote:
Thomas Morley writes:
Regarding the snippet:
Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them from Documentation/snippets/new (if they
required changes
Thomas Morley writes:
> Regarding the snippet:
> Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them from Documentation/snippets/new (if they
required changes more than running convert-ly).
--
Da
2014-02-13 22:34 GMT+01:00 Pierre Perol-Schneider
:
> Dear Squad,
>
> Regarding this snippet : http://lsr.dsi.unimi.it/LSR/Item?id=732
> I'm not sure what am I suppose to do since rests are no more affected in
> v.2-18.
> Anyway it has been upgraded (but does it make sense).
>
> Any opinion ?
> Che
On 13/02/14 21:34, Pierre Perol-Schneider wrote:
Dear Squad,
Regarding this snippet : http://lsr.dsi.unimi.it/LSR/Item?id=732
I'm not sure what am I suppose to do since rests are no more affected in
v.2-18.
Anyway it has been upgraded (but does it make sense).
Any opinion ?
Cheers,
Pierre
_
Dear Squad,
Regarding this snippet : http://lsr.dsi.unimi.it/LSR/Item?id=732
I'm not sure what am I suppose to do since rests are no more affected in
v.2-18.
Anyway it has been upgraded (but does it make sense).
Any opinion ?
Cheers,
Pierre
___
bug-lily
13 matches
Mail list logo
