On 2010/01/10 06:40:56, Patrick McCarty wrote:
On 2010/01/10 05:03:30, joeneeman wrote:
http://codereview.appspot.com/186054/diff/1/2
File lily/pango-font.cc (right):
http://codereview.appspot.com/186054/diff/1/2#newcode384
lily/pango-font.cc:384: bool to_paths = get_program_option
Another nasty cutoff -- already in the PDF snippet as found in out-www
(attached for convenience) -- can be seen if you look at the output of
snippet/string-quartet-template-simple.ly
The lowest part of the system bracket is missing.
Werner
lily-6fc0ab3e-1.pdf
Description: Adobe PDF
[git 04213e5e]
The file snippet/displaying-complex-chords.ly isn't formatted
correctly: The sharp sign overlaps with the chord.
Has there been any change recently to lilypond which causes this
regression? Obviously some time ago this snippet gave correct
results...
Werner
On Sun, Jan 10, 2010 at 09:36:05AM -, Trevor Daniels wrote:
Graham Percival wrote Saturday, January 09, 2010 10:19 AM
In the past few months, we've had a number of developers being
surprised at some of the build system changes.
I don't think so. Most of the 'lesser' developers
don't
Le vendredi 08 janvier 2010 à 23:02 +, Trevor Daniels a écrit :
Why not qualify each of these generic words? Like
Graham did with Summary of contributing?
I second this for node names; as for section titles, they needn't be
unique, so we could use the same title 'Introduction' for each of
Hi, lilypond-2.12.3 is now available in openSUSE. It would be very much
appreciated if someone could update the lilypond download page with this
link :-
http://software.opensuse.org/search?baseproject=openSUSE%3A11.2p=1q=lilypond
The logo on the page is fine.
The above link is to a search page
On Sat, Jan 09, 2010 at 03:08:09PM -0800, Patrick McCarty wrote:
On 2010-01-09, Graham Percival wrote:
typography-demo.ly is already in the regtests. Do we want to keep
all the below?
- bach sarabande
- schubert morgenlier
- mozart horn concerto
- les-nereides
Yes, let's keep
On Sun, Jan 10, 2010 at 03:15:10PM +0100, John Mandereau wrote:
Le vendredi 08 janvier 2010 à 23:02 +, Trevor Daniels a écrit :
Why not qualify each of these generic words? Like
Graham did with Summary of contributing?
I second this for node names; as for section titles, they needn't
Hi Patrick (et al.),
for people who haven't used the LSR (lilypond snippet repository) before,
if you click on the pretty pictures of things you want to do,
they turn into lilypond code for you to learn from:) It's all automagic.
Your post brings up a good point: each LSR snippet page should
Graham Percival wrote Sunday, January 10, 2010 1:35 PM
On Sun, Jan 10, 2010 at 09:36:05AM -, Trevor Daniels wrote:
Graham Percival wrote Saturday, January 09, 2010 10:19 AM
In the past few months, we've had a number of developers being
surprised at some of the build system changes.
Graham Percival gra...@percival-music.ca writes:
On Sat, Jan 09, 2010 at 03:08:09PM -0800, Patrick McCarty wrote:
On 2010-01-09, Graham Percival wrote:
typography-demo.ly is already in the regtests. Do we want to keep
all the below?
- bach sarabande
- schubert morgenlier
- mozart
Trevor Daniels wrote:
Perhaps a special Subject: field would help, rather than
yet another list. All it need do is make the mail stand
out from other mails, like PLEASE RESPOND. Then copy such
mails directly to those developers whose opinion you seek,
as well as sending it to the -devel
Mark Polesky wrote:
Such posts would also be searchable on
http://lists.gnu.org/archive/html/lilypond-devel/ with
this string:
+subject:/^\!/
I meant to say:
+subject:/^!/
(I think). It's one of those.
- Mark
___
lilypond-devel
2010/1/10 Werner LEMBERG w...@gnu.org:
Has there been any change recently to lilypond which causes this
regression? Obviously some time ago this snippet gave correct
results...
Only due to a bug in accidental positioning: the two accidentals used
to be typeset in overstrike, so the
http://codereview.appspot.com/181144/diff/1009/29
File lily/span-bar.cc (right):
http://codereview.appspot.com/181144/diff/1009/29#newcode204
lily/span-bar.cc:204: else if (type == S)
You also need to pick up S./.S here, otherwise you'll get a nasty
surprise between staves ;)
else if
2010/1/8 Marc Hohl m...@hohlart.de:
Yes, the picture in the tracker has one loop missing, but in
all other sources, the sign looked (mainly) as mine.
How do they deal with the segno at the end of a line though? The
tracker example is aligned as a normal barline (i.e., with the
double-bar at
2010/1/1 Carl Sorensen c_soren...@byu.edu:
I think we should go ahead and push this patch (but if we need
to wait for the new chord name code, I guess we can do so)
If you're happy with the slight change in behaviour, that's fine by me.
Regards,
Neil
Le lundi 04 janvier 2010 à 15:03 -0800, Patrick McCarty a écrit :
I just fixed two of the gradient images in master. I didn't notice
them before because they are not currently used in the CSS. :-)
Great! I'm not sure whether the gradient image of this ones for hover
(for the first item of
-- Weitergeleitete Nachricht --
Betreff: Re: [Texi2html-bug] Converting texinfo comments to HTML comments
Datum: Montag, 11. Januar 2010
Von: Patrice Dumas pertu...@free.fr
An: texi2html-...@nongnu.org
On Tue, Jul 21, 2009 at 01:05:53AM +0200, Reinhold Kainhofer wrote:
Hi
http://www.codereview.appspot.com/181144/diff/1009/29
File lily/span-bar.cc (right):
http://www.codereview.appspot.com/181144/diff/1009/29#newcode204
lily/span-bar.cc:204: else if (type == S)
On 2010/01/10 20:50:38, Neil Puttock wrote:
You also need to pick up S./.S here, otherwise you'll get
Hey everyone. Here's a first draft of my idea for the new
CG chapter 2. I left out some obvious things to save space.
And of course there are unfinished spots, but it's a preview
of (I hope) the new Git chapter. I say I hope because I
worry that some of you might think it's too much?
Well,
21 matches
Mail list logo
