On 06/20/2010 06:10 PM, David Kastrup wrote:
> People want a _solution_ to their problem, not new problems they never
> thought about and which are not actually in their personal problem
> space.
That's true, but it only shows that Lilypond isn't yet capable of
operating as a general-purpose best
Hi Jan,
Here are some more comments for you.
Cheers,
Neil
http://codereview.appspot.com/1579041/diff/19001/20003
File lily/metronome-engraver.cc (right):
http://codereview.appspot.com/1579041/diff/19001/20003#newcode81
lily/metronome-engraver.cc:81: && g->get_property_data
("break-align-symbo
On 19 June 2010 16:56, Marc Hohl wrote:
> Here it is.
Applied.
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM.
http://codereview.appspot.com/1681043/diff/1/2
File lily/grob.cc (right):
http://codereview.appspot.com/1681043/diff/1/2#newcode126
lily/grob.cc:126: bool grob_transparent = to_boolean (get_property
("transparent"));
This is a bit fussy. `transparent' will do, since it's clear from the
f
Hi Xavier,
Thanks for the comments...
It seems to me that the best situation would be to have a property like
#'show-marks in Staff, StaffGroup, and GrandStaff & PianoStaff, with a
#'marks-direction settable to #UP/#DOWN/#BOTH. The only big issue I can see
[conceptually] would be handling Fren
On 2010/06/19 04:55:25, Carl wrote:
Both versions can be used, according to Ross. The reason we have 2/8
standing
alone is to prevent 2/8, 3/8, and 4/8 from being beamed together in
3/4 time,
where that would be an error.
I don't consider that an error; it's traditional typesetting style.
On 18 June 2010 18:44, Jan Nieuwenhuizen wrote:
> I just do
>
> gdb out/bin/lilypond
> r
Unfortunately that doesn't help: it runs fine following the segfault,
just like the bare snippet does.
Cheers,
Neil
___
lilypond-devel mailing list
lilypond
LGTM.
http://codereview.appspot.com/1670042/diff/1/2
File input/regression/page-breaking-min-distance.ly (right):
http://codereview.appspot.com/1670042/diff/1/2#newcode1
input/regression/page-breaking-min-distance.ly:1: \version "2.13.22"
2.13.26
http://codereview.appspot.com/1670042/diff/1/2#
Le 20/06/2010 20:10, Reinhold Kainhofer disait :
Am Sonntag, 20. Juni 2010, um 11:00:33 schrieb Jean-Charles Malahieude:
Hi!
On a fresh build, I notice that all snippets in the docs are no longer
translated. It unfortunately seems to happen not just with me... and I
don't know when this has ap
Am Sonntag, 20. Juni 2010, um 11:00:33 schrieb Jean-Charles Malahieude:
> Hi!
>
> On a fresh build, I notice that all snippets in the docs are no longer
> translated. It unfortunately seems to happen not just with me... and I
> don't know when this has appeared.
> As a matter of fact, all "transla
Graham Percival writes:
> On Sun, Jun 20, 2010 at 5:10 PM, David Kastrup wrote:
>> People try to be editorially neutral, and not suggest any choice of
>> religion like vi, Emacs, whatever.
>
> http://lilypond.org/website/easier-editing.html
>
> "As a general rule, if you are not already familiar
2010/6/20 Graham Percival :
> Initializing settings for web site: [it]
> ** Node following `Notazione' in menu `Uso' and in sectionning
> `Utilizzo' differ
> ** `Utilizzo' doesn't appear in menus
> ** `Manuali' is up for `Utilizzo', but has no menu entry for this node
> ** No node following `Utiliz
Initializing settings for web site: [es]
WARNING: Unable to find node 'Text editor support' in book usage.
Initializing settings for web site: [it]
** Node following `Notazione' in menu `Uso' and in sectionning
`Utilizzo' differ
** `Utilizzo' doesn't appear in menus
** `Manuali' is up for `Utilizz
On Sun, Jun 20, 2010 at 5:10 PM, David Kastrup wrote:
> People try to be editorially neutral, and not suggest any choice of
> religion like vi, Emacs, whatever.
http://lilypond.org/website/easier-editing.html
"As a general rule, if you are not already familiar with Emacs or Vim,
then you would p
On Sat, 2010-06-19 at 12:00 -0400, lilypond-devel-requ...@gnu.org wrote:
> From: Laura Conrad
> Subject: Re: How to develop Emacs mode?
> To: Nicolas Sceaux
> Cc: David Kastrup , lilypond-devel@gnu.org
> Message-ID: <87wrtvazky@laymusic.org>
> Content-Type: text/plain; charset=us-ascii
>
> >
Joseph Wakeling writes:
> On 06/19/2010 07:50 PM, Valentin Villenave wrote:
>> Ditto here. I have contacted dozens of French universities, music
>> schools, government-funded music structures and whatnot. Everytime I
>> got an answer, the answer was: "Fuck off, we already have Finale".
>>
>> Or
2010/6/20 Jean-Charles Malahieude :
> Hi!
>
> On a fresh build, I notice that all snippets in the docs are no longer
> translated. It unfortunately seems to happen not just with me... and I don't
> know when this has appeared.
> As a matter of fact, all "translated headers" are present in
> Documen
On 06/19/2010 07:50 PM, Valentin Villenave wrote:
> Ditto here. I have contacted dozens of French universities, music
> schools, government-funded music structures and whatnot. Everytime I
> got an answer, the answer was: "Fuck off, we already have Finale".
>
> Or something like that.
What were t
Reviewers: ,
Message:
Mike,
There are still some issues in code formatting in stencil.scm.
The general principle in Scheme indentation is that we like to get as
much
as possible on a line. In particular,
* We never leave an opening parenthesis alone on a line
* We try to never leave a procedu
>> From a syntactical point of view, I can't see an immediate benefit of
>> saying
>>
>> #path:miter
>>
>> instead of
>>
>> #'miter
>
> Hm? Could you explain what constitutes a "syntactical point of
> view" in your book?
I probably misformulated. I simply mean that the `path:' prefix is an
2010/6/19 Graham Percival :
> I'm slightly uncomfortable giving "default values" in an .itely file,
Also do I,
> but
The patch is aimed to provide an example, not to give defaults, and
> IIRC the rest of spacing.itely does that anyway, so whatever.
> Thanks, pushed.
Thank you.
When the new sp
Thanks for doing this. I think this looks quite good.
As I mention below, I think it might be best to eliminate the "style"
arguments and make them part of the properties. We already have
'thickness as a property, and we could add 'path-details.
Or we could make 'path-thickness part of 'path-d
Hi!
On a fresh build, I notice that all snippets in the docs are no longer
translated. It unfortunately seems to happen not just with me... and I
don't know when this has appeared.
As a matter of fact, all "translated headers" are present in
Documentation/snippets; so, what's up doc?
Cheers,
Werner LEMBERG writes:
>>> Looks good to me. It would be nice if I could say
>>>
>>> \path #0.25 #'miter #'square ##f #samplePath
>>>
>>> instead of using numbers for the second and third parameter. Is this
>>> possible?
>>
>> How about defining constants path:miter and path:square instead?
24 matches
Mail list logo
