To round out my feature/bug tryptych (yes, this is the day that I make my score
not look crappy...sorry for all the traffic @ once...)
<>
\relative c'' { b1 \stopStaff \override Staff . StaffSymbol #'line-count = #1
\startStaff \tempo "Langsam" b1 b1 b1 }
\relative c'' { b1 \stopStaff \override
Well, no, I lied, just plain bug. I can't imagine this being a feature. But,
before I start working on it, does anyone have a clean work-around to get the
bendAfter spanning the line break correctly?
Cheers,
MS
<>
\score {
\new Staff << { s1*3 \break } \relative c' {
s1*2 \times 44/72 {\cresc
Hey all,
In the attached png, you'll see that the feathered beam resets to 0 feather @
the line break. Actually, it even regresses a bit: you'll see that it's
actually fatter at the linebreak than it is a couple beats after, after which
it starts to spread out again.
I would argue that the la
2011/2/5 Francisco Vila :
> 2011/2/5 Graham Percival :
>> On Sat, Feb 05, 2011 at 10:25:35AM +0100, Francisco Vila wrote:
>>> Is there a way of
>>> reviewing both pages publicly as they currently are on its branch?
>>
>
> OK, here is a preview.
> http://paconet.org/lilypond/out-website/website/inde
2011/2/6 Janek Warchoł :
> Carl Sorensen wrote:
>> Once you get to that point, just hit the escape key, then type :wq.
>> You are in vim, or some equivalent editor.
>
> I heard about vim...
> Yeah, so now i've experienced the Vim Joke and i have to admit that i
> fulfill the Vim hypothesis: i've ge
Great work!
I can't really speak to the font stuff. You can make your C++ code a
lot shorter by using arrays. And I see that you've wiped a lot of the
tabbing in the original code. You may want to start by copying a fresh
version of the file into your git repository and then copying and
pasting
Le 06/02/2011 04:21, percival.music...@gmail.com disait :
[...]
Documentation/notation/input.itely:526: @subsection Creating titles,
headers, and footers
I get nervous when the @subsection doesn't match the @node, but I can't
think of a definitely alternative after a few seconds. The only serious
Reviewers: ,
Message:
This is a bogus comment.
Am i doing this right?
Janek
Description:
shortened stems and flags
This improves the way that stems in forced directions are shortened and
adds loads of new flags to be used with these shortened stems.
Please review this at http://codereview.apps
"Keith OHara" wrote in message
news:loom.20110206t041824-...@post.gmane.org...
My issue-1500 patch slightly increased horizontal spacing in several
regtests
(reversing some of the tightening seen in the change from 2.13.24 to .25)
I changed 'lyrics-melisma-beam.ly' to make it more sensitive to
On 6 February 2011 11:55, Phil Holmes wrote:
>
> chord-tremolo-stem-direction.ly looks worse than before - is it now actually
> correct?
It is due to Han-Wen work on "beam scoring code".
Han-Wen, Carl, Werner and Reinhold discussed whether the new one was
better or worse than before (most preferr
- Original Message -
From: "Keith OHara"
To:
Sent: Sunday, February 06, 2011 3:29 AM
Subject: 2.13.48 regtests
Han Wen changed the placement of tremolo bars between semibreves, whole
notes.
chord-tremolo-stem-direction.ly looks worse than before - is it now actually
correct?
--
> Pál changed 'mensural-ligatures.ly' and perhaps can comment on whether the new
> output is what he intended.
changes in dot placement is intended, see the thread starting at
http://lists.gnu.org/archive/html/lilypond-devel/2011-01/msg00168.html
spacing is different at least because there are mo
12 matches
Mail list logo
