date:20110926

On Mon, Sep 26, 2011 at 01:41:26PM +0200, Reinhold Kainhofer wrote:
> Am Monday, 26. September 2011, 03:15:54 schrieb Graham Percival:
> > Does anybody have a passing familiarity with json?  I'm having
> > trouble getting started with rietveld json api.
> 
> You simply need to add the /api/ to the URL:
> 
> wget http://codereview.appspot.com/api/224052
>
> The correct code is:
> request = urllib2.Request(url + data)

Excellent, thanks!  Now we have all the bits and pieces necessary
to put James and Colin mostly out of a job.  :)

James, Colin: unfortunately I'm almost out of time for this week,
so it'll have to wait until next week.  I'll start with James'
patch compiling and regtest generation.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: NR Context Layout Order rewrite (5.1.7) - tracker 1812 (issue 4839061)

2011-09-26 Thread percival . music . ca



http://codereview.appspot.com/4839061/diff/7002/Documentation/notation/changing-defaults.itely
File Documentation/notation/changing-defaults.itely (right):

http://codereview.appspot.com/4839061/diff/7002/Documentation/notation/changing-defaults.itely#newcode961
Documentation/notation/changing-defaults.itely:961: @example
could this be a @lilypond instead?

http://codereview.appspot.com/4839061/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Fix 1477: Add (ly:expect-warning msg args) to suppress expected warnings (issue 5037046)

2011-09-26 Thread percival . music . ca


Looks mostly good.  I would have preferred to have the code changes in a
separate patch from the regtest .ly editing, but that's not a major
issue.


http://codereview.appspot.com/5037046/diff/15001/input/regression/stem-tremolo.ly
File input/regression/stem-tremolo.ly (right):

http://codereview.appspot.com/5037046/diff/15001/input/regression/stem-tremolo.ly#newcode4
input/regression/stem-tremolo.ly:4: #(ly:expect-warning (_ "tremolo
duration is too long"))
Why do we expect those warnings here?  It sounds like somebody just
screwed up writing the regtest, so we should fix that instead of
ignoring the warnings.

http://codereview.appspot.com/5037046/diff/15001/input/regression/tie-arpeggio.ly
File input/regression/tie-arpeggio.ly (right):

http://codereview.appspot.com/5037046/diff/15001/input/regression/tie-arpeggio.ly#newcode11
input/regression/tie-arpeggio.ly:11: have to follow the lef-tied note
directly. When @code{tieWaitForNote}
left-tied

(not your patch, but it would be nice to fix it anyway)

http://codereview.appspot.com/5037046/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Creates convert-ly rules for flag syntax changes (issue 5050046)

2011-09-26 Thread percival . music . ca


LGTM

http://codereview.appspot.com/5050046/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCH: countdown to 20110928

2011-09-26 Thread Colin Campbell


For 22:00 MDT Wednesday Sept 28

Issue 307 : 
collision slur with tuplet bracket - R 4813048 



Issue 1321 : 
Enhancement: add partcombineUp and partcombineDown functions - R 4514042 



Issue 1477 : 
suppress output for expected warnings - R 5037046 



Issue 1812 : NR 
Context Layout Order rewrite - R 4839061 



Issue 1871 : 
Several fixes for annotate-spacing - R 4950071 



Issue 1921 : 
Creates convert-ly rules for flag syntax changes - R 5050046 



Issue 1855 : 
Prevents nested tuplets from colliding - R 4808082 



Issue 1846 : 
Improves horizontal spacing of axis groups that SpanBar grobs traverse - 
R 4917046 


Issue 1844 : 
Changes variable names in include/beam-scoring-problem.hh and 
beam-quanting.cc - R 4961041 


Issue 1929 : 
stem-tremolo-position.ly broken - R 5133042 




Cheers,
Colin

--
I've learned that you shouldn't go through life with a catcher's mitt on both 
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 09:31:08PM -0600, Colin Campbell wrote:
> >As an aside, I've moved the stored credentials (if somebody is
> >compfortable with plaintext in their home directory) to
> >~/.lilypond-project-hosting-login
> 
> An additional precaution, besides hiding the file with the dot
> prefix, would be chmod 0700 .lilypond-project-hosting-login to
> restrict access to the owner only.

chmod 0600 , but yes.

I've been influenced by ESR's design notes on fetchmail:
http://www.fetchmail.info/esrs-design-notes.html
in particular the "why i will never add password encryption in
.fetchmailrc":
  The reason there's no facility to store passwords encrypted in
  the .fetchmailrc file is because this doesn't actually add
  protection.

  Anyone who's acquired the 0600 permissions needed to read your
  .fetchmailrc file will be able to run fetchmail as you anyway --
  and if it's your password they're after, they'd be able to rip
  the necessary decoder out of the fetchmail code itself to get it.

  All .fetchmailrc encryption would do is give a false sense of
  security to people who don't think very hard.

That said, I recognize that it's much easier to snarf a password
from a dotfile than it is to sneak a custom-hacked fetchmail onto
somebody's computer.  I actually keep all my personal dot-files
(including fetchmail) on a separate sd card which I mount+unmount,
precisely to lower the chance of anything bad happening if
somebody else gets access to my university desktop computer.
So I'd be the last person to throw stones at others for being too
paranoid!  :)

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

2011-09-26 Thread Colin Campbell


On 11-09-26 08:26 PM, Graham Percival wrote:

On Mon, Sep 26, 2011 at 06:38:02AM +, Keith OHara wrote:

Confirming that it worked for me.
It was necessary to install stuff from
http://code.google.com/p/gdata-python-client/

I believe that I have removed that dependency.


That will cause some of us to invent yet another throwaway username
and password that we don't worry about storing in plain test.
Not a big problem, but you might know an alternative way for the
script to authenticate?

Script now supports entering your username+password manually.
Somebody could do something more sophisticated with storing
authentications like upload.py does, but that's beyond my
interest+time at the moment.  I may return to this in a few weeks.

