On 26 juin 2012, at 18:26, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It’s clearly a big
problem, but this isn’t something we can fix by waving a change of
policy. I’ll schedule a time to discuss it. We need to do
Am 29.06.2012 08:05, schrieb m...@apollinemike.com:
On 26 juin 2012, at 18:26, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It’s clearly a big
problem, but this isn’t something we can fix by waving a change of
policy. I’ll
m...@apollinemike.com m...@apollinemike.com writes:
Sorry for the long delay. The second batch of dates in August are
doable for me (Friday the 24th to Tuesday the 28th). Keep me posted!
Ok with those who already said they could make the first date?
--
David Kastrup
On Wed, Jun 27, 2012 at 8:19 PM, Graham Percival
gra...@percival-music.ca wrote:
Having never used scheme or C++ in
lilypond to fix a bug, I'm curious to find out how it's done.
The Graham Way of fixing bugs: mark the issue as Invalid ;-)
___
Sorry for the long delay. The second batch of dates in August are
doable for me (Friday the 24th to Tuesday the 28th). Keep me posted!
Ok with those who already said they could make the first date?
I've booked my flights (15th to 20th) already some weeks ago, but this
shouldn't be a
Werner LEMBERG w...@gnu.org writes:
Sorry for the long delay. The second batch of dates in August are
doable for me (Friday the 24th to Tuesday the 28th). Keep me posted!
Ok with those who already said they could make the first date?
I've booked my flights (15th to 20th) already some
Janek Warchoł janek.lilyp...@gmail.com writes:
On Wed, Jun 27, 2012 at 8:19 PM, Graham Percival
gra...@percival-music.ca wrote:
Having never used scheme or C++ in
lilypond to fix a bug, I'm curious to find out how it's done.
The Graham Way of fixing bugs: mark the issue as Invalid ;-)
The
Pity. If you say you booked your flights already for the sake of
visiting your relatives, this would probably imply that you would
not likely have had more than a day to spare anyway, right?
Werner
___
lilypond-devel mailing list
Hey Julien,
thanks a million!
Cheers,
patrick
http://codereview.appspot.com/5697059/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2012/6/28 d...@gnu.org:
A feature should be documented, or it will not be discoverable.
Of course all features (old and new) should be documented.
But, AFAICT, non of the possibilities offered in /ly/titling-init.ly
(i.e. first-page, last-page, not-first-page, part-last-page) is
documented
2012/6/29 David Kastrup d...@gnu.org:
(...)
That's a patch 2/2. In this case, you don't really want to have two
separate commits, but replace the previous commit with a changed one.
The usual way to do that is to commit with git commit --amend ...
Now that you already have made two commits,
On Fri, Jun 29, 2012 at 11:32:53AM +0200, Thomas Morley wrote:
2012/6/28 d...@gnu.org:
A feature should be documented, or it will not be discoverable.
Well, they should be documented, but I propose to open a new issue to do so.
That sounds sensible. In the past we've said that new
Thomas Morley wrote Friday, June 29, 2012 10:32 AM
Of course all features (old and new) should be documented.
But, AFAICT, non of the possibilities offered in /ly/titling-init.ly
(i.e. first-page, last-page, not-first-page, part-last-page) is
documented anywhere in LM or NR.
Well, they
LGTM, I think. I'm not completely certain what I'm reviewing here.
I'm content to have this (whatever it is) go through, but in the future
could you:
- keep you changes in a separate git branch (locally)
- run: git cl upload origin/master
while on that local git branch.
Yes, this will
LGTM
http://codereview.appspot.com/6343055/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM.
http://codereview.appspot.com/6352053/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Il giorno ven, 29/06/2012 alle 11.00 +, gra...@percival-music.ca ha
scritto:
LGTM, I think. I'm not completely certain what I'm reviewing here.
I'm content to have this (whatever it is) go through, but in the future
could you:
- keep you changes in a separate git branch (locally)
-
John Mandereau john.mander...@gmail.com writes:
Il giorno ven, 29/06/2012 alle 11.00 +, gra...@percival-music.ca ha
scritto:
LGTM, I think. I'm not completely certain what I'm reviewing here.
I'm content to have this (whatever it is) go through, but in the future
could you:
- keep
Hey all,
John and I went to the Maison des Sciences de l'Homme today to get the LilyPond
server up and running. We'll be doing a few modifications over the next few
days and, once it's ready to be used by the devel team, we'll let you guys
know. Just a quick note now, though, to let you know
Assuming from the contents that this was intended as a public response
(the foreigners bit does not make sense otherwise).
Werner LEMBERG w...@gnu.org writes:
Pity. If you say you booked your flights already for the sake of
visiting your relatives, this would probably imply that you would
On 29 juin 2012, at 16:59, David Kastrup wrote:
Assuming from the contents that this was intended as a public response
(the foreigners bit does not make sense otherwise).
Werner LEMBERG w...@gnu.org writes:
Pity. If you say you booked your flights already for the sake of
visiting your
Il giorno ven, 29/06/2012 alle 16.59 +0200, David Kastrup ha scritto:
Well, if there are no other relevant feedbacks today, I am moving for
the second date then (August 24th to 28th). It is a pity that we won't
get everyone covered, but that's life. It doesn't preclude at least us
two
LGTM with one proposed change.
http://codereview.appspot.com/6352053/diff/1/scripts/auxiliar/makelsr.py
File scripts/auxiliar/makelsr.py (right):
http://codereview.appspot.com/6352053/diff/1/scripts/auxiliar/makelsr.py#newcode79
scripts/auxiliar/makelsr.py:79: default=out/bin,
This all looks
On Fri, Jun 29, 2012 at 03:56:03PM +, philehol...@googlemail.com wrote:
http://codereview.appspot.com/6352053/diff/1/scripts/auxiliar/makelsr.py#newcode79
scripts/auxiliar/makelsr.py:79: default=out/bin,
...
it would be better if the default was the build/out directory, and if
convert-ly
On Tue, Jun 26, 2012 at 6:26 PM, David Kastrup d...@gnu.org wrote:
[...]
So the core data would be Dortmund Germany (about 10 miles from there)
and the proposal for a date would Friday August 17th to Tuesday August
21st, or one week later.
Excellent! Both options are ok to me, with a small
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: john.mander...@gmail.com; philehol...@googlemail.com;
lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com
Sent: Friday, June 29, 2012 5:27 PM
Subject: Re: Get texidoc translations out of snippets source
On Thu, Jun 28, 2012 at 11:39 PM, Graham Percival
gra...@percival-music.ca wrote:
On Thu, Jun 28, 2012 at 08:46:09PM +0200, Janek Warchoł wrote:
i see that some very interesting things are happening.
I was inactive in the last days because i've contracted pneumonia, argh...
:-[
I hope to
On Thu, Jun 28, 2012 at 8:46 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
I was inactive in the last days because i've contracted pneumonia, argh...
:-[
I hope to participate a bit in the discussions, but not as much as i'd like
to.
Oh dear. Get well soon, I hope this won't be too long
On Fri, Jun 29, 2012 at 5:05 PM, m...@apollinemike.com
m...@apollinemike.com wrote:
I can be there for those dates (24th to 28th). Perhaps not all as I am
moving apartments around the 28th but definitely for 2 or 3 days!
Oh, then please let me know if you're flying from France, perhaps I
On Fri, Jun 29, 2012 at 11:03:27PM +0200, Valentin Villenave wrote:
On Fri, Jun 29, 2012 at 5:05 PM, m...@apollinemike.com
m...@apollinemike.com wrote:
I can be there for those dates (24th to 28th). Perhaps not all as I am
moving apartments around the 28th but definitely for 2 or 3 days!
On 12-06-27 08:06 AM, Matthieu Leschemelle wrote:
Hello,
I'm the designer and developer of TablEdit, tablature editor.
TablEdit exports ly files for two years.
http://www.tabledit.com/screen/lilypond.shtml
I'd like to be mentioned in the list of programs supporting LilyPond.
Would it be
Folks,
I'm quite allergic to overly long lines in any kind of documents.
Particularly the various Makefiles have become unreadable IMHO, so I
suggest something similar to the attached version of the top-level
`GNUmakefile.in'. What do you think?
Werner
PS: If you want to compare with
I'm quite allergic to overly long lines in any kind of documents.
Particularly the various Makefiles have become unreadable IMHO, so I
suggest something similar to the attached version of the top-level
`GNUmakefile.in'. What do you think?
Oops, this was the original file, now comes the new
Oops, this was the original file, now comes the new one.
And here is a revised version which shortens even more overlong lines.
Werner
# -*-Makefile-*-
depth = .
SUBDIRS = \
python scripts \
flower lily \
mf ly \
tex ps scm \
po make \
elisp vim \
input \
stepmake
Consider this example file `foo.ly':
\version 2.15.41
\paper {
page-breaking = #ly:one-line-breaking
}
\header {
copyright = ##f
footer = ##f
tagline = ##f
}
\relative c' {
\repeat unfold 200 { d16 d d d e e e e f f f f g g g g }
}
If called with
lilypond
35 matches
Mail list logo
