Am 18.09.2012 07:16, schrieb Graham Percival:
On Sun, Sep 16, 2012 at 09:06:10PM +0200, Marc Hohl wrote:
So I looked at
http://lilypond.org/doc/v2.17/Documentation/contributor/lsr-to-git
and I wonder if these changes should be included
*in* the barline patch or the procedure described in the l
> Please follow the instructions here
> http://lilypond.org/doc/v2.15/Documentation/contributor/summary-for-experienced-developers
> or at least add a tracker with the raw patch attached directly. It
> won't be a candidate for reviewing and pushing, but at least it
> would be easier for other peo
Uh, oh, please ignore the new stuff.
http://codereview.appspot.com/6459081/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/6450113/diff/8003/scm/fret-diagrams.scm
File scm/fret-diagrams.scm (right):
http://codereview.appspot.com/6450113/diff/8003/scm/fret-diagrams.scm#newcode642
scm/fret-diagrams.scm:642: (corner1
On 2012/09/18 04:52:05, Graham Percival wrote:
Could we get a comment
On Sun, Sep 16, 2012 at 12:02:59PM +0200, Werner LEMBERG wrote:
>
> > you find attached 8 files: one .txt file containing seven
> > documentation entries and seven .ly files for each entry.
>
> I've now edited your contribution; attached is a patch. Documentation
> team, please comment and integ
On Sun, Sep 16, 2012 at 09:06:10PM +0200, Marc Hohl wrote:
> So I looked at
>
> http://lilypond.org/doc/v2.17/Documentation/contributor/lsr-to-git
>
> and I wonder if these changes should be included
> *in* the barline patch or the procedure described in the link
> above should be done *after* it
http://codereview.appspot.com/6450113/diff/8003/scm/fret-diagrams.scm
File scm/fret-diagrams.scm (right):
http://codereview.appspot.com/6450113/diff/8003/scm/fret-diagrams.scm#newcode642
scm/fret-diagrams.scm:642: (corner1
from the context, I gather than corner1 is not guaranteed to be
lower-lef
>> ... but as David has correctly mentioned previously, it is not
>> fruitful to discuss something for a long time and make everyone
>> agree to it, just to find out later on that the idea can't be
>> implemented in the current framework.
>
> I agree that doing so isn't fruitful. However, it may
http://codereview.appspot.com/6489107/diff/9001/lily/spacing-spanner.cc
File lily/spacing-spanner.cc (left):
http://codereview.appspot.com/6489107/diff/9001/lily/spacing-spanner.cc#oldcode274
lily/spacing-spanner.cc:274: doesn't touch the right column. */
This comment tells me what the code did,
On 17/09/12 13:38, David Kastrup wrote:
So what would be required here seemingly would be linearization of the
spacing in absence of note columns which convey proper timing through
their note values, however non-linearly spaced.
Actually, this is an interesting question for people to examine in
I recently changed
http://lsr.dsi.unimi.it/LSR/Item?id=233
now the image in LSR is cut off by 1/3 of the first stave. I've no clue why.
A simple work-around would be to add \markup \vspace #1 on top of the
code. (I tested it)
But this snippet is tagged docs and part of /documentation/snippets:
cen
Dear developers,
Thank you for your work on lilypond.
What about considering ( as a post-event and ) as a standalone event ?
c( )d( )e is symmetric and very clear.
best regards,
Mathieu
On Thu, Sep 13, 2012 at 2:27 AM, David Kastrup wrote:
> I don't think that distributing ( and ) betw
Janek Warchoł writes:
> On Sat, Sep 15, 2012 at 5:25 PM, Werner LEMBERG wrote:
>>
>>> If there is widespread agreement that the idea is good, then at some
>>> point it could be implemented.
>>
>> ... but as David has correctly mentioned previously, it is not
>> fruitful to discuss something for
On Sat, Sep 15, 2012 at 5:25 PM, Werner LEMBERG wrote:
>
>> If there is widespread agreement that the idea is good, then at some
>> point it could be implemented.
>
> ... but as David has correctly mentioned previously, it is not
> fruitful to discuss something for a long time and make everyone ag
James,
On Sat, Sep 15, 2012 at 3:45 PM, James wrote:
>
>> Third, the numbers of short user-definable abbreviations gets halved.
>> Something like
>>
>> F = \markup { "Horn in F" }
>>
>> would no longer be possible because \f is already in use.
>
> So what? You are a developer, fix that. I do wa
Mathieu Huiban writes:
>> On Thu, Sep 13, 2012 at 2:27 AM, David Kastrup wrote:
>>
>>> I don't think that distributing ( and ) between standalone event and
>>> post-event respectively is a concept that will carry the day
>>> sufficiently to be given a chance at a comeback. It would make
>>> (c
m...@mikesolomon.org wrote
>
> They are actually commands to the path stencil - they look like native
> PS commands because they use the same lingo. If your backend implements
> the path stencil, LilyPond should do the rest of the work for you,
> outputting slurs and ties as paths instead of
Joseph Rushton Wakeling writes:
> On 13/09/12 08:11, David Kastrup wrote:
>> If it does, so does
>>
>> << c'1 { s4 s\< s2 s\! } >>
>
> Stepping back from syntax for a second,
Let's keep that in mind.
> the problem with the above (as currently implemented) is that the
> spacing will not produce
Graham Percival writes:
> David, after Waltrop I was really enthusiastic about lilypond. I
> saw the problems that Rudolfo had in trying to make a simple
> change to the website, and I was really fired up to fix the
> problems in the CG. I was also fired up to organize weekly
> discussions on i
On 13/09/12 08:11, David Kastrup wrote:
If it does, so does
<< c'1 { s4 s\< s2 s\! } >>
Stepping back from syntax for a second, the problem with the above (as currently
implemented) is that the spacing will not produce correct output from a visual
engraving point of view. This applies also
On 2012-09-17 05:01, ornello wrote:
James wrote
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=35725a573e47be7c02c51964641ea534fb88be6b
Does this help?
james
Hmm... I see that in lookup.cc the call to the backend function
bezier-sandwich has been replaced by native PS c
James wrote
>
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=35725a573e47be7c02c51964641ea534fb88be6b
>
> Does this help?
>
> james
>
Hmm... I see that in lookup.cc the call to the backend function
bezier-sandwich has been replaced by native PS commands. I don't find a
be
Hello,
On 17 September 2012 10:56, ornello wrote:
> In 2.16.0 the backend callback function bezier-sandwich has been eliminated.
> What is the replacement function called for creating slurs in the backend?
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=35725a573e47be7c02c51964
http://codereview.appspot.com/6450113/diff/8003/scm/fret-diagrams.scm
File scm/fret-diagrams.scm (right):
http://codereview.appspot.com/6450113/diff/8003/scm/fret-diagrams.scm#newcode649
scm/fret-diagrams.scm:649: (ordered-cons (car corner1) (car corner2))
I was wondering whether it would not ma
In 2.16.0 the backend callback function bezier-sandwich has been eliminated.
What is the replacement function called for creating slurs in the backend?
Greetings,
Dominik
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Replacement-for-backend-function-bezier-sandwich-tp1
I won't be pushing 2823 at this point - we've agreed that the clef needs
changing completely. I have a copy of the metafont book being delivered
--
Phil Holmes
- Original Message -
From: Colin Campbell
To: Devel
Sent: Monday, September 17, 2012 3:59 AM
Subject: PATCH:
2012/9/17 David Kastrup :
> Francisco Vila writes:
>
>> 2012/9/16 David Kastrup :
>>> This is the developer list, after all.
>>
>> Hey, I have the Dragon Book in my bedside table, I can give a language
>> to my daughter for her birthday, and still find some things difficult.
>
> Why am I the one f
Francisco Vila writes:
> 2012/9/16 David Kastrup :
>> This is the developer list, after all.
>
> Hey, I have the Dragon Book in my bedside table, I can give a language
> to my daughter for her birthday, and still find some things difficult.
Why am I the one figuring out then until which time I c
Am 17.09.2012 08:15, schrieb Keith OHara:
Marc Hohl hohlart.de> writes:
The testing process works fine on my local
machine, but 'make doc' fails due to some
syntax changes in the snippets. For example,
defaultBarType = "empty" will not work once
the patch is applied.
and I wonder if these cha
29 matches
Mail list logo