As an aside, I've moved the stored credentials (if somebody is
compfortable with plaintext in their home directory) to
~/.lilypond-project-hosting-login

Cheers,
- Graham




An additional precaution, besides hiding the file with the dot prefix, 
would be chmod 0700 .lilypond-project-hosting-login to restrict access 
to the owner only.


Cheers,
Colin

--
I've learned that you shouldn't go through life with a catcher's mitt on both 
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 04:02:12PM -0300, Han-Wen Nienhuys wrote:
> On Sun, Sep 25, 2011 at 11:36 PM, Graham Percival
>  wrote:
 > Once this script is fully tested and working, it will relieve a
> > lot of our current frustrations.  Please switch to it -- even if
> > there's a problem with the new parts of the script, the original
> > behavior of the rietveld upload is completely unchanged, so you
> > lose nothing!
> 
> Have you tried sending your commits back to Evan ?  IIRC,  he is very
> responsive.

I haven't tried contacting him yet.  I'm not certain if sending
these upstream is appropriate;
- I'm importing a huge chunk of gdata-python in an ugly
  duplication of code (because I don't want to ask casual lilypond
  contributors to install gdata)
- the code.google.com stuff is only relevant to projects using
  that, whereas git-cl is a more general tool.  (that said,
  git-cl could have a "post-upload hook" which we could use)
- we're still shaking out major bugs and annoyances with the new
  git-cl, so I think it's premature in any case.  :)

Once things settle down, I could point him at my github account in
case he sees anything worth taking?

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 11:25:49PM +0200, Julien Rioux wrote:
> True, but still worth noting since 1) the script could be made to
> exit gracefully in such a case, and

Yes, absolutely.  It now tries to upload again but without
adding/changing labels (which is all that non-members are allowed
to do; no option to change that in google code, grr), and asks you
to email -devel.

> 2) it seems that the upload to
> Rietveld got interrupted and it is maybe linked to this error on the
> googlepage side of things.

That's a different problem:
http://code.google.com/p/lilypond/issues/detail?id=1491
unfortunately I'm not aware of a good solution for this.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 06:38:02AM +, Keith OHara wrote:
> Confirming that it worked for me.
> It was necessary to install stuff from
> http://code.google.com/p/gdata-python-client/

I believe that I have removed that dependency.

> That will cause some of us to invent yet another throwaway username
> and password that we don't worry about storing in plain test.
> Not a big problem, but you might know an alternative way for the
> script to authenticate?

Script now supports entering your username+password manually.
Somebody could do something more sophisticated with storing
authentications like upload.py does, but that's beyond my
interest+time at the moment.  I may return to this in a few weeks.

As an aside, I've moved the stored credentials (if somebody is
compfortable with plaintext in their home directory) to
~/.lilypond-project-hosting-login

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Big web page

On Mon, Sep 26, 2011 at 05:05:48PM +0100, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
> 
> >Note that if web-big-html lacks pictures, then presumably other
> >manuals (like notation-big-html and contributor-big-html) will
> >also lack pictures.
> 
> No.  This is because web-split is created during make website,
> whereas manual-split is created during make doc.

