On 2012/12/16 08:09:38, dak wrote:
Well, the idea was to use this in pairs of contexts with otherwise
identical harakiri conditions, and give only one of them the
dead-is-alive flag. So one context pops up only when the other
doesn't.
I had the idea of using this with the Keep_alive_together
It doesn't like it when I end hairpins on note columns with stems
attached to cross-staff beams. I do not know why.
\new PianoStaff <<
\new Staff = "up" <<
{\voiceOne e''8. fis''16 g''2 fis''4 }
{s8\< s s s\! s\> s s s\!} >>
\new Staff = "down" {
\clef bass \voiceTwo
\change
LGTM
Trevor
https://codereview.appspot.com/6938071/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
I see that David Kastrup is currently fixing issue #1029
"\thumb should behave like other fingerings", thank you.
Does that mean that after the fix has been pushed \thumb will be
engraved by "Fingering_engraver" (or "New_Fingering_engraver", I do
not understand why there are two engravers)?
S
Hi,
Now that "Measure_counter_engraver" has been implemented into LilyPond
people can add a measure counter (great, thanks).
But unfortunately people have to start it and stop it _manually_,
using \startMeasureCount and \stopMeasureCount.
Could we add a feature to have an _automatic_ measure coun
Le 16/12/2012 20:54, Phil Holmes disait :
- Original Message - From: "Jean-Charles Malahieude"
To: "Phil Holmes"
Cc: "lilypond-devel"
Sent: Sunday, December 16, 2012 7:40 PM
Subject: Snippets' correction
Hi Phil,
Since you master the LRS-update, here is a patch concerning texidocs
tha
- Original Message -
From: "Jean-Charles Malahieude"
To: "Phil Holmes"
Cc: "lilypond-devel"
Sent: Sunday, December 16, 2012 7:40 PM
Subject: Snippets' correction
Hi Phil,
Since you master the LRS-update, here is a patch concerning texidocs
that have not been covered by convert-ly (
Hi Phil,
Since you master the LRS-update, here is a patch concerning texidocs
that have not been covered by convert-ly (resukt of a git grep "#'").
>From 55bc3ff354a61fa7c5cec78a5b6b17cd6fefeb80 Mon Sep 17 00:00:00 2001
From: Jean-Charles Malahieude
Date: Sun, 16 Dec 2012 20:11:00 +0100
Subje
LGTM
https://codereview.appspot.com/6940064/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Colin Hall-3 wrote
> As I understand it this is a request for a new feature in Lilypond
> that warns the user if they use \set on a property which can also be
> manipulated using \override and \revert.
>
> Have I correctly understood this and, if so, does it make sense to
> accept this feature req
On 14 déc. 2012, at 14:47, Kieren MacMillan
wrote:
> Hello all,
>
> Like many people on this list, I engrave a number of choral works using
> Lilypond. Like a smaller subset of those people, I engrave a number of large
> and very large works (musicals, operas, extended choral works, etc.), w
Hi all,
In spacing.itely (paragraph beginning on line 2127) I read this sentence:
"This means that the placement of a non-staff line depends
on both the surrounding staves and the surrounding non-staff lines.
Setting the @code{stretchability} of one of these types of spacing to
a small value wil
On 14 December 2012 14:47, Kieren MacMillan
wrote:
> Hello all,
>
> (snip)
>
> Ultimately, I would like to have Lilypond choose the correct number
> of staves so that horizontal and vertical spacing is optimal, using
> partcombine (or 'partexplode'?), cueing, etc., to accomplish its
> task.
>
> (s
Hi,
Eluze submitted a bug report here:
http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00036.html
As I understand it this is a request for a new feature in Lilypond
that warns the user if they use \set on a property which can also be
manipulated using \override and \revert.
Have I co
Hi,
Forwarded from bug-lilypond here:
http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00068.html
Looks like Yevgeny Lezhnin is investigating issue 2990. Perhaps you
guys can give him some feedback on this.
Cheers,
Colin.
- Forwarded message from Yevgeny Lezhnin -
Date: Sun
https://codereview.appspot.com/6845078/diff/19001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/6845078/diff/19001/Documentation/notation/input.itely#newcode1332
Documentation/notation/input.itely:1332: direction \footnote
[@va
Reviewers: Graham Percival,
Message:
On 2012/12/16 01:08:31, Graham Percival wrote:
could we get something in Changes.tely about this? No need to update
this
patch; you can push the modification to changse.tely immediately once
this patch
is accepted.
I did not do so on the theory that "b
k-ohara5...@oco.net writes:
On 2012/12/15 21:32:41, dak wrote:
The "dead-is-alive"-thing had the
advantage that even though I did not understand what I am
working with, it was easy to make it behave as advertised.
"This reverses the decisions that the Hara_kiri_engraver makes."
This engra
18 matches
Mail list logo
