On Mon, Sep 10, 2012 at 04:12:54PM +0100, Phil Holmes wrote:
- Original Message - From: John Mandereau
john.mander...@gmail.com
To: Phil Holmes em...@philholmes.net
Il giorno lun, 10/09/2012 alle 15.08 +0100, Phil Holmes ha scritto:
On
On Mon, Sep 10, 2012 at 11:54:05PM +0100, Phil Holmes wrote:
I guess the best bet is to kick GUB off from a clean state:
rm -rf uploads
rm -rf target
You don't need to kill all of target. It's enough to kill any
file or subdirectory containing lilypond inside of target.
This can be done
Janek and I had a brief chat on Tuesday night on the irc channel.
Yesterday, we had a voice chat with google hangout about various
recent happenings on -devel. I think that both options can be
very helpful for understanding each other better. Is anybody else
interested in chatting, with either
Now that 2.16 is out, somebody should remove the lion is not
supported warning from the download page. It's a two-line patch
that can be pushed directly to master.
sending this to -devel instead of bug- because we really don't
need the normal bug infrastructure for this.
- Graham
On Fri, Sep 07, 2012 at 11:07:19AM +0200, Jan Nieuwenhuizen wrote:
Can someone please explain me very slowly why we don't simply use
Git as intended?
Have you noticed that git patches are already in e-mail form? You could
post them to lilypond devel! Just comment and review in-line.
On Fri, Sep 07, 2012 at 09:40:32AM +0200, Benkő Pál wrote:
Could you elaborate on why we want this?
I seem to have misunderstood your qouted comment
http://codereview.appspot.com/6477062/#msg5
ah, I'd forgotten that.
I fear these const's can mislead developers not absolutely
up-to-date
On Fri, Sep 07, 2012 at 05:09:06PM +0200, Mats Bengtsson wrote:
Seriously, I don't really see the point of a separate mailing list.
We are already so used to long discussions on lilypond-devel. Also,
I expect a fairly large portion of the current subscribers to
lilypond-devel would join in
On Fri, Sep 07, 2012 at 02:47:49PM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
Because this empirically did not work in the past for us.
Possibly we can identify why and fix it.
Yes, hopefully. I apologize for the tone of my earlier email; I
should have been more polite
On Sat, Sep 08, 2012 at 01:01:15AM +, lemzw...@googlemail.com wrote:
I mean, in this file there's a weird mixture of tabs and spaces
Weird? It's always tabs (which is assumed to be represented visually by
eight spaces on screen) followed by less than eight spaces.
However, some editors
On Thu, Sep 06, 2012 at 10:22:57AM +0200, David Kastrup wrote:
Absolutely. I'll just point out where one person who tried out Lilypond
was innocently transparent in his bewilderment that anyone would call
out fis in the key of D, and quietly denote the unusual F-natural as f.
On Thu, Sep 06, 2012 at 07:20:57PM +, benko@gmail.com wrote:
Description:
remove top-level const's from declarations
Could you elaborate on why we want this? Do the consts fail to
compile with some compiler, or are they only supposed to be
included in the C++ files, or...?
- Graham
On Mon, Sep 03, 2012 at 08:15:27PM +0100, Graham Percival wrote:
For the past 6 days, we've performed an experiment: can we have a
On Thursday, I will create a new mailing list, with the tentative
name lilypond-syntax-explorations. Alternate name suggestions
are welcome.
I'm re-thinking
On Tue, Sep 04, 2012 at 08:33:45AM +, d...@gnu.org wrote:
-snip review-
So, _now_ please take every sentence and every answer in this mail,
rewrite it in the form of a comment and stick it in the file in the
places where people would be looking for it.
Yes.
_This_ is the kind of
On Tue, Sep 04, 2012 at 10:27:59AM +0200, m...@mikesolomon.org wrote:
When I said that it'd be great for people to put /* TO COMMENT
*/, that is exactly the type of stuff I'd love to see in the
code. Feel free to propose a patch with a bunch of /* TO
COMMENT */ - I think if we mark these
On Tue, Sep 04, 2012 at 01:46:28PM +0200, Janek Warchoł wrote:
On Tue, Sep 4, 2012 at 1:24 PM, Graham Percival
gra...@percival-music.ca wrote:
I think that being pickier with the reviews, possibly including
David's nice idea about only replying with updated patches, is
the best direction
On Tue, Sep 04, 2012 at 05:43:58PM +0200, David Kastrup wrote:
Thomas Morley thomasmorle...@googlemail.com writes:
So I'm with Graham:
2012/9/3 Graham Percival gra...@percival-music.ca:
I do not think that musicians have nothing valuable
to say. I *especially* do not agree
On Mon, Sep 03, 2012 at 11:45:50AM +0200, David Kastrup wrote:
m...@mikesolomon.org m...@mikesolomon.org writes:
As a frequent producer of uncommented code that pushes into a code
base with uncommented code, I am more than willing to put comments.
However, I'll say that a lack of comments
On Mon, Sep 03, 2012 at 12:59:55PM +0200, m...@mikesolomon.org wrote:
On 3 sept. 2012, at 12:53, m...@mikesolomon.org wrote:
Hey all,
-snip 129 lines-
Answered my own question - please ignore.
Mike, please quote correctly. We very very rarely need to see an
entire quoted email; especially
On Mon, Sep 03, 2012 at 02:20:43AM -0300, Han-Wen Nienhuys wrote:
To me, a Grand Input Syntax fixing of LilyPond, would amount to
creating a syntax that strictly separates parsing and interpretation.
This implies not only rethinking a lot of syntax, but also it means
letting go of some of the
On Mon, Sep 03, 2012 at 01:24:22AM -0300, Han-Wen Nienhuys wrote:
On Sat, Sep 1, 2012 at 4:39 PM, Graham Percival
gra...@percival-music.ca wrote:
The meta-target is after spending 5 years very publicly
telling people *not* to talk about changing the syntax because
we would do so
On Mon, Sep 03, 2012 at 02:43:51AM -0300, Han-Wen Nienhuys wrote:
On Mon, Sep 3, 2012 at 2:19 AM, David Kastrup d...@gnu.org wrote:
Most of the proposals are a bad idea
without actually having to look at implementability because they
introduce ambiguities that are hard to resolve
Yes.
On Mon, Sep 03, 2012 at 02:39:45PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Why not hold the preliminary discussions on a separate list (to
which parser experts are encouraged *not* to read), then only
bring a proposal to -devel when it's ready
On Mon, Sep 03, 2012 at 04:10:59PM +0200, Jan Nieuwenhuizen wrote:
On the one hand I very much appreciate the ideas and proposals, because
they tell me that people really care about our user interface. This is
what people see of LilyPond and so it is easy to identify LilyPond by
it. On the
On Mon, Sep 03, 2012 at 05:17:53PM +0200, David Kastrup wrote:
With things like
c-\parenthesize-\p
no hard and fast syntax rule will resolve the ambiguity caused by your
let's stick - before things applying to the previous element proposal.
The hard and fast rule is - attaches to a note;
For the past 6 days, we've performed an experiment: can we have a
productive free-form discussion of syntax changes on
lilypond-devel? I think the results are fairly clear: the answer
is no.
Our previous anonymous developer survey showed that mailing list
civility is a major concern for some
On Sat, Sep 01, 2012 at 10:58:31PM +0200, Nicolas Sceaux wrote:
Le 1 sept. 2012 à 18:25, Graham Percival a écrit :
Continuing to brainstorm on the problem of it not being obvious to
which note a particular \command refers to, what if we used:
If a prefix music function is consistently
On Sun, Sep 02, 2012 at 12:58:47AM +0200, Janek Warchoł wrote:
For what it's worth, i'm ok with this discussion (and similar ones)
happening on devel, as long as we won't loose track of concrete
proposals (when they will appear, ofc.).
I think the direction we're moving in is to have
On Fri, Aug 31, 2012 at 11:25:24PM +0100, James wrote:
Just to reiterate, test-patchy is pretty dumb so when entering
manually links to rietveld can you make sure there is no punctuation
near or around the link to the code to download to test.
Yes.
Interested parties could work on
On Fri, Aug 31, 2012 at 11:11:28PM -0300, Han-Wen Nienhuys wrote:
I have become convinced that optional, unnamed arguments are not a
happy design decision, in any language. In Lily it's particularly
problematic, since we don't group function parameters.
I agree; it's a mess. Let's examine
On Sat, Sep 01, 2012 at 01:27:23PM +0200, David Kastrup wrote:
172 ~ 188 is an abomination anyway. It would be reasonably
straightforward to accept a pair here, like #(172 . 188) or
172/188 which is equivalent.
Straightforward from a programming perspective, but as far as
printed music is
On Fri, Aug 31, 2012 at 11:18:54PM +0100, James wrote:
On 31 August 2012 22:35, John Mandereau john.mander...@gmail.com wrote:
I can change Patchy so that it compresses the show-XXX tree in a xz
file, send it to Grenouille via SFTP,
would it be possible to do this over rsync, to allow
On Thu, Aug 30, 2012 at 01:40:29AM +0200, John Mandereau wrote:
If you don't include the touch all manual pages in your commit, GUB
build of tools::texinfo shall fail for every system, whether help2man is
available system-wide or not, as in this case Texinfo build does not
look for binaries in
On Mon, Aug 27, 2012 at 07:01:56PM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
whoops, I hadn't thought about it -- at 19:00 UTC this Tuesday,
I'll be either at Heathrow airport or in the air flying to
Glasgow. Shall we start next week (in Sep)? or maybe if at least
one
On Fri, Aug 31, 2012 at 12:24:39PM +0200, John Mandereau wrote:
Il giorno gio, 30/08/2012 alle 18.15 +0100, James ha scritto:
We have two of config files.
lilypond-patchy-config and .msmtp-patchy (used by patchy staging).
I sent you a sample config file, if the instructions work for you
On Tue, Aug 28, 2012 at 08:17:58AM +0100, Graham Percival wrote:
Let's make a list of tasks we want, then make sure that we're
doing them on sensible computers.
I've moved this list to github:
https://github.com/gperciva/lilypond-extra/blob/master/misc/computing-power.txt
- Graham
On Sat, Sep 01, 2012 at 12:07:07PM -0300, Han-Wen Nienhuys wrote:
This is also the danger of having broad discussions over syntax.
...
on the basis of how intuitive it looks. See also
http://en.wikipedia.org/wiki/Parkinson's_Law_of_Triviality
Yes, that was the whole reason why I wanted to
On Sat, Sep 01, 2012 at 04:54:47PM +0100, Phil Holmes wrote:
Unfortunately it breaks make test. Apologies - I was sure I'd
tested it with make doc, but must have omitted it with this one. Is
the best option to revert the commit in staging, or is there a
better way?
The way is to delete
Continuing to brainstorm on the problem of it not being obvious to
which note a particular \command refers to, what if we used:
\postfix: c2 d\p is unchanged
/prefix: for music functions like c2 /parenthesize d
.neutral: for commands which aren't attached to notes, such
as .clef or
On Sat, Sep 01, 2012 at 05:47:39PM +0100, Phil Holmes wrote:
This fixes the problem:
progress (str(imp.load_source (book_custom_package%s % nr, i)))
and makes sense to me: imp.load_source retutrns a module; str()
converts that to a string which progress can handle. Print could
On Sat, Sep 01, 2012 at 09:18:17PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Continuing to brainstorm on the problem of it not being obvious to
which note a particular \command refers to, what if we used:
\postfix: c2 d\p is unchanged
/prefix
On Fri, Aug 31, 2012 at 02:04:12PM +0200, John Mandereau wrote:
Il giorno gio, 30/08/2012 alle 12.52 +0100, Graham Percival ha scritto:
Failing that, any other developer could set
patch-new to trigger a new test if the discussion suggests that
the previous test results are not correct
On Fri, Aug 31, 2012 at 02:54:11PM +0200, John Mandereau wrote:
Il giorno ven, 31/08/2012 alle 13.21 +0100, Graham Percival ha scritto:
People like James can build new test results quite quickly,
have them automatically uploaded to Grenouille, and Grenouille
can then server them
On Fri, Aug 31, 2012 at 01:20:14PM -0300, Han-Wen Nienhuys wrote:
On Thu, Aug 30, 2012 at 9:02 AM, Graham Percival
gra...@percival-music.ca wrote:
Automated readers - I am not very convinced about this. Reading .ly
correctly implies having a complete scheme interpreter at your
disposal
On Thu, Aug 30, 2012 at 10:17:26AM +0200, John Mandereau wrote:
Il giorno gio, 30/08/2012 alle 08.57 +0100, Trevor Daniels ha scritto:
I don't think the patch for this issue should have been tested.
It has been marked 'patch-needs-work' since 29 May.
It should have been marked
On Thu, Aug 30, 2012 at 11:38:51AM +0200, John Mandereau wrote:
every new comment on those issues with old patches will trigger a test.
That's definitely overkill! What if I post a comment saying yes,
this patch definitely looks bad?
IMHO all issues that have not changed since 2 months and
On Thu, Aug 30, 2012 at 08:50:35AM -0300, Han-Wen Nienhuys wrote:
It would be helpful to have a comprehensive overview of what would be changed.
That's why I wanted to make sure that proposals are in good
shape before discussing them on the main list. But there seems
to be general consensus
On Thu, Aug 30, 2012 at 05:35:51PM +0100, Phil Holmes wrote:
- Original Message - From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Wednesday, August 29, 2012 11:04 PM
Subject: Re: 2.17.1
So since Phil took a bit of time after forking the unstable release
branch to
On Wed, Aug 29, 2012 at 10:16:18AM +0100, Phil Holmes wrote:
For reference, I added the new group and added my gub user to that
group, and the script still barfed. It can't change the properties
of the files unless it has the permissions to do that, which it
doesn't.
Hmm, are you sure you
On Wed, Aug 29, 2012 at 11:58:12AM +0200, David Kastrup wrote:
Phil Holmes m...@philholmes.net writes:
Well, actually, I omitted that part of the instruction, since I could
see my user in group lilypond...
Your running processes don't change membership. Use
id
to see what the actual
As per GOP 2-4 - C++ and scheme indentation, we now have a
fixscm.sh in the source tree. Running this was postponed pending
Mike's monster skyline patch and possibly some sort of guile 2.0
thing.
What's the status of the guile 2.0 patch? In particular, is it
safe to run fixscm.sh now, or should
After further investiation of astyle at the Waltrop meeting, I've
tweaked GOP2-4 - C++ and scheme indentation.
Instead of using astyle 2.02 strictly, we will also allow astyle
2.02.1. The later version changes:
type* bar;
into
type *bar;
which matches the way that we format pointers which do
At the Waltrop meeting, Janek proposed a number of interesting but
potentially disruptive changes to the lilypond syntax. On a
personal note, I really like most of them, but it will take a good
chunk of work before they're ready to discuss on the main
development list.
Further complicating
On Wed, Aug 29, 2012 at 01:09:20PM +0100, Phil Holmes wrote:
2.17.1. The official regtest comparison is against 2.15.38, because
of the vagaries of my initial GUB build.
ouch, but not critical in this case. Mike's monster patch changes
pretty much everything, so a regtest comparison isn't
On Tue, Aug 28, 2012 at 07:11:10PM +0200, Federico Bruni wrote:
I can launch 'make website' now, but the css stylesheet is not loaded.
Because there's no css/ directory in out-website/
Yes, because
out-website/index.html
is not the real website. Intead, look at
On Tue, Aug 28, 2012 at 10:44:17AM +0100, James wrote:
On 28 August 2012 08:17, Graham Percival gra...@percival-music.ca wrote:
- Patchy staging-merge: powerful computer, no fixed internet
connection. Every 6 hours?
As you know you have mine that already does test-patchy (manually
On Wed, Aug 29, 2012 at 02:09:43PM +0100, James wrote:
Just an off-the-cuff suggestion. If we had a 'patch-new-doc' and a
'patch-new' label would that be useful and tell patchy if it sees the
former to build doc as well?
I suppose so, although people uploading with git-cl would need to
specify
On Wed, Aug 29, 2012 at 03:15:08PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Thoughts? opinions? alternatives that I haven't considered?
These discussions are going to produce a *lot* of emails.
And if they come to conclusions, they are going
On Wed, Aug 29, 2012 at 03:17:40PM +0100, Phil Holmes wrote:
git --git-dir downloads/lilypond/git push
ssh+git://gperci...@git.sv.gnu.org/srv/git/lilypond.git/
refs/tags/release/2.17.1-1:refs/tags/release/2.17.1-1
Permission denied (publickey).
I'm assuming that this is because GUB is
On Wed, Aug 29, 2012 at 03:52:08PM +0200, Janek Warchoł wrote:
i know that i'm late - forgot about it, sorry :( - but nevertheless it
may still be possible:
what about having a separate release containing only Mike's patch?
I think that's too much hassle right now with GUB changing so much
and
Let's make a list of tasks we want, then make sure that we're
doing them on sensible computers.
- Patchy staging-merge: powerful computer, no fixed internet
connection. Every 6 hours?
- Patchy test-patches: powerful computer, fixed internet
connection, lots of free space to host the regtest
On Tue, Aug 28, 2012 at 03:43:40PM +0100, Phil Holmes wrote:
gub@gub-virtualbox:~/gub$ make lilypond-upload
LILYPOND_BRANCH=release/unstable
LILYPOND_REPO_URL=git://git.sv.gnu.org/lilypond.git
chgrp -R lilypond uploads/lilypond*
chgrp: invalid group: `lilypond'
right, oops. You need to
On Tue, Aug 28, 2012 at 01:24:09PM +0100, James wrote:
I have been trying to see about cutting a new LilyDev (2.7) on 12.04 -
the limitation being whatever remastersys backup is supported on -
when I last looked it was not on 12:10.
I should say so, since 12:10 is still two months in the
On Tue, Aug 28, 2012 at 01:21:53PM +0100, Phil Holmes wrote:
FWIW, it's been running from scratch for about 4 hours on my fast
quad core, so you do need a big, fast machine to do this regularly.
The first time you run GUB (or whenever the GUB git repository has
changed significantly), it takes
On Tue, Aug 28, 2012 at 10:45:00PM +0200, Marc Hohl wrote:
Am 28.08.2012 20:52, schrieb David Kastrup:
Marc Hohl m...@hohlart.de writes:
After searching a bit more,
git grep blank-page-force
shows several hits, but in 2.17.x, this should read blank-page-penalty,
so I assume when master
Here's a summary of the situation:
- git repository is here:
https://github.com/gperciva/gub
anybody who wants push ability to this repository will get it.
- there is now an experimental branch. Commits should probably
be pushed there first, then when somebody has completed a GUB
run, it
On Mon, Aug 27, 2012 at 11:20:55AM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
The idea is that we'd pick some time (say, 19:00 UTC on Tuesdays
-- but that's a completely random time),
I'm planning to be there and will let you know if I can't make it.
whoops, I hadn't thought
On Mon, Aug 27, 2012 at 10:21:53AM +, benko@gmail.com wrote:
lily/include/skyline.hh:58: listBuilding *const result);
I'd like to see the const removed (top-level const on function parameter
types are ignored), but that may be the target of another patch.
Good idea! However, that
LGTM
- Graham
On Mon, Aug 27, 2012 at 04:49:11PM +0100, Phil Holmes wrote:
Anyone object if I push a patch that adds -q to the call to bib2texi
direct to staging? I've tested it and make doc runs fine - it gets
rid of some clutter in the output of make doc.
--
Phil Holmes
On Thu, Aug 23, 2012 at 09:25:55PM -0300, Han-Wen Nienhuys wrote:
Change font license from GPL to dual licensed OFL / GPL (see
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=OFL_web)
We have agreement of this from the people who were here:
Author: Janek Warchol
On Mon, Aug 27, 2012 at 10:07:40PM +0100, Phil Holmes wrote:
Is it compulsory to have a pony tail?
Yes and no. All senior hackers on GNU software must have either a
ponytail that's more than 5cm long, or a beard which is more than
2cm long. That's in the GNU policy document, section 18.21. It
On Sun, Aug 26, 2012 at 11:14:06AM +0100, Phil Holmes wrote:
- Original Message - From: Martin Tarenskeen
m.tarensk...@zonnet.nl
To: lilypond-devel mailinglist lilypond-devel@gnu.org
Also I was hoping to find info about the required/recommended
Python version here when I was
Let's give this another try.
Anybody interested in setting up a regular weekly chat? Either
IRC or skype or some other chat protocol.
The idea is that we'd pick some time (say, 19:00 UTC on Tuesdays
-- but that's a completely random time), then whoever wanted to
hang out could come by. Or, if
If people want to have the 2.16.0 release announcement spread in
more places, they might want to look at:
http://code.google.com/p/lilypond/issues/detail?id=1719
and make a list here.
Please don't send announcements to other locations quite yet; I'd
like to have 3 days for last-minute fixes.
We have an indentation script for scheme in staging now. We're
not actually running the script on the source tree until 1 or 2
big patches are merged: Mike's skyline stuff, and possibly the
guile2.0 stuff. This will hopefully get the fixes done in the
near future without introducing lots of
Presumably the script was tested with bash, but was being run with
sh or dash? or something like that?
- Graham
git
--git-dir=/main/src/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/.git
show HEAD | head -100 out/RELEASE-COMMIT
make[5]: Leaving directory
On Tue, Aug 21, 2012 at 12:08:16PM +, d...@gnu.org wrote:
Reviewers: Graham Percival,
Message:
On 2012/08/21 11:57:45, Graham Percival wrote:
2) the patch title says CG:, but this doesn't touch the CG.
But the CG touches the patch. Concretely, it states:
All engravers should have
http://lilypond.org/~graham/gop/gop_5.html
** Proposal summary
C++ will remain as-is, using astyle 2.02 (not astyle2.02.1) with
scripts/auxiliar/fixcc.py
Scheme will be indented with emacs --batch mode.
There should be no tabs in any C++ or scheme files.
** Motivation
It would be nice if we
On Mon, Aug 20, 2012 at 09:58:19PM +0200, Frédéric Bron wrote:
My question remains: should we sort alphabetically the list under
Programs that can export LilyPond code in the following webpage? It
looks like a mess.
Yes, they should be sorted alphabetically. I'll note that it's
almost done;
On Sun, Aug 19, 2012 at 10:27:37AM +0100, Phil Holmes wrote:
- Original Message - From: Graham Percival
gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
OTOH, I don't think that we should delete bits of code unless we
know why they were there in the first place. There's
On Sun, Aug 19, 2012 at 03:02:29PM +0200, David Kastrup wrote:
The schedule would focus on stable release work and criteria on Friday,
with the goal of getting most participants hands-on experience or at
least exposure to GUB work. Coursework goal is the release of 2.16, and
getting the
On Sun, Aug 19, 2012 at 04:50:54PM +, d...@gnu.org wrote:
On 2012/08/19 16:07:28, Ian Hulin (gmail) wrote:
Where is it going to end up after a make install run and where will it
be
delivered when the binaries are built and run?
Huh?!?!?!? It has nothing to do whatsoever with make
On Sat, Aug 18, 2012 at 03:31:06PM +0100, Phil Holmes wrote:
My understanding of this problem was that it appeared that Popen (at
some point in the past) would not work with our delivered Python (as
created by Gub). I also believed that the fix to 1933 also probably
removed this limitation.
On Sat, Aug 18, 2012 at 03:40:19PM +0100, Phil Holmes wrote:
- Original Message - From: gra...@percival-music.ca
To: philehol...@googlemail.com; d...@gnu.org
Cc: re...@codereview-hr.appspotmail.com; lilypond-devel@gnu.org
I haven't looked at the new logic in detail, but exactly what
On Sat, Aug 18, 2012 at 05:23:17PM +0100, Phil Holmes wrote:
- Original Message - From: Phil Holmes
m...@philholmes.net
To: Graham Percival gra...@percival-music.ca
Cc: philehol...@googlemail.com; john.mander...@gmail.com;
So we have fixed it. You want I should find out when
On Fri, Aug 17, 2012 at 01:38:08PM -0400, m...@mikesolomon.org wrote:
Has to do with my loop question from before - I am sure now that there is an
infinite loop but I'm not sure in what file it's being triggered.
John's way is probably better, but I'd do something like
for f in
I'm sorry, but I am quite confused.
On Fri, Aug 17, 2012 at 10:02:19AM +0200, Jan Nieuwenhuizen wrote:
Anything that can be automated, that otherwise would require manual
intervention or attention, should be automated.
I definitely agree with this.
I do not care if the tool is 50MB to
Two developers didn't seem fond of this idea, but other people
liked it, so it's not changed significantly.
http://lilypond.org/~graham/gop/gop_5.html
** Proposal summary
C++ will remain as-is, using astyle 2.02 (not astyle2.02.1) with
scripts/auxiliar/fixcc.py
Scheme will be indented with a
On Mon, Aug 13, 2012 at 09:38:15AM +0200, David Kastrup wrote:
3. Where there are significant changes to component .scm files for
guile V2, these will also be converted into a shim similar to lily.scm
and will have file-guile-1.scm and file-guile-2.scm files
produced.
Personally, I am
On Mon, Aug 13, 2012 at 11:26:21AM +0100, James wrote:
Just an FYI for those that understand this stuff:
/home/james/lilypond-git/build/python/out/book_snippets.py:744:
DeprecationWarning: os.popen3 is deprecated. Use the subprocess
module.
(stdin, stdout, stderr) = os.popen3 (cmd)
I have
On Mon, Aug 13, 2012 at 08:16:48PM +0200, David Kastrup wrote:
Werner LEMBERG w...@gnu.org writes:
Hmm, `wild changes' is a mild exaggeration, isn't it? It makes
50 Cyrillic characters appear in the PDFs which were simply missing
previously. It's a one-line change in `macros.itexi'
and
On Mon, Aug 13, 2012 at 09:16:24PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Yes. Pushing directly to staging is basically a gamble:
IF YOU WIN: you avoid the delay and hassle of git-cl, reviews, a
patch countdown, etc.
IF YOU LOSE: somebody doesn't
On Sun, Aug 12, 2012 at 02:48:05PM +0200, David Kastrup wrote:
Since it would be awkward (but not impossible) if 2.17.0 would be
released before 2.16.0, any patches now entering in master will not have
seen exposure in a development release before 2.16.0 is tentatively
released.
Actually,
On Sun, Aug 12, 2012 at 09:28:45PM +0200, John Mandereau wrote:
Le dimanche 12 août 2012 à 14:16 +0100, Graham Percival a écrit :
Changing this would require a fair amount of hacking on the
website build process and documentation; not impossible, but not a
fun task either.
Do we want
On Fri, Aug 10, 2012 at 08:32:04AM +0100, Trevor Daniels wrote:
Graham Percival wrote Thursday, August 09, 2012 10:01 AM
Scheme will be indented with a yet-to-be written
scripts/auxiliar/fix-scheme.sh, which does the same thing as
emacs.
This will certainly be useful to ensure uniform
On Thu, Aug 09, 2012 at 07:25:51AM +0100, James wrote:
Trying issue 2727
Problem with urls:
[]
There's no patch in
http://code.google.com/p/lilypond/issues/detail?id=2727
I don't know how that happened, but I can't find any patch in
rietveld that looks promising either. I've removed the
http://lilypond.org/~graham/gop/gop_5.html
** Proposal summary
Speaking academically, scheme code style is a “solved problem”.
Let’s pick one of the existing solutions, and let a computer deal
with this. Humans should not waste their time, energy, and
creativity manually adding tabs or spaces to
Not much discussion after the mid-way point. I'm not certain if
this means that everybody agrees, or they just think I'm
completely wrong and it's not worth even discussing it (as
happened with the first proposal for stable release handling).
http://lilypond.org/~graham/gop/gop_4.html
**
On Thu, Aug 09, 2012 at 12:09:51PM +0200, David Kastrup wrote:
m...@mikesolomon.org m...@mikesolomon.org writes:
I'd sent out a note of agreement before but I'll send out another one
just to signal that I'm 100% for incrementally freezing parts of
LilyPond's syntax. Specifically, I'm
On Thu, Aug 09, 2012 at 12:21:06PM +0200, Jan Nieuwenhuizen wrote:
Graham Percival writes:
New contributors sometimes struggle to follow our indentation and
code style
Yes, that's bad. Do we explain that we're a GNU project and as
such use GNU coding style? Together with a pointer
On Thu, Aug 09, 2012 at 12:46:41PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
On Thu, Aug 09, 2012 at 12:09:51PM +0200, David Kastrup wrote:
\tempo syntax is quite an abomination. It is one of those things that
regularly cause parser changes to trip up
201 - 300 of 5586 matches
Mail list logo