Not quite correct.
** created during make website.
lilypond.org/*.html

** created during make doc
http://lilypond.org/doc/v2.14/Documentation/web/index

Of particular interest is:
http://lilypond.org/doc/v2.14/Documentation/web/download
http://lilypond.org/doc/v2.14/Documentation/web-big-page#download
apparently some images work just fine in web-big-page!  These were
added using @sourceimage instead of @imageFloat or anything like
that.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: FiguredBass: Rewrite of the engraver to fix vertical position (issue 224052)

2011-09-26 Thread reinhold . kainhofer


On 2011/09/24 09:51:54, Graham Percival wrote:

any chance of rebasing this patch?


New patchset uploaded, but that's not completely ready for consumption.

I'm still fighting with the issue that a child grob of the vertical
alignment spanner can only be on the same vertical position as its
predecessor, but not above (we have a check for max(0, dy) in there). If
I make that max(0,...) check optional, the bass figures are correctly
shifted up, but unfotunately I loose all padding :(

http://codereview.appspot.com/224052/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Does lilypond 2.15.x support guile 2.0 yet?


On 09/26/2011 07:18 PM, Julien Rioux wrote:

On 26/09/2011 2:18 PM, Dave Plater wrote:

On 09/26/2011 10:31 AM, Graham Percival wrote:

On Mon, Sep 26, 2011 at 09:54:18AM +0200, Dave Plater wrote:

Lilypond won't even be able to be installed via tarball on openSUSE
12.1 without the user removing guile 2.0 completely and installing
guile 1.8 via tarball, as a result these users of lilypond and
rosegarden will drop openSUSE.


I believe that users can run GUB no problem. We ship our own
guile-1.8 precisely to avoid this kind of trouble.

Cheers,
- Graham


Well so far I have help from the openSUSE guile maintainer in creating
dual guile versions so it looks like all will be well after all.

Dave


How do you configure lilypond so that it is built against your guile1 instead 
of the system-wide guile? I tried to do this recently but
could not figure it out. I ended up removing guile completely and reinstalling, 
which took much longer.

I haven't got that far yet but in my case I'll most probably either rename the problem guile libs and executables or link them. The 
libraries should have their natural names as they should be versioned and the devel packages will be mutually exclusive due to name 
clashes. /usr/bin/guile-snarf will have to be renamed but the "--program-suffix=1" switch appends a 1 to it during build, guile-tools has 
been replaced in guile 2.0.2 so it can simply be renamed back to guile-tools during install with no ill effect, guile-config is depreciated 
and no longer used so it can be deleted.
Basically as long as the other packages on the system don't use guile 2.0 executables and have been built against the libraries and the 
libraries install from their own package guile 1.8 can exist happily alongside guile 2.0. I'll send a link to my spec files in a couple of 
days but the rule is package the libraries in their own versioned package to accommodate the likes of gnucash and make everything else 
mutually exclusive ie. libguile1 can exist with libguile2 and guile 1.8 uninstalls guile 2.0. The $datadir files are versioned already as 
well. There's the pkgconfig file that can be easily manipulated if need be but that is part of the devel package anyway.

Hope this helps, I'll read it again when I wake up in the morning and correct 
anything stupid.

Dave

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: MIDI output: min/max MIDI volume levels, dynamics of polyphonic passages within a single Voice

2011-09-26 Thread Janek Warchoł

Hi Heikki,

2011/9/25 Janek Warchoł :
> I will add a tracker issue for this bug tomorrow.

Added as issue 1938 http://code.google.com/p/lilypond/issues/detail?id=1938

> I'll also test your patch against current master.

I've checked that your patch can be applied to current master and that it works!
I've put it for review to our code-reviewing website:
http://codereview.appspot.com/5134047/ - we'll see what the other
developers will say.

Thanks!
Janek

PS make sure that you have subscribed to lilypond-devel@gnu.org mailing list

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

MIDI volume can exceed maximum value (fix 1938) (issue 5134047)

2011-09-26 Thread janek . lilypond


Reviewers: ,

Message:
http://code.google.com/p/lilypond/issues/detail?id=1938

fix by Heikki Tauriainen

Description:
MIDI volume can exceed maximum value (fix 1938)

make Dynamic performer respect midiMinimumVolume
and midiMaximumVolume, also with (de)crescendi
which aren't terminated by absolute dynamic mark.

Please review this at http://codereview.appspot.com/5134047/

Affected files:
  M lily/audio-item.cc
  M lily/dynamic-performer.cc
  M lily/include/audio-item.hh


Index: lily/audio-item.cc
diff --git a/lily/audio-item.cc b/lily/audio-item.cc
index  
1cbf7765b70f338ff82a5b9ed004ddf47c8eebbd..e14fa2f7af1972351093b84afabc1912f505b825  
100644

--- a/lily/audio-item.cc
+++ b/lily/audio-item.cc
@@ -79,9 +79,11 @@ Audio_dynamic::Audio_dynamic ()
 {
 }

-Audio_span_dynamic::Audio_span_dynamic ()
+Audio_span_dynamic::Audio_span_dynamic (Real min_volume, Real max_volume)
 {
   grow_dir_ = CENTER;
+  min_volume_ = min_volume;
+  max_volume_ = max_volume;
 }

 void
@@ -135,7 +137,7 @@ Audio_span_dynamic::render ()

   Real start_v = dynamics_[0]->volume_;
   if (dynamics_.back ()->volume_ < 0)
-dynamics_.back ()->volume_ = max (min (start_v + grow_dir_ * 0.25,  
1.0), 0.1);
+dynamics_.back ()->volume_ = max (min (start_v + grow_dir_ * 0.25,  
max_volume_), min_volume_);


   delta_v = dynamics_.back ()->volume_ - dynamics_[0]->volume_;

Index: lily/dynamic-performer.cc
diff --git a/lily/dynamic-performer.cc b/lily/dynamic-performer.cc
index  
3977a77c30a2166efe89f91e6cc92c8759cc5624..be6cc166de354e1dead268333ebc9a133882831a  
100644

--- a/lily/dynamic-performer.cc
+++ b/lily/dynamic-performer.cc
@@ -110,7 +110,7 @@ Dynamic_performer::process_music ()

   if (span_events_[START])
 {
-  span_dynamic_ = new Audio_span_dynamic ();
+  span_dynamic_ = new Audio_span_dynamic (equalize_volume (0.1),  
equalize_volume (1.0));
   announce_element (Audio_element_info (span_dynamic_,  
span_events_[START]));


   span_dynamic_->grow_dir_ = grow_dir_[START];
Index: lily/include/audio-item.hh
diff --git a/lily/include/audio-item.hh b/lily/include/audio-item.hh
index  
dc4bb6efbd3c1073426567205c4401cb9d540718..ee0e2e9447beb4a7dcf58367f80983342f614a7d  
100644

--- a/lily/include/audio-item.hh
+++ b/lily/include/audio-item.hh
@@ -54,10 +54,12 @@ class Audio_span_dynamic : public Audio_element
 public:
   Direction grow_dir_;
   vector dynamics_;
+  Real min_volume_;
+  Real max_volume_;

   virtual void render ();
   void add_absolute (Audio_dynamic *);
-  Audio_span_dynamic ();
+  Audio_span_dynamic (Real min_volume, Real max_volume);
 };

 class Audio_key : public Audio_item



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

2011-09-26 Thread Julien Rioux


On 26/09/2011 11:13 PM, Janek Warchoł wrote:

2011/9/26 Julien Rioux:

I tried this. Rietveld issue was created, but google page issue gave me an
error. Attaching


Do i guess correctly that it's because your e-mail address is not
authorized in our tracker?  Graham?

cheers,
Janek



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel


True, but still worth noting since 1) the script could be made to exit 
gracefully in such a case, and 2) it seems that the upload to Rietveld 
got interrupted and it is maybe linked to this error on the googlepage 
side of things.


--
Julien


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

2011-09-26 Thread Janek Warchoł

2011/9/26 Julien Rioux :
> I tried this. Rietveld issue was created, but google page issue gave me an
> error. Attaching

Do i guess correctly that it's because your e-mail address is not
authorized in our tracker?  Graham?

cheers,
Janek
Traceback (most recent call last):
  File "../git-cl/git-cl", line 875, in 
sys.exit(main(sys.argv))
  File "../git-cl/git-cl", line 869, in main
return func(argv[2:])
  File "../git-cl/git-cl", line 599, in CmdUpload
projecthosting_upload.upload(issue, patchset, subject, desc)
  File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 108, in upload
status = patchy.upload(issue, patchset, subject, description)
  File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 99, in upload
self.update_issue(issue_id, description)
  File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 71, in 
update_issue
labels = ["Patch-new"])
  File "/home/jrioux/git/git-cl/gdata/projecthosting/client.py", line 133, in 
update_issue
**kwargs)
  File "/home/jrioux/git/git-cl/gdata/client.py", line 685, in post
desired_class=desired_class, **kwargs)
  File "/home/jrioux/git/git-cl/gdata/client.py", line 320, in request
RequestError)
gdata.client.RequestError: Server responded with: 403, No permission to edit 
issue

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

2011-09-26 Thread janek . lilypond


LGTM.
Thanks!


http://codereview.appspot.com/5096050/diff/20001/python/musicexp.py
File python/musicexp.py (right):

http://codereview.appspot.com/5096050/diff/20001/python/musicexp.py#newcode1510
python/musicexp.py:1510: # Print out the style if we have ome, but the
'() should only be
The typo that was fixed in the previous version of the patch is back :P

http://codereview.appspot.com/5096050/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: musicxml2ly: title and subtitle (issue 1913), miscellaneous (issue 5096050)

2011-09-26 Thread ptrcklschmdt

On 2011/09/25 18:30:51, janek wrote:

2011/9/25  :
> Hi Janek,
>
> I was talking about uploading some changes of this patch to

rietveld. I

> forgot to add some bits and pieces I had announced in the

description of

> this patch to the reworked version. I would have had to adjust only

2 of

> the 3 files in the patch. That's why I asked whether it's possible

to

> upload only these 2 changed files in a new patch, but probably

not...

It is possible.

> As I'm not really experienced with git I would have to redo the

whole

> patch.

That surely won't be necessary.
In fact, it'd be undesired also from our point of view.

> I use Lilydev and git. IIRC I had some problems with lily-git the

last

> time I used it, but I will give it another try...

If you are able to use git via command line, there's no point in
switching to lily-git :)  Lily-git is only an "easy" tool for people
that may have trouble with command line.

So, here is what you need to know about git in your current situation.
  For clarity i'll describe how everything is done from the very
beginning:
1) work begins by cloning git repository from official server to your

Lilydev

2) make changes in files inside working directory (i.e. files that
appear inside lilypond-git)
3) make a commit: 'git commit -a'
4) update your repository: 'git pull -r'
5) upload your patch to Rietveld: 'git cl upload origin/master'
After this step the newly created Rietveld issue will show the
differencies between your local git repository (which contains your
patch, since you have committed it in step 3) and official "master"
repository.  There are differencies in 3 files.
This is the step you are in.
6) make the changes you forgot about to the files in working
directory, save those files
7) commit the changes: 'git commit -a -m "write your commit message
inside quotation marks" ' (you can also omit -m option and write
commit message in the editor that appears)
8) update your repository: 'git pull -r'
9) upload new version of the patch to Rietveld: 'git cl upload

origin/master'

What exactly does this do?  First of all, it doesn't create a new
Rietveld issue, but updates the issue that already exists (that's
good).  It sends the difference between your local git repository and
official repository.  It doesn't matter that it was done as two
commits; the Rietveld tool will look at the diff send and think "there
is a difference in two files between what was previously uploaded and
the current state of things" and update these two files.  We will be
able to see everything - both newest versions of these two files and
your version of the third file (which is already uploaded) - when we
go to http://codereview.appspot.com/5096050/

I hope this makes things clear.  If you have any questions, ask!
Good luck,
Janek

Thanks!

http://codereview.appspot.com/5096050/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

2011-09-26 Thread Han-Wen Nienhuys

On Sun, Sep 25, 2011 at 11:36 PM, Graham Percival
 wrote:
> Please use
>  https://github.com/gperciva/git-cl
> instead of the current git-cl.  To configure, add a file called
>  google.login
> to your lilypond srcdir, in the format
> username
> password
>
> This updated git-cl will:
> - create an issue with Patch-new to code.google.com, including a
>  link to your rietveld issue of course
> or
> - update an existing issue with your Patch-new link if you include
>  "fix xyz" or "issue xyz" in your patch description
>
> There will still be rough edges, but the projecthosting_upload.py
> part of the new git-cl is pretty small and should be easy to
> patch.  Problem reports and patches are most welcome.
>
> Once this script is fully tested and working, it will relieve a
> lot of our current frustrations.  Please switch to it -- even if
> there's a problem with the new parts of the script, the original
> behavior of the rietveld upload is completely unchanged, so you
> lose nothing!

Have you tried sending your commits back to Evan ?  IIRC,  he is very
responsive.

-- 
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

2011-09-26 Thread Julien Rioux


On 26/09/2011 4:36 AM, Graham Percival wrote:

Please use
   https://github.com/gperciva/git-cl
instead of the current git-cl.  To configure, add a file called
   google.login
to your lilypond srcdir, in the format
username
password

This updated git-cl will:
- create an issue with Patch-new to code.google.com, including a
   link to your rietveld issue of course
or
- update an existing issue with your Patch-new link if you include
   "fix xyz" or "issue xyz" in your patch description

There will still be rough edges, but the projecthosting_upload.py
part of the new git-cl is pretty small and should be easy to
patch.  Problem reports and patches are most welcome.

Once this script is fully tested and working, it will relieve a
lot of our current frustrations.  Please switch to it -- even if
there's a problem with the new parts of the script, the original
behavior of the rietveld upload is completely unchanged, so you
lose nothing!

Cheers,
- Graham


I tried this. Rietveld issue was created, but google page issue gave me 
an error. Attaching


--
Julien
Traceback (most recent call last):
  File "../git-cl/git-cl", line 875, in 
sys.exit(main(sys.argv))
  File "../git-cl/git-cl", line 869, in main
return func(argv[2:])
  File "../git-cl/git-cl", line 599, in CmdUpload
projecthosting_upload.upload(issue, patchset, subject, desc)
  File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 108, in upload
status = patchy.upload(issue, patchset, subject, description)
  File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 99, in upload
self.update_issue(issue_id, description)
  File "/home/jrioux/git/git-cl/projecthosting_upload.py", line 71, in 
update_issue
labels = ["Patch-new"])
  File "/home/jrioux/git/git-cl/gdata/projecthosting/client.py", line 133, in 
update_issue
**kwargs)
  File "/home/jrioux/git/git-cl/gdata/client.py", line 685, in post
desired_class=desired_class, **kwargs)
  File "/home/jrioux/git/git-cl/gdata/client.py", line 320, in request
RequestError)
gdata.client.RequestError: Server responded with: 403, No permission to edit 
issue

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Does lilypond 2.15.x support guile 2.0 yet?

2011-09-26 Thread Julien Rioux


On 26/09/2011 2:18 PM, Dave Plater wrote:

On 09/26/2011 10:31 AM, Graham Percival wrote:

On Mon, Sep 26, 2011 at 09:54:18AM +0200, Dave Plater wrote:

Lilypond won't even be able to be installed via tarball on openSUSE
12.1 without the user removing guile 2.0 completely and installing
guile 1.8 via tarball, as a result these users of lilypond and
rosegarden will drop openSUSE.


I believe that users can run GUB no problem. We ship our own
guile-1.8 precisely to avoid this kind of trouble.

Cheers,
- Graham


Well so far I have help from the openSUSE guile maintainer in creating
dual guile versions so it looks like all will be well after all.

Dave


How do you configure lilypond so that it is built against your guile1 
instead of the system-wide guile? I tried to do this recently but could 
not figure it out. I ended up removing guile completely and 
reinstalling, which took much longer.


--
Julien


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Big web page

2011-09-26 Thread Phil Holmes

- Original Message - 
From: "Graham Percival" 

To: "Phil Holmes" 
Cc: "Janek Warchol" ; "Devel" 

Sent: Monday, September 26, 2011 6:39 AM
Subject: Re: Big web page

On Sun, Sep 25, 2011 at 12:32:59PM +0100, Phil Holmes wrote:

So - going on comments concerning GOP, we have had one support, one
comment to the effect that someone once objected, and no-one
objecting.  Please could we consider this as a serious proposal, and
if anyone thinks we need to keep web-big-page.html please say so,
and why.

I object.  I think we should be conservative about removing stuff.
Nobody is seriously complaining about the broken images on
web-big-html, so let's just leave it alone for now.

Note that if web-big-html lacks pictures, then presumably other
manuals (like notation-big-html and contributor-big-html) will
also lack pictures.

No.  This is because web-split is created during make website, whereas 
manual-split is created during make doc.  make doc runs the scripts that fix 
up the images in manuals-split (they're put into the manuals-big correct, 
and into manuals-split wrongly.  The script fixes the wrong ones).

Also note that fixing the pictures can
probably be fixed by adding the right symlink somewhere, or by
moving the -big-html manuals into a separate directory.  If we
really knew how the doc build system worked -- which we don't --
then fixing this would be a 120-second job.  Just leave it alone
until we understand stuff better.

There's nothing to fix except web-big.

I have discovered another reason for getting rid of it - it's almost
impossible to test any work done to change the way it's created (BTW
- this is not a bleat about an error I made earlier, it's something
I've realised as I documented make website).   The command "make
website" doesn't really make the website.

umm...
That's no worse than fixing any other problem in the doc build.

lilypond.org has lots
more content on it - all the manuals, for example, the images, etc.
"make website" doesn't even create web-big-page.html.  "make
website" really only makes the html pages in web.texi.

Yes.  I mean, nobody expected "make website" to produce all the
binaries for download, right?

On my system, those things (manuals, pictures,
web-big-page.html) are only created by the much slower make doc.

Yes.

If it helps, think of "the website" as "stuff immediately
available on lilypond.org/*.html", whereas "the web manual" as
"one of the manuals produced by make doc"

I couldn't think of any way to avoid the name clash.

I've got no problem with what "make website" is called, or what it does.  I 
just wanted to ensure there's clarity about what it doesn't do.

--
Phil Holmes

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Coding par-tay!

Hey all,

For those of you for whom Paris is accessible and who are free on the weekend 
of the 15th, Bertrand and I will be meeting up to start a gutting of the markup 
code in his endeavors to make LilyPond replace LaTeX and in my endeavors to 
make LilyPond recreate the contemporary music example on the SCORE website.  
It'd be great if several people could make it to work on the project.  Lemme 
know if you're able to come and, if so, I'll fill you in on the details.

Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

indent = # isn't the same in \layout or \paper blocks

2011-09-26 Thread -Eluze


hi

if you define the indentation, ragged-right and others in a \layout block
(at top level) the only way to overwrite it is in another \layout block in a
\score block. an overwrite in a \paper block has no effect.

else when the definition is in the \paper block - you can overwrite it for
whole \books or \bookparts in the \paper block or individually at \score
level in the \layout block.

i didn't find a clue to this in the docs and i wonder if this is intended
bevahior!?

also, if you define these variables in a \paper as well as in a \layout
block the value set in the \layout block will dominate.

my personal conclusion is to only use these variables in \paper blocks
(where possible…)

Eluze
-- 
View this message in context: 
http://old.nabble.com/indent-%3D---isn%27t-the-same-in-%5Clayout-or-%5Cpaper-blocks-tp32503941p32503941.html
Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com.


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Does lilypond 2.15.x support guile 2.0 yet?


On 09/26/2011 10:31 AM, Graham Percival wrote:

On Mon, Sep 26, 2011 at 09:54:18AM +0200, Dave Plater wrote:

Lilypond won't even be able to be installed via tarball on openSUSE
12.1 without the user removing guile 2.0 completely and installing
guile 1.8 via tarball, as a result these users of lilypond and
rosegarden will drop openSUSE.


I believe that users can run GUB no problem.  We ship our own
guile-1.8 precisely to avoid this kind of trouble.

Cheers,
- Graham


Well so far I have help from the openSUSE guile maintainer in creating dual 
guile versions so it looks like all will be well after all.

Dave

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 10:52:57AM +0200, m...@apollinemike.com wrote:
> On Sep 26, 2011, at 10:29 AM, Graham Percival wrote:
> 
> > If you have a bit of time, do the github "merge request" thing.
> > Lots of open-source projects are using github, so it's worth
> > doing... and IMHO github just makes the whole process more fun.
> 
> I have 15 minutes tomorrow morning

well, I had 15 minutes now, so I did it.  I also added some other
wyas of recognizing issue numbers.

> lemme know if there's a tutorial somewhere that'll show me how
> to do some editing.

For future reference, this appears to be the place.  Hmm, at first
glance it appears that you need to fork it first.  That doesn't
sound right, because I remember making pull requests to Jan for
GUB, and I haven't forked that.
http://help.github.com/send-pull-requests/

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: anybody know about json + urllib2 ?

2011-09-26 Thread Reinhold Kainhofer

Am Monday, 26. September 2011, 03:15:54 schrieb Graham Percival:
> Does anybody have a passing familiarity with json?  I'm having
> trouble getting started with rietveld json api.  I'm going to work
> on the code.google.com python interaction for the rest of today,
> but it would be great if somebody could get the json thing
> started.

You simply need to add the /api/ to the URL:

wget http://codereview.appspot.com/api/224052

{"description":"FiguredBass: Rewrite of the engraver to fix vertical 
position\n\n-) use list<..> instead of vector<..>\n-) Don't reuse old figure 
storage and no longer
 simply fill in\n   empty positions, which causes ordering to be lost in 
some\n   extender cases.\n-) Add description of engraver 
logic","created":"2010-02-25 15:22:20
.668441","cc":["lilypond-devel@gnu.org"],"reviewers":
["colinpkcampb...@gmail.com","pkx1...@gmail.com","reinh...@kainhofer.com","percival.music...@gmail.com"],"owner_em
ail":"reinhold.kainho...@gmail.com","patchsets":
[1002,2001],"modified":"2011-09-24 
09:51:54.987195","private":false,"base_url":"","closed":false,"owner":"Reinhold","is
sue":224052,"subject":"FiguredBass: Rewrite of the engraver to fix vertical 
position"}


> Task: get a basic "hello world" with riteveld working.  Once I've
> got that, the rest is (relatively) simple.  The following python
> script gives me no joy; it just returns the main webpage.
> 
> 
> #!/usr/bin/env python
> import urllib2
> url = "http://codereview.appspot.com";
> data = "/api/5096046"
> request = urllib2.Request(url, data)

You are basically doing a request to 
http://codereview.appspot.com/?/api/5096046


The correct code is:
request = urllib2.Request(url + data)


reinhold@einstein:~$ python rv.py 
{"description":"Doc: add a note about \\relative f to 
notation","created":"2011-09-21 07:17:28.631011","cc":["lilypond-
de...@gnu.org"],"reviewers":
["d...@gnu.org","pkx1...@gmail.com","percival.music...@gmail.com"],"owner_email":"janek.lilyp...@gmail.com","patchsets":
[1,6001],"modified":"2011-09-26 
10:28:39.716188","private":false,"base_url":"","closed":true,"owner":"janek","issue":5096046,"subject":"Doc:
 
add a note about \\relative f to notation (issue 1909)"}


> Various help pages below, but I think I'm missing something
> fundamental about how json works.

Yes, it's much simpler than you thought: You simply construct an URL and 
download that file. There's no particular data to sent, all arguments are 
encoded in the URL already.

Cheers,
Reinhold
-- 
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: \slashedGrace vs \acciaccatura

2011-09-26 Thread Reinhold Kainhofer

Am Sunday, 25. September 2011, 16:30:48 schrieb Neil Puttock:
> On 25 September 2011 15:19, Phil Holmes  wrote:
> > a) I believe the slashedGrace function is
> > to allow a slurred grace note inside a slur
> 
> Nope.  Reinhold recently added support for separate slurs on graces,
> so they work fine nested inside other slurs.

I think phil meant the correct thing: It is intended to allow a slashed grace 
note inside a slur (where in many manuscripts and editions I encountered, 
there is no slur from the slashed grace note to the real note, since the slur 
is already there, anyway. Some editions have a second slur from the grace note 
to the real note, but many don't.).
So far, we only had 
-) grace: no slur, no slash
-) appoggiatura: slur, no slash
-) acciaccatura: slur, slash

As you can see the combination "slash, but no slur" was missing... That's 
exactly what \slashedGrace is about. There is no unique musical term or fixed 
definition of what it means. It will be used often instead of an acciaccatura, 
when there is already a slur, but I have also seen it without slur.

> b) I'm not convinced a tied grace note makes musical sense
> 
> It's usually used to indicate a note/chord to be played early, at
> least in piano music when it's logistically impossible to sound on the
> beat without a third hand. :)  I believe this is the usage which
> Reinhold was thinking of when he added the new command (see
> grace-slashed-no-slur.ly).

No. I have had that slashedGrace slur in my own packages for quite a while, 
because some composers simply wrote such a thing in their manuscripts (i.e. a 
grace note with a slash, but no slur or tie whatsoever).

The bug report, to which I attached the patch and which was fixed by the 
patch, however, describes exactly this situation of a tied grace note with 
slash.

Cheers,
Reinhold

-- 
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: add a note about \relative f to notation (issue 1909) (issue 5096046)

2011-09-26 Thread Janek Warchoł

2011/9/26  :
> LGTM.  If you wanted to add a @lilypond to make it more visible, I'm
> happy with that, otherwise just go ahead and push.

pushed 0d4c0b0979c200e54cffc6b68671df50d6b90a49

I've accidentally created a new branch 'relativef' in savannah
repository - sorry for that, it was a typo.  I've deleted it already.

cheers,
Janek

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Does lilypond 2.15.x support guile 2.0 yet?


On 09/26/2011 10:31 AM, Graham Percival wrote:

On Mon, Sep 26, 2011 at 09:54:18AM +0200, Dave Plater wrote:

Lilypond won't even be able to be installed via tarball on openSUSE
12.1 without the user removing guile 2.0 completely and installing
guile 1.8 via tarball, as a result these users of lilypond and
rosegarden will drop openSUSE.


I believe that users can run GUB no problem.  We ship our own
guile-1.8 precisely to avoid this kind of trouble.

Cheers,
- Graham

My intention is to persuade openSUSE to revert to guile-1.8 I can see no problem with this and hopefully I can generate some support for 
this cause. I'm updating solfege atm and it's failing on lilypond in factory but lilypond is an optional requirement so I've moved lilypond 
from a build requirement to a "Recommends:" temporarily until this is resolved. I haven't yet checked to see if there are other casualties 
due to lilypond's failure. I may, at least, be able to move lilypond to the Packman repo and have a guile 1 there but it will have the 
problem of removing guile 2 when installed.
I don't know very much at all about GUB, is it possible that I can package it and make an rpm from it that will enable the parallel use of 
it? I haven't much time, because I was disconnected from the internet due to unfortunate circumstances from end June to mid August I missed 
the lilypond build failure when guile was updated and new packages will no longer be possible soon.


Thanks
Dave

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Sep 26, 2011, at 10:29 AM, Graham Percival wrote:

> On Mon, Sep 26, 2011 at 09:35:32AM +0200, m...@apollinemike.com wrote:
>> On Sep 26, 2011, at 9:29 AM, Graham Percival wrote:
>> 
>>> Anybody feel like patching find_fix_issue_id ?
>> 
>> if word in ["fix","issue","Fix","Issue"] :
> 
> ok, that's simple enough.
> 
>> Just lemme know what I need to do to patch the file.
> 
> If you have a bit of time, do the github "merge request" thing.
> Lots of open-source projects are using github, so it's worth
> doing... and IMHO github just makes the whole process more fun.
> :)


I have 15 minutes tomorrow morning - lemme know if there's a tutorial somewhere 
that'll show me how to do some editing.

Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Does lilypond 2.15.x support guile 2.0 yet?

On Mon, Sep 26, 2011 at 09:54:18AM +0200, Dave Plater wrote:
> Lilypond won't even be able to be installed via tarball on openSUSE
> 12.1 without the user removing guile 2.0 completely and installing
> guile 1.8 via tarball, as a result these users of lilypond and
> rosegarden will drop openSUSE.

I believe that users can run GUB no problem.  We ship our own
guile-1.8 precisely to avoid this kind of trouble.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 09:35:32AM +0200, m...@apollinemike.com wrote:
> On Sep 26, 2011, at 9:29 AM, Graham Percival wrote:
> 
> > Anybody feel like patching find_fix_issue_id ?
> 
> if word in ["fix","issue","Fix","Issue"] :

ok, that's simple enough.

> Just lemme know what I need to do to patch the file.

If you have a bit of time, do the github "merge request" thing.
Lots of open-source projects are using github, so it's worth
doing... and IMHO github just makes the whole process more fun.
:)

If you're not interested, or if you don't have a github account
yet, I can just make the change manually myself; this one is
simple enough.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: current master gives strange warning

2011-09-26 Thread David Kastrup

David Kastrup  writes:

> "m...@apollinemike.com"  writes:
>
>> is anyone else getting:
>>
>> warning: identifier name is a keyword: `relative'
>
> Sounds like your lily/lily-parser.cc is out of date with respect to your
> ly/music-functions-init.ly or you just forgot to recompile after the
> last update.

Sorry, I mean lily/lily-lexer.cc.

> \relative has been removed from grammar and parser.  It now is merely a
> music function, so one can override it (like, say, make it default to
> \relative f instead of \relative c') if one wants to.

-- 
David Kastrup


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: current master gives strange warning

On Sep 26, 2011, at 10:13 AM, David Kastrup wrote:

> "m...@apollinemike.com"  writes:
> 
>> is anyone else getting:
>> 
>> warning: identifier name is a keyword: `relative'
> 
> Sounds like your lily/lily-parser.cc is out of date with respect to your
> ly/music-functions-init.ly or you just forgot to recompile after the
> last update.
> 
> \relative has been removed from grammar and parser.  It now is merely a
> music function, so one can override it (like, say, make it default to
> \relative f instead of \relative c') if one wants to.
> 

Quite right quite right - sorry for the noise!

Cheers,
MS


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: current master gives strange warning

2011-09-26 Thread Neil Puttock

On 26 Sep 2011 09:08, "m...@apollinemike.com"  wrote:
>
> is anyone else getting:
>
> warning: identifier name is a keyword: `relative'

Sounds like you've pulled the latest changes without rebuilding.

You'll only get that message if the lexer hasn't been recompiled, since
David's removed that token.

Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: current master gives strange warning

2011-09-26 Thread David Kastrup

"m...@apollinemike.com"  writes:

> is anyone else getting:
>
> warning: identifier name is a keyword: `relative'

Sounds like your lily/lily-parser.cc is out of date with respect to your
ly/music-functions-init.ly or you just forgot to recompile after the
last update.

\relative has been removed from grammar and parser.  It now is merely a
music function, so one can override it (like, say, make it default to
\relative f instead of \relative c') if one wants to.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

current master gives strange warning

is anyone else getting:

warning: identifier name is a keyword: `relative'

Cheers,
MS

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Does lilypond 2.15.x support guile 2.0 yet?

On 09/24/2011 10:22 PM, Graham Percival wrote:

On Fri, Sep 23, 2011 at 03:53:56PM +0200, Dave Plater wrote:

If all else fails maybe I can use the release candidate of lilypond
for openSUSE 12.1 and update to 2.16.0 before release.

There is absolutely zero chance of lilypond 2.16 using guile 2.0.
There is maybe a 10% chance that any version of lilypond will
support guile 2.0 in 2011. Total guesswork for future
predictions: 50% chance of supporting guile 2.0 before July 2012,
80% chance of support guile 2.0 before the end of 2012.

What that means for opensuse is up to you. If you particularly
want guile 2.0, then by all means jump in; the more people working
on it, the higher the chances are that it'll get done sooner. But
based on the amount of work that currently goes into guile 2.0,
those are my estimates.

Cheers,
- Graham

I'm pasting my message opensuse-factory (the next release 12.1 development list) cc'ed to opensuse-packaging, opensuse-project,
opensuse-marketing and the maintainer that updated guile to 2.0.1 from 1.8.7 who ironically is the person that I took over maintenance of
lilypond from. My bet is that we will revert to guile 1.

Dave Plater
OpenSUSE has jumped way ahead of all the other major distributions by pushing guile-2.0 to factory, this may cause problems for packages
such as gnucash if it uses guile to the extent that lilypond does. Lilypond uses guile extensively and are working on porting lily to guile
2.0 but this is their timeline quoted from one of my emails from Graham Percival to the devel list please note that lilypond 2.16.0 may not
be released before openSUSE 12.1 and I'm working on 2.14.2 atm the current release :

Cheers,
- Graham

and I think this is also relevant, another lily developers reply from the same
message:

Given that the upcoming ubuntu oneiric apparently does not include guile 2.0, I
also don't see a switch to guile 2.0 in the near future.
I suppose that we should ask the ubuntu people when they'll finally package
guile 2.0.

Cheers,
Reinhold

I've looked at parallel installation of guile 1.8.8 (we jumped from 1.8.7 to 2.0.1) and it doesn't look easy otherwise I would have
submitted guile1 but I'm still working on it although I'm not that familiar with the autoconf/automake build system at this level.

What this means for openSUSE, lilypond is a very popular musical notation type setting program, the developers pride themselves in the
accuracy of the notation positions, it is also used, for musical notation by rosegarden, a popular music and midi composition program. Both
of these applications have no substitutes in the open source world and only have costly equivalents in the ms windows world, neither being
available for ms windows although there are requests to port for both this won't happen in the immediate future. Rosegarden can work
without lilypond as it is only bound to lilyponds notation fonts but the sheet music it exports will be useless so it will lose major
functionality.
Lilypond won't even be able to be installed via tarball on openSUSE 12.1 without the user removing guile 2.0 completely and installing
guile 1.8 via tarball, as a result these users of lilypond and rosegarden will drop openSUSE.

I started as a community maintainer by saving both lilypond and rosegarden from being dropped, I'm now very active in maintaining
multimedia apps and libs and losing these programs will mean losing a large section of professionals in music related professions that have
migrated from the windows world including the people that I've converted from ms windows just by showing them rosegarden although ms's
change from xp to vista also helped.

For the other packages that directly depend on guile : guile aisleriot gnucash autogen and slib, the change back to guile-1.8.8 won't
AFAICS have any negative effects, all of these packages simply have patches for guile 2.0 and after looking at the patches, will most
probably build with the patches still in place. I don't know what the situation is with guile users but it is an app for use by apps and
not a direct users app. Guile-1.8.7 builds for factory, guile-1.8.7 doesn't build for 11.4.

What are we going to do? Drop lilypond, I will keep it alive in home:plater:lilypond with guile-1.8.8 to replace guile-2.0.2 or revert to
guile-1.8.8 in line with the other linux distributions?

Thanks
Dave Pla

Re: Implement optional music function arguments (issue 5023044)

2011-09-26 Thread dak



http://codereview.appspot.com/5023044/diff/22001/scm/ly-syntax-constructors.scm
File scm/ly-syntax-constructors.scm (right):

http://codereview.appspot.com/5023044/diff/22001/scm/ly-syntax-constructors.scm#newcode52
scm/ly-syntax-constructors.scm:52: (format #f (_ "~a function can't
return ~a")
On 2011/09/25 22:25:35, Ian Hulin (gmail) wrote:

(_ "~a function cannot return ~a")
Sounds more official and serious and less chatty than "can't".


Picking German as one of the more complete catalogs:

$ git grep -c "can't" po/de.po
po/de.po:12
$ git grep -c "cannot" po/de.po
po/de.po:63
$ git grep -c "can not" po/de.po
po/de.po:2

Does not seem like that policy is kept perfectly consistent.  On the
other hand, I have to admit being surprised that we use the
predominantly British spelling here while using "color" exclusively and
preferring "neighbor" over "neighbour" 3:1 and using "centre" almost
only in the translations.

I'll do the change soonish.

http://codereview.appspot.com/5023044/

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Sep 26, 2011, at 9:29 AM, Graham Percival wrote:

> On Mon, Sep 26, 2011 at 09:03:04AM +0200, m...@apollinemike.com wrote:
>> It looks like it created a new issue on the tracker (1937), although I put 
>> "Issue 1929" in the message describing this patch set:
> 
> heh.
> https://github.com/gperciva/git-cl/blob/master/projecthosting_upload.py#L77
> it just occurred to me that it would get confused about
> (fix 123)
> nor does it support our vaguely customary "do blah blah (123)".
> 
> Anybody feel like patching find_fix_issue_id ?

if word in ["fix","issue","Fix","Issue"] :

> It's not
> complicated code at all, and I'd rather do the heavy lifting on
> allowing people to run git-cl without installing gdata, and on
> making a buildbot which auto-tests patches so that James doesn't
> have to do it manually.
> 

Just lemme know what I need to do to patch the file.

Cheers,
MS


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl

On Mon, Sep 26, 2011 at 09:03:04AM +0200, m...@apollinemike.com wrote:
> It looks like it created a new issue on the tracker (1937), although I put 
> "Issue 1929" in the message describing this patch set:

heh.
https://github.com/gperciva/git-cl/blob/master/projecthosting_upload.py#L77
it just occurred to me that it would get confused about
  (fix 123)
nor does it support our vaguely customary "do blah blah (123)".

Anybody feel like patching find_fix_issue_id ?  It's not
complicated code at all, and I'd rather do the heavy lifting on
allowing people to run git-cl without installing gdata, and on
making a buildbot which auto-tests patches so that James doesn't
have to do it manually.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

I'm a student

2011-09-26 Thread Phil Holmes

Or I will be from today.  I'm off to the first day of freshers' week in a 
few minutes.  This week it's pretty much full time with fresher's 
activities.  Fairly part-time from next week.  Just need to sign up for all 
those clubs I'll never go to.


--
Phil Holmes



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: replacement git-cl