Carl Sorensen writes:
> On May 5, 2012, at 8:16 PM, "David Kastrup" wrote:
>
>>
>> But what about <>\footnote: that does not have this problem.
>>
>> In fact, isn't <> generally prettier than s1*0? Should we be using it
>> in code and documentation rather than s1*0?
>
>
> What a great idea!
>> But what about <>\footnote: that does not have this problem.
>>
>> In fact, isn't <> generally prettier than s1*0? Should we be using
>> it in code and documentation rather than s1*0?
>
>
> What a great idea! No notes generated; the duration doesn't
> change.
Indeed! I wasn't aware that <>
On May 5, 2012, at 8:16 PM, "David Kastrup" wrote:
>
> But what about <>\footnote: that does not have this problem.
>
> In fact, isn't <> generally prettier than s1*0? Should we be using it
> in code and documentation rather than s1*0?
What a great idea! No notes generated; the duration d
Quoting David Kastrup :
We can probably use yes:400600[0-2]) here: 4.6.3 is supposed to contain
the fix.
Thank you for opening a separate ticket for it (2514) and reviewing my
ticket (2513)!
--
Regards,
Pavel Roskin
___
lilypond-devel mailing li
Hi,
thinking about a replacement rule for turning \footnote into a
postevent, I was thinking about replacing \footnote, if not preceded by
- ^ _, into s1*0\footnote. However, this has the disadvantage of
changing the default duration if a note without duration follows.
But what about <>\footnot
On Thu, 03 May 2012 16:20:45 -0700, Łukasz Czerwiński
wrote:
On 3 May 2012 04:18, Keith OHara wrote:
On Wed, 02 May 2012 17:12:33 -0700, Łukasz Czerwiński
And where to find what's min_length_fraction for? Googling that didn't help...
It is a local variable holding [...] property of a
Ledge
On Sat, May 05, 2012 at 09:57:07AM +0700, Michael Pozhidaev wrote:
> After the last announce I have tried the linux x86_64 binary package of
> lilypond-2.15.38 to see what is going to be in 2.16. It works but I met
> some regressions in midi output comparing with 2.14.2 currently I am
> working wit
Reviewers: ,
Message:
this patch makes staff_radius work in cases when line-positions is
overridden. so long staff_radius assumed overriding at most line-count.
http://codereview.appspot.com/6202048/diff/1/lily/tuplet-bracket.cc
File lily/tuplet-bracket.cc (left):
http://codereview.appspot.co
Hello,
On 5 May 2012 03:57, Michael Pozhidaev wrote:
> Hello!
>
> After the last announce I have tried the linux x86_64 binary package of
> lilypond-2.15.38 to see what is going to be in 2.16. It works but I met
> some regressions in midi output comparing with 2.14.2 currently I am
> working with
Hello!
After the last announce I have tried the linux x86_64 binary package of
lilypond-2.15.38 to see what is going to be in 2.16. It works but I met
some regressions in midi output comparing with 2.14.2 currently I am
working with.
At first attempt I didn't find out how to workaround them. Basi
On 2012/05/05 16:58:22, benko.pal wrote:
thank you very much! please add Beam_performer too to ensure
consistency with
Voice (may be needed when doing ancient and modern edition from a
common
source).
Added Beam_performer for Vaticana and Mensural based on this comment.
http://codereview.
On Sat, May 05, 2012 at 10:35:02AM +0200, Federico Bruni wrote:
> Il 25/04/2012 12:04, Graham Percival ha scritto:
> [..]
> >>> I'm trying to learn Python and I'd like to contribute to some frog
> >>> tasks requiring python (I've starred some frog issues in the tracker).
> >>> Probably this is t
hi Aleksandr,
I've uploaded a patch that gets at Vaticana and Mensural as well. It
seems that
"Beam_performer" would not be necessary for the two, but I don't know
about
"Tie_performer" and "Slur_performer". It would probably be good for
someone who
knows more than me about Gregorian chant
On Sat, May 05, 2012 at 08:07:44AM +, lilyp...@googlecode.com wrote:
>
> Comment #8 on issue 2476 by elu...@gmail.com: Doc AU: Using escape
> characters in different shells for -doptions can be inconsistent
> http://code.google.com/p/lilypond/issues/detail?id=2476
>
> the problem occurs only
LGTM
http://codereview.appspot.com/5976056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Le 04/05/2012 17:34, Francisco Vila disait :
2012/5/4 Phil Holmes:
I think the way to do this would be to have makelsr.py extract the texidoc
and doctitle strings from the snippets and to put them into
Documentation/texidoc/. In principle it would delete them from the snippet,
and then put them
Il 25/04/2012 12:04, Graham Percival ha scritto:
[..]
> I'm trying to learn Python and I'd like to contribute to some frog
> tasks requiring python (I've starred some frog issues in the tracker).
> Probably this is too much difficult for a newbie.
Actually, I've got a good suggestion on how y
17 matches
Mail list logo
