LGTM
I apologize that you had to wait. Thank you for your work!!
http://codereview.appspot.com/6189048/diff/9003/input/regression/collision-whole.ly
File input/regression/collision-whole.ly (right):
http://codereview.appspot.com/6189048/diff/9003/input/regression/collision-whole.ly#newcode16
i
Folks,
can someone with a fast machine please test whether a recent
texinfo.tex file works for the lilypond documentation? Simply replace
tex/texinfo.tex (temporarily) with this file:
http://cvs.savannah.gnu.org/viewvc/*checkout*/texinfo/doc/texinfo.tex?revision=1.365&root=texinfo
Wer
> we have
>
> txi-de.tex txi-en.tex txi-es.tex txi-fr.tex txi-hu.tex txi-it.tex
>
> in tex/, so I guess we also want txi-nl.tex.
Added.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lil
On 12-05-14 10:00 AM, James wrote:
ALso I am not sure if testing your own patches and changing them to
patch-review is 'good form'
+1 from a Controller!
I saw (USA?) Colin had started to test patches as well
Alberta, ekshully, or BST-7 (UTC -6). My machine (Acer Z5610
All-in-one: pretty,
On 12-05-14 07:13 AM, Joseph Rushton Wakeling wrote:
Might be a nice moment to see what I can do about that long-dormant
doc work. :-)
___
Let me know if I can help, Joseph, and welcome back!
Colin "the older one" Campbell
--
I've learned that y
Il giorno lun, 14/05/2012 alle 14.16 +0200, John Mandereau ha scritto:
> Hi guys,
>
> I just ran lilypond-patchy-staging.py, I'm sorry for the false failure
> notification, I have changed Texlive version on my computer since my
> last LilyPond build and did not install txi-??.tex files, so texi2pd
http://codereview.appspot.com/6190068/diff/1002/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
http://codereview.appspot.com/6190068/diff/1002/Documentation/web/community.itexi#newcode884
Documentation/web/community.itexi:884: for 2012 edition of the program;
w
http://codereview.appspot.com/6211047/diff/1/lily/beam.cc
File lily/beam.cc (right):
http://codereview.appspot.com/6211047/diff/1/lily/beam.cc#newcode1282
lily/beam.cc:1282: staff_span *= 0.5 / staff_space;
division is silly and works only because staff_space is generally 1.
http://codereview.a
New patch
http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely#newcode1044
Documentation/notation/input.itely:1044: Automatically n
LGTM
http://codereview.appspot.com/6211047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/6190068/diff/1002/Documentation/web/community.itexi
File Documentation/web/community.itexi (right):
http://codereview.appspot.com/6190068/diff/1002/Documentation/web/community.itexi#newcode884
Documentation/web/community.itexi:884: for 2012 edition of the program;
w
LGTM
http://codereview.appspot.com/6206061/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/6137050/diff/22001/Documentation/notation/input.itely#newcode1044
Documentation/notation/input.itely:1044: Automatically number
On Mon, 14 May 2012 03:32:11 -0700, wrote:
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode487
lily/lexer.ll:487: {FRACTION} {
On 2012/05/13 02:43:23, Keith wrote:
Stupid question, but I can't figure it out. Can we remove this
pattern from the
rules for individual sta
On Sun, May 13, 2012 at 11:34 PM, Graham Percival
wrote:
> On Sat, May 12, 2012 at 02:14:27PM +0200, Janek Warchoł wrote:
>> what changes in the LilyPond design should we make to make
>> LilyPond a more efficient and easy to use tool.
>
> LilyPond itself will remain as a command-line "compiler".
On 14 mai 2012, at 18:28, David Kastrup wrote:
> "m...@apollinemike.com" writes:
>
>> For me, it is faster to write a lot of kludgy code, see what it
>> breaks, and then write good code [1] rather than trying to write good
>> code from the get-go. So cheap regtests definitely help.
>
> That so
"m...@apollinemike.com" writes:
> For me, it is faster to write a lot of kludgy code, see what it
> breaks, and then write good code [1] rather than trying to write good
> code from the get-go. So cheap regtests definitely help.
That sounds uncomfortably like: "It's ok to design stuff above one
On 14 mai 2012, at 18:00, James wrote:
> Hello,
>
> On 14 May 2012 14:56, m...@apollinemike.com wrote:
>>
>> On 14 mai 2012, at 15:40, Graham Percival wrote:
>>
>>> On Mon, May 14, 2012 at 02:25:29PM +0200, John Mandereau wrote:
Hi Graham,
Il giorno dom, 13/05/2012 alle 19.24 +0200,
Hello,
On 14 May 2012 14:56, m...@apollinemike.com wrote:
>
> On 14 mai 2012, at 15:40, Graham Percival wrote:
>
>> On Mon, May 14, 2012 at 02:25:29PM +0200, John Mandereau wrote:
>>> Hi Graham,
>>> Il giorno dom, 13/05/2012 alle 19.24 +0200, Graham Percival ha scritto:
Agreed. I think the
2012/5/14 :
> Begin LilyPond compile, commit:
So you are back? Welcome, John!
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypon
Reviewers: Keith, Graham Percival,
Message:
As you can see, this draft comment did not get out in time but was
forgotten.
Looks like changing the version to 2.15.34 is now in your ballpark.
http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-seconds.ly
File input/regress
Il giorno lun, 14/05/2012 alle 15.46 +0200, Graham Percival ha scritto:
> On Mon, May 14, 2012 at 03:38:33PM +0200, John Mandereau wrote:
> > IIUC the "From:" field is not read from a config file but is hardcoded
> > in compile_lilypond_test.py:55, can we set up to a sensible default
> > value, or
Graham Percival writes:
> Tomorrow I'll go see the "science and technology" museum (maybe 4
> hours?),
4 weeks is more realistic.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypon
Han-Wen Nienhuys writes:
> On Mon, May 14, 2012 at 3:04 AM, David Kastrup wrote:
>>
>> "m...@apollinemike.com" writes:
>>
>> > One idea I've been a fan of for a long time is some type of aux file
>> > system in LilyPond. That is, if we can come up with a file format
>> > that stores loads of d
On Mon, May 14, 2012 at 3:04 AM, David Kastrup wrote:
>
> "m...@apollinemike.com" writes:
>
> > One idea I've been a fan of for a long time is some type of aux file
> > system in LilyPond. That is, if we can come up with a file format
> > that stores loads of data from previous runs of a score a
On Mon, May 14, 2012 at 01:48:54PM +0200, Joseph Rushton Wakeling wrote:
> On 14/05/12 11:41, David Kastrup wrote:
> >
>
> Before saying anything more, I'm sorry if my earlier email was
> offensive or intemperate; it wasn't meant to be.
Ditto.
> I was writing out of concern for the ease of contr
On 14 mai 2012, at 15:40, Graham Percival wrote:
> On Mon, May 14, 2012 at 02:25:29PM +0200, John Mandereau wrote:
>> Hi Graham,
>> Il giorno dom, 13/05/2012 alle 19.24 +0200, Graham Percival ha scritto:
>>> Agreed. I think the most we'd use it for would be LSR. I don't
>>> think we should give
Joseph Rushton Wakeling writes:
> One of the frustrations on that occasion a year ago was that I would
> have been quite likely on my own initiative to see if I could do
> anything, _if_ I hadn't been treated to the lecture.
It is a reasonably safe guess that the "lecture" had been by Graham.
Gr
On Mon, May 14, 2012 at 03:38:33PM +0200, John Mandereau wrote:
> IIUC the "From:" field is not read from a config file but is hardcoded
> in compile_lilypond_test.py:55, can we set up to a sensible default
> value, or should it be made configurable?
Either is fine with me. A sensible default val
On Mon, May 14, 2012 at 02:25:29PM +0200, John Mandereau wrote:
> Hi Graham,
> Il giorno dom, 13/05/2012 alle 19.24 +0200, Graham Percival ha scritto:
> > Agreed. I think the most we'd use it for would be LSR. I don't
> > think we should give ssh logins to developers for testing patches;
> > that
Il giorno lun, 14/05/2012 alle 15.18 +0200, Graham Percival ha scritto:
> On Mon, May 14, 2012 at 03:07:23PM +0200, John Mandereau wrote:
> > Ok, this time I got
> >
> > $ cat /home/lilydev/lilypond-auto-compile-results/log-2012-05-14-14.txt
> > Begin LilyPond compile, commit: c597a126f11943be
On Mon, May 14, 2012 at 09:52:32AM +0200, Joseph Rushton Wakeling wrote:
> On 14/05/12 07:37, Graham Percival wrote:
> >No. LilyPond is a command-line "compiler". That's something that
> >would happen in an alternate program.
>
> I'm not disputing that, or suggesting that you go into GUI/IDE
> t
On Mon, May 14, 2012 at 01:51:42PM +0200, Joseph Rushton Wakeling wrote:
> On 14/05/12 11:47, m...@apollinemike.com wrote:
> >This is very hard because of the butterfly effect - an A-flat in an
> >already-crammed line could lead to new line breaking, which means new
> >vertical spacing etc..
>
>
James writes:
> I don't know the ramifications of running two merges at the same time
None, really. The worst is when the second merge starts from a later
version of origin/staging and still finishes first.
In that case, the first merge will flag an error when it tries pushing
an already super
On 14/05/12 14:36, David Kastrup wrote:
It is not like the graphical frontends are not mentioned in LilyPond's
documentation. Have you checked
http://lilypond.org/doc/v2.15/Documentation/web/easier-editing#Score_002c-tab-and-MIDI-editors_003a>?
Personally I'm a Frescobaldi fan. MuseScore is a
On Mon, May 14, 2012 at 03:07:23PM +0200, John Mandereau wrote:
> Ok, this time I got
>
> $ cat /home/lilydev/lilypond-auto-compile-results/log-2012-05-14-14.txt
> Begin LilyPond compile, commit: c597a126f11943be74a98efee056ab54ae729315
> Merged staging, now at: c597a126f11943be74a98ef
On 14/05/12 14:15, David Kastrup wrote:
They are treated by the bug squad picking up the suggestion and filing
it in the issue problem.
If someone suggested to you that they will refuse doing that, that
someone was not giving you correct information.
OK. :-)
To be fair, reconsidering things,
John,
On 14 May 2012 12:52, wrote:
> Begin LilyPond compile, commit: c597a126f11943be74a98efee056ab54ae729315
>
> Merged staging, now at: c597a126f11943be74a98efee056ab54ae729315
>
> Success: ./autogen.sh --noconfigure
>
> Success: ../configure --disab
Ok, this time I got
$ cat /home/lilydev/lilypond-auto-compile-results/log-2012-05-14-14.txt
Begin LilyPond compile, commit: c597a126f11943be74a98efee056ab54ae729315
Merged staging, now at: c597a126f11943be74a98efee056ab54ae729315
Success:./autogen.sh --noconfigure
S
Il giorno lun, 14/05/2012 alle 14.44 +0200, David Kastrup ha scritto:
> John Mandereau writes:
>
> > Hi guys,
> >
> > I just ran lilypond-patchy-staging.py, I'm sorry for the false failure
> > notification, I have changed Texlive version on my computer since my
> > last LilyPond build and did not
john.mander...@gmail.com writes:
> Begin LilyPond compile, commit: c597a126f11943be74a98efee056ab54ae729315
>
> Merged staging, now at: c597a126f11943be74a98efee056ab54ae729315
>
> Success:./autogen.sh --noconfigure
>
> Success:../configure -
John Mandereau writes:
> Hi guys,
>
> I just ran lilypond-patchy-staging.py, I'm sorry for the false failure
> notification, I have changed Texlive version on my computer since my
> last LilyPond build and did not install txi-??.tex files, so texi2pdf
> choked on translated manuals. I'm disablin
Joseph Rushton Wakeling writes:
> On 14/05/12 11:47, m...@apollinemike.com wrote:
>> This is very hard because of the butterfly effect - an A-flat in an
>> already-crammed line could lead to new line breaking, which means
>> new vertical spacing etc..
>
> I don't assume it would be easy! But ena
Hi Graham,
Il giorno dom, 13/05/2012 alle 19.24 +0200, Graham Percival ha scritto:
> Agreed. I think the most we'd use it for would be LSR. I don't
> think we should give ssh logins to developers for testing patches;
> that should be done locally otherwise it could easily lead to
> major headache
Hi guys,
I just ran lilypond-patchy-staging.py, I'm sorry for the false failure
notification, I have changed Texlive version on my computer since my
last LilyPond build and did not install txi-??.tex files, so texi2pdf
choked on translated manuals. I'm disabling email sending, at least
until I ge
Joseph Rushton Wakeling writes:
> It's not trivial if I have to install custom code in order to submit a
> tiny doc patch!
>
> If I were hacking on LP itself then it would surely be a small issue
> by comparison, but I wasn't, and I don't think small tweak-y
> contributions should be treated this
On 2012/05/14 10:32:11, dak wrote:
So the answer to this question is: no. Maybe it has to do with the
starting
state specific UNSIGNED rules firing with priority then. I'll try
moving the
FRACTION rule up, but am sceptical that this will work out better, so
just let's
keep the unchanged
Begin LilyPond compile, commit: c597a126f11943be74a98efee056ab54ae729315
Merged staging, now at: c597a126f11943be74a98efee056ab54ae729315
Success:./autogen.sh --noconfigure
Success:../configure --disable-optimising
Success:
On 14/05/12 11:47, m...@apollinemike.com wrote:
This is very hard because of the butterfly effect - an A-flat in an
already-crammed line could lead to new line breaking, which means new vertical
spacing etc..
I don't assume it would be easy! But enabling GUI/IDE developers to build
function
On 14/05/12 11:41, David Kastrup wrote:
Before saying anything more, I'm sorry if my earlier email was offensive or
intemperate; it wasn't meant to be. I was writing out of concern for the ease
of contributing to LilyPond (more on that in a moment).
Have you actually used Rietveld for re
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll
File lily/lexer.ll (right):
http://codereview.appspot.com/6200068/diff/2001/lily/lexer.ll#newcode487
lily/lexer.ll:487: {FRACTION} {
On 2012/05/13 02:43:23, Keith wrote:
Stupid question, but I can't figure it out. Can we remove th
Joseph Rushton Wakeling writes:
> On 14/05/12 09:56, David Kastrup wrote:
>> http://lilypond.org/doc/v2.15/Documentation/source/Documentation/notation/skipping-corrected-music>
>
> Yes, but that wasn't the use-case I had in mind. The sort of thing I
> was thinking of was:
>
> (i) I have a fu
On 14 mai 2012, at 11:22, Joseph Rushton Wakeling wrote:
> On 14/05/12 09:56, David Kastrup wrote:
>> http://lilypond.org/doc/v2.15/Documentation/source/Documentation/notation/skipping-corrected-music>
>
> Yes, but that wasn't the use-case I had in mind. The sort of thing I was
> thinking of wa
Joseph Rushton Wakeling writes:
> On 14/05/12 09:46, David Kastrup wrote:
>> We don't have a canonical developer, one whose personal
>> branch/repository would be official for the project.
>
> GitHub and Launchpad both permit branches to be owned by groups as
> well as individuals. I'm sure othe
On 14/05/12 09:56, David Kastrup wrote:
http://lilypond.org/doc/v2.15/Documentation/source/Documentation/notation/skipping-corrected-music>
Yes, but that wasn't the use-case I had in mind. The sort of thing I was
thinking of was:
(i) I have a full, complete score, which I have compiled.
On 14/05/12 09:46, David Kastrup wrote:
We don't have a canonical developer, one whose personal
branch/repository would be official for the project.
GitHub and Launchpad both permit branches to be owned by groups as well as
individuals. I'm sure other DVCS-based code hosts do as well, but tho
Joseph Rushton Wakeling writes:
> On 14/05/12 07:37, Graham Percival wrote:
>> No. LilyPond is a command-line "compiler". That's something that
>> would happen in an alternate program.
>
> I'm not disputing that, or suggesting that you go into GUI/IDE
> territory directly -- what I'm suggesting
On 14/05/12 07:37, Graham Percival wrote:
No. LilyPond is a command-line "compiler". That's something that
would happen in an alternate program.
I'm not disputing that, or suggesting that you go into GUI/IDE territory
directly -- what I'm suggesting is that consideration be given to what mig
Joseph Rushton Wakeling writes:
> On 14/05/12 07:35, Graham Percival wrote:
>> On Mon, May 14, 2012 at 03:38:54AM +0200, Joseph Rushton Wakeling wrote:
>>> Here you go. :-) Let me know if it needs tweaking or might be
>>> better in another section of the guide.
>>
>> Please see the "summary for
http://codereview.appspot.com/6197068/diff/1/Documentation/notation/staff.itely
File Documentation/notation/staff.itely (right):
http://codereview.appspot.com/6197068/diff/1/Documentation/notation/staff.itely#newcode1361
Documentation/notation/staff.itely:1361: \new CueVoice { \set
"instrumentCu
David Kastrup writes:
>> No. LilyPond is a command-line "compiler". That's something that
>> would happen in an alternate program.
Possibly Something like Ikebana or Schikkers List
> LilyPond, as opposed to TeX, is a living project and one does not need
> to think of everything in advance.
Ri
61 matches
Mail list logo
