Re: Reasons why a LilyPond-to-MEI conversion should be developed

[Urs Liska]

Hi Simon,

thank you for that comment that is very much to the point in a number of
respects. Anyway, I have a few clarifications and/or additions to report.

Am 24.10.2015 um 01:39 schrieb Simon Albrecht:
> On 23.10.2015 17:44, Urs Liska wrote:
>> Hello devs,
>>
>> I would like to get some feedback for use when preparing the mei2ly
>> application. I will deliberately not say what I think about the topic to
>> get less influenced opinions.
>>
>> We will have to define a scope for the project that is sufficiently big
>> and at the same time not too small.
> 
> That’s tautological the way you wrote it. 

Of course, sorry.

> Do I get you right
> interpreting this as ‘should be ambitious but realistic’?

Yes, that's what I wanted to write.

> 
>>   Apart from what we may be interested
>> in it's important to be plausible and credible in order to get the
>> application accepted.
>>
>> mei2ly, the possibility to use LilyPond to engrave MEI encoded editions,
>> is clearly the foundation of the project, so there's nothing to argue
>> about that. There are technical aspects, e.g. if LilyPond should consume
>> MEI
> 
> Interesting thought. I should be surprised if MEI were to consent in
> granting LilyPond this honour (as which I’d consider it). Given the
> ‘universal’ intent of MEI, they might not want to ‘take sides’ with
> LilyPond (as opposed to other typesetting software) in such a complete
> and definite way.

I'm not sure if Richard really got you right, and I'm not sure if *I*
understand you right.

The idea is adding LilyPond as a "rendering engine" for MEI editions,
making it possible to produce professional engravings from MEI editions.
If you consider this an honor then yes, they *are* consenting to that idea.

So far there is *no* option to produce high-quality engravings from MEI
(unbelievable, isn't it?). Existing editions do one of the following:
- use Verovio (http://verovio.org), a very intersting tool that can
  render MEI as SVG, more or less instantly, with automatic reflow in
  a browser, and with tools to rewrite modifications in the SVG to
  the XML source file.
  It's a great tool but not targeted at professional engraving.
  This is in line with digital editions focusing on the flexible
  *use* and manipulation of the data.
- Create specialized engraving tools for special (e.g. medieval)
  notations
- Create an "authoritative" version of the score separately
- Work with pre-existing (publisher's) engravings and only add the
  "digital" content besides that.

Adding LilyPond to the toolkit would finally open up a way to produce
professional scores from within the MEI realm. Therefore they are
extremely happy with my advances.
They are not "taking sides" but welcome an additional tool in their toolbox.

> 
>>   or if a converter should produce LilyPond input (or to have both),
>> but the conversion direction itself is of course a prerequisite of all
>> discussion.

With regard to Richard's comment I'd like to add here:
I don't think consuming MEI should be built into LilyPond's executable
because that would unnecessarily bloat it. And I don't think and
wouldn't propose that MEI becomes LilyPond's native input langugage.

With "consuming directly" I'm referring to *some* way of doing the
process without touching LilyPond's input language. For example a
secondary script might convert MEI to some format that can be fed into
LilyPond, something similar to (make-music) expressions.

This script could either run standalone and then invoke Lilypond on the
intermediate data. Or it could be implemented in a way that it runs from
*inside* LilyPond, but not from the executable but some kind of Scheme
module.

In either case this may be easier because the whole area of LilyPond
syntax could be circumvented.
One crucial point here would be the improvement of the edition-engraver,
in a way that all necessary overrides for perfecting the output could be
injected into that stream. This is also one of the points where our
project will have direct impact on LilyPond in general, providing
new/improved solutions that any LilyPond user can benefit from.

>>
>> The other way round is less clear. Should it be possible to convert
>> LilyPond scores into MEI data?
> 
> From the code samples I’ve seen, I can’t seriously imagine anybody
> _entering_ music in .mei directly.

There are people/projects who actually do that.
I wouldn't want to do so either but that's a matter of perspective. A
typical Finale user would say the very same of a LilyPond input file.

> So there must be some kind of ‘frontend’ for the input. 

There are various attempts to develop generic, semigraphical tools for
that. But the common approach so far is entering the main content in
Finale and using a path through MusicXML export and then several stages
of XSLT processing. I find this extremely non-satisfying.

Then there are a few approach of developing "native" MEI editors, but I
don't think anything really usable is available already. But 

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[David Kastrup]

Noeck  writes:

> Me personally, I don't see the point in creating MEI files. I like the
> LilyPond input language. It is a concise and human readable
> representation of the music. I can use version control (git). I don't
> see what MEI would improve for me. I guess MEI is rather less readable
> and auto-generated ly code likely, too (therefore I don't use Denemo).
> My desired output format is pdf – so I have what I need. Perhaps if
> freely available databases with MEI encoded music would exist, it
> could get interesting to convert these to ly for further tweaks.

The main point of some stupid straightforward XML-based format is that
computer-based transformations are readily possible.  For MusicXML,
there are filters converting a "stream-based" (or what it was called)
representation into a time-based one, implemented with straightforward
XML tools.  In LilyPond, we need iterators in one direction and don't
have anything for the reverse direction.

The only computer-based tool with a reliable understanding of LilyPond
syntax is LilyPond itself.

> So, I support the idea but I see no personal advantages.

It's like PostScript vs PDF.  Nobody wants to write PDF code if he can
write PostScript instead.  On the other hand, nobody wants to write an
interpreter for PostScript if he can write one for PDF instead.

Look which of the two is more prevalent these days.

-- 
David Kastrup

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

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[David Kastrup]

Simon Albrecht  writes:

> On 24.10.2015 16:54, David Kastrup wrote:
>> They are not in LilyPond.  There is no tangible or recognizable thing
>> like a "music stream"
> […]
>> chances are rather slim that parts of the code
>> could be usefully adapted to work with LilyPond these days.
>
> What a pity, it would have seemed a nice starting point.

The event-listener code in partcombiner.scm (?) would be a starting
point along this line.  There is also event-listener.ly.  It's not like
the tools aren't there.  The problem would be more along the line of
ensuring that indeed all pertinent information is passed through events
and that the events are sufficient for identifying the event hierarchy.

-- 
David Kastrup

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

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[Simon Albrecht]

On 25.10.2015 09:15, Urs Liska wrote:

if LilyPond should consume
>>MEI

>
>Interesting thought. I should be surprised if MEI were to consent in
>granting LilyPond this honour (as which I’d consider it). Given the
>‘universal’ intent of MEI, they might not want to ‘take sides’ with
>LilyPond (as opposed to other typesetting software) in such a complete
>and definite way.

I'm not sure if Richard really got you right, and I'm not sure if*I*
understand you right.

The idea is adding LilyPond as a "rendering engine" for MEI editions,
making it possible to produce professional engravings from MEI editions.
If you consider this an honor then yes, they*are*  consenting to that idea.


OK, I mistook you there. I read your ‘consume’ as ‘make the entire MEI 
_project_ a part of the LilyPond project’. I might have known that you 
couldn’t have meant that :-)


Yours, Simon

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

Re: modify coord-rotate to get exact values for (sin PI) etc (issue 269530043 by thomasmorle...@gmail.com)

[thomasmorley65]

On 2015/10/21 09:32:07, dak wrote:

https://codereview.appspot.com/269530043/diff/40001/scm/lily-library.scm

File scm/lily-library.scm (right):



https://codereview.appspot.com/269530043/diff/40001/scm/lily-library.scm#newcode721

scm/lily-library.scm:721: (moved-angle (- angle (/ (* quadrant PI)

2)))

Ok, let's just tackle this as a theoretical exercise since I remain

unconvinced

that we are doing ourselves much of a favor straying from degrees

except at the

final step.  Then angle-0-2pi is basically an independent source of

numerical

ambiguity we want to avoid.  So I'd probably do it as follows:



(let* ((quadrant
(inexact->exact (round (/ angle PI/2
(moved-angle (- angle (* quadrant PI/2)))
(s (sin moved-angle))
(c (cos moved-angle))
(x (coord-x coordinate))
(y (coord-y coordinate)))
   (case (modulo quadrant 4)
 ((0) % -45 .. 45
  (cons ...))
 ((1) % 45 .. 135
  (cons ...))
 ((2) % 135 .. 225
  (cons ...))
 ((3) % 225 .. 315
  (cons ...



Note that this retains the problem that (* quadrant PI/2) might just
not be properly representable which can make the whole exercise end up
still not delivering perfect values for 3*PI/2 or 5*PI/2 or similar,
depending on just how those values were arrived at.  However,



(* exact-integer PI/2) likely has about the best chance to match
values that the user arrived with using similar expressions of his
own.  I'd also don't make two separate case statements for cos and sin
since that's likely a construct that is a bit expensive.


Changed it following your proposal.
Up to now I found no drawback.


https://codereview.appspot.com/269530043/diff/40001/scm/lily-library.scm#newcode751

scm/lily-library.scm:751: (cyclic-base-value (+ value cycle) cycle))
On 2015/10/20 23:06:58, thomasmorley651 wrote:
> what are those red dots??
> Never seen them before.



Spaces before tabs would be my guess.  Or just generally a spacing

change.

either of the two.


Must be spacing change then



https://codereview.appspot.com/269530043/

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

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[Urs Liska]

Hi Joram,

some valid points here, but also some "beside the point":

Am 24.10.2015 um 22:11 schrieb Noeck:
> Hi Urs,
>
> possible advantages could be: a larger user base and maybe contributions
> from more (academic/professional/knowledgeable) people to the engraving
> quality of LilyPond. 

This is true, and one of the reasons why I think LilyPond should bother
with this idea in the first place. But that's not what I wanted to know.
I'm explicitly asking: "Why should a project to integrate LilyPond in
the MEI context also develop the ly2mei direction. Isn't mei2ly
sufficient?" And this question is explicitly asked from the MEI
perspective because that will be the perspective of the application and
particularly the people who will evaluate the application.

> Offering a high quality engraving solution for an
> already existing community. 

This is the obvious reason why my project is received so favourably. But
that's only affects the mei2ly direction, not ly2mei.

> And other synergy effects and perhaps
> funding. As the input is further disentangled from the output, users
> could use any input tool that supports MEI and still can get LilyPond
> output. That way we could have a GUI input method (which I presume
> exists for MEI) for free. That's what comes to my mind.

This is also correct and also beside the question or rather only
addressing the mei2ly issue.

But I think it is important to stress that even though the project is
initiated from the MEI perspective, that is from "adding LilyPond to
MEI" LilyPond will benefit a lot from it, not only from the aspect of
user base, potential use cases for our existing users etc. but also
technically, through improvements that have to be made as prerequisites
for mei2ly. And hopefully because such a project will be a "catalysator"
for a generally more active development.

>
> Me personally, I don't see the point in creating MEI files. I like the
> LilyPond input language. It is a concise and human readable
> representation of the music. I can use version control (git). I don't
> see what MEI would improve for me. I guess MEI is rather less readable
> and auto-generated ly code likely, too (therefore I don't use Denemo).
> My desired output format is pdf – so I have what I need. 

This is an important point. If you are a common LilyPond user interested
in creating PDF scores then ly2mei doesn't add anything of value for
you. But what David said is not just a theoretical thing. LilyPond
scores can basically only be used with LilyPond. If you'd be able to
convert them to MEI you'd have the option of general-purpose XML
operations and any tools that the MEI community has or will produce, for
example analytical applications or storing the scores in common
databases or whatever. Particularly everything around the concept of
digital editions, that is: bringing your scores to a browser, making it
interactive, enhancing content with metadata etc.

This may not be something that you, Joram, are after, but something that
could be considered a rather common use case for LilyPond users.

Finally there is something that seems to be at the horizon when both
mei2ly and ly2mei exist at the same time. What I would very much like to
see is an integrated environment (e.g. in Frescobaldi) where you can
edit a score in .ly format, have instant preview through ly2mei2verovio,
possibly graphical content editing features through Verovio, and only in
the end use LilyPond for the graphical result.

Best
Urs

> Perhaps if
> freely available databases with MEI encoded music would exist, it could
> get interesting to convert these to ly for further tweaks.
>
> So, I support the idea but I see no personal advantages.
>
> Cheers,
> Joram
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel


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

Re: Allure and git-cl troubleshooting

[Paul Morris]

> On Oct 25, 2015, at 5:14 PM, Trevor Daniels  wrote:
> 
> Thanks Paul - should be good to go now.

Thanks, good to be on board.

I gave git-cl another try and got the same error from my previous message, 
ending in:

File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
  raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found

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

Re: Issue 4504 whiteout-style

[Paul Morris]

Hi Simon,

> On Oct 25, 2015, at 6:02 PM, Simon Albrecht  wrote:
> 
> I think this is not the best possible setting: If I want to apply 
> whiteout-outline now, I have to use two overrides. IMO it would be easier to 
> use if we had the two properties
> – whiteout [possibly whiteout-style], with options 'none, 'box, and 'outline
> – and whiteout-padding (a number).
> What do you think?

Hmmm… that seems worth considering.  (And a good reminder for me to propose 
changes and hash out the best plan first before doing the full work of 
implementation...)  I’ll give it some thought.  Lets move this discussion to 
the issue tracker, to keep it all in one place:

https://sourceforge.net/p/testlilyissues/issues/4504/

Also, the issues will be easier to discuss once the proposed changes are up on 
Rietveld...

Thanks,
-Paul

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

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

Paul Morris wrote Sunday, October 25, 2015 9:33 PM


> I gave git-cl another try and got the same error from my previous message, 
> ending in:
>
> File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
>  raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
> urllib2.HTTPError: HTTP Error 404: Not Found

Hhm, assuming you've got a bearer token from
https://sourceforge.net/auth/oauth/, 
and have set up the full url to the correct page:
https://sourceforge.net/p/testlilyissues/issues/
I don't know what else might be wrong.

We'll have to let Phil have a look.

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

Re: Issue 4504 whiteout-style

[Simon Albrecht]

Hello Paul,

On 25.10.2015 20:39, Paul Morris wrote:

Introduce whiteout-style, with options of
 'box and 'outline, as a grob property to be
 used with the whiteout grob property, and as
 an optional property of the whiteout markup
 command.
 
 Remove the whiteout-box grob property and

 markup command, and use whiteout-style
 instead.
 
 Make the box style of whiteout the default

 style again, as it was before issue 4418.


I think this is not the best possible setting: If I want to apply 
whiteout-outline now, I have to use two overrides. IMO it would be 
easier to use if we had the two properties

– whiteout [possibly whiteout-style], with options 'none, 'box, and 'outline
– and whiteout-padding (a number).
What do you think?

Yours, Simon

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

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[Joram]

Hi Urs,

I totally overlooked the 'LilyPond-to-MEI' part (the central part) of
your question. And I wondered why you ask that question while knowing
already so many good answers to it. Sorry.

> This may not be something that you, Joram, are after, but something that
> could be considered a rather common use case for LilyPond users.

That's why I wrote 'personally'.

> Finally there is something that seems to be at the horizon when both
> mei2ly and ly2mei exist at the same time. What I would very much like to
> see is an integrated environment (e.g. in Frescobaldi) where you can
> edit a score in .ly format, have instant preview through ly2mei2verovio,
> possibly graphical content editing features through Verovio, and only in
> the end use LilyPond for the graphical result.

That's indeed a valid point which I did not see so far: Verovio based
GUI possibilities and the XML-based transformations David told me.

For all the rest: Yes, I missed the point of your question and yes, I
think this is a good thing in general.

Cheers,
Joram

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

Re: My finances for working on LilyPond

[Paul Morris]

> On Oct 23, 2015, at 9:19 AM, Federico Bruni  wrote:
> 
> 1) DOWNLOAD PAGE
> What's the most viewed page in the website (excluding the home)? Probably the 
> download page:
> http://lilypond.org/website/download.html
> 
> Let's add there a big Note saying something like: "Our most active main 
> developer David Kastrup is working full-time on LilyPond development and need 
> your support to make a living. If you use and love LilyPond, please allow 
> David to continue his precious work by contributing whatever amount of money 
> you can afford. [link to Community>Sponsoring page]"
> 
> 2) SPONSORING PAGE
> I can guess without looking at 'git log' that the sponsoring page was written 
> by Graham :-)
> It does not encourage any donation, right? The feeling is very different from 
> what we are reading in many replies in this thread. Maybe it's time to change 
> it a little bit?
> 
> 3) GITSTATS

I agree that doing some things along these lines would be a good idea.  

Another possibility is to combine the "help us"[1] and “sponsoring"[2] pages.  
That way all the ways to help further LilyPond are in one place and we could 
link to it from the download page and/or home page with some appropriate 
message.  Combining these pages would also help reduce the large number of 
sub-pages under Community heading.  The content of the “sponsoring” page could 
become a single section on the “help us” page with a heading like “Bounties and 
Sponsorships”.  Maybe “contributing” is a good heading for all these things, 
i.e. we could have a single “contributing” page instead of “help us” and 
“sponsoring” pages?  

(Apparently I’m always thinking about what to name things…)

-Paul

[1] http://lilypond.org/help-us.html
[2] http://lilypond.org/sponsoring.html



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

Re: My finances for working on LilyPond

[David Kastrup]

Jacques Menu  writes:

> Hello folks,
>
> I’m only an amateur musician, but I really appreciate Lilypond’s
> availability. I haven’t been creating scores any other way since I
> first encountered it at the time of version 2.12.
>
> Current example : Bach’s Magnificat, in which I partly double the
> cello with the bassoon, has many alterations changes. I’m using «
> \accidentalStyle Score.teaching » to have all of them made explicit,
> which greatly helps the bad reader I am.

Well, the current syntax of the command is due to me, and some overhaul
of the internals and making sure that accidentals are repeated after
clef changes (yes, I have read the request by someone else(?) just now
to stop that again but have not yet had the time and/or energy to reply
yet, sorry, willdo eventually).  But the functionality as such was
available from before my time...

> For the same, I transposed a flûte part one half-tone to help the
> player (she’s young and still a music school pupil) getting a better,
> more plain sound using another flute.

Well, I messed with the definition of the \transposition command to make
it somewhat less weird.  But transpositions still are not really the
most fantastic part of LilyPond, particularly with MIDI.

Like with many other things, so much remains to be done...

Probably not worse than other programs though.

> I feel guilty for not having contributed yet, since I’m much indebted
> to the people who make Lilypond alive and evolving, including those
> who provide help on this list.  I’ve been a C++ developper in a former
> life, and I have an idea of the kind of arduous work David Kastrup
> performs with such a big piece of software.  And LP doesn’t benefit
> from support by big computer science companies, as some other open
> software products do.

The OpenSSH(?) situation was remarkably bad for a long time.  Something
used everywhere, and the single core developer no longer able to support
himself.  At least that has made people attentive.  LilyPond is not an
integral part of similarly essential offerings.  Perhaps we need to work
on that in order to make wake-up calls reach bigger money than they
currently do.  It's basically all volunteers without economic dependence
on LilyPond.

> So, David, please send me your IBAN privately, and I’ll fix this
> problem on my side.

Will do.

Thanks!

-- 
David Kastrup

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

Re: My finances for working on LilyPond

[David Kastrup]

Simon Albrecht  writes:

> On 22.10.2015 19:21, David Kastrup wrote:
>> As you all know, my sole source of income are donations from happy
>> LilyPond users.  It would appear that LilyPond users have stopped being
>> happy with my work.
>
> You must know that this is not the case. I should be much surprised if
> I were the only one to appreciate the highly complicated work you do,
> of which the results sometimes are hard to grasp in their immediate
> effect. But that does not diminish their value for the project at all,
> and unless I’m much mistaken nobody currently working on LilyPond
> could rival your understanding of the internals and your ability to
> fix them.

Sounds like a liability more than an asset.  I do hope that I am moving
in a direction where acquiring such understanding will become easier but
the movement is slow as molasses.

In the backend area, I think that of the active programmers, Keith
O'Hara still has a better grasp of what is going on.  Particularly with
regard of weird dependencies so I am aiming to annihilate his advantage
in the long run by getting rid of the need for dealing with weird
dependencies manually.  Cheating, I know.

Dan has been taking up a number of C++ issues recently and also worked
on moving things to more mainstream C++.  David Nalesnik has been doing
impressive things using Scheme alone, and Thomas Morley's contributions
are not to be sneezed at either.  I am glad that there is a bit more
volume of work actually happening since, "understanding of the
internals" or not, solving individual problems is still taking a lot of
time and I am not particularly productive in that area.  Probably
age-related as I've passed 50.

> I do not think one can construe a link between the work you do and the
> sudden (?) decrease of funding;

I don't think it would be sudden.  It's been over a year since I started
procrastinating about even taking a look at my finances and/or writing
about them.  I haven't yet looked further backward yet, but the Paypal
account, usually responsible for a third or so of contributions, has
been pretty dry for at least half a year or so when making small
purchases.

Of course, I'll still have to face the music eventually, but the total
level of my bank account is roughly 4000 down from what I remember about
a year or so ago.  And I actually sold off one accordion in that time.

> indeed, you continue to make quite impressive and important changes.
> I have taken so much profit from your work that it’s about time I gave
> something back. It can’t be as much as I’d certainly like to give, but
> if I don’t remain the only one to take part, it will make a
> difference. Please tell me (privately, I assume) where to direct the
> support. (You probably know that I live in Germany.)

Via separate mail.  Thanks

-- 
David Kastrup

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

Re: Allure and git-cl troubleshooting

[Federico Bruni]

Il giorno dom 25 ott 2015 alle 20:48, Paul Morris 
 ha scritto:
urllib2.URLError: certificate verify failed (_ssl.c:581)>


Installing the package ca-certificates should fix it (I added it to 
LilyDev after generating the ISO you are using...).





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

Re: LilyDev version 4.0 released

[Paul Morris]

Hi Federico,

I’ve installed and used the new LilyDev 4 and am glad to report that everything 
is working well.  Thanks for updating it.  Here are a couple minor things I’ve 
noticed:

- gedit wasn't installed on my instance for some reason.

- nano is already set up as the default editor (which is great for those like 
myself who don’t have a clue about vi/vim) so it probably makes sense to edit 
the CG[1] to make it clearer that if you’re using LilyDev you don’t need to 
bother with setting nano as the editor with git config. 

[1] 
http://lilypond.org/doc/v2.19/Documentation/contributor/setting-up#configuring-git

Thanks again,
-Paul


> On Oct 12, 2015, at 12:15 PM, Federico Bruni  wrote:
> 
> Hi all
> 
> I've just uploaded the new LilyDev iso to Github:
> https://github.com/fedelibre/LilyDev/releases/tag/v4.0
> 
> Please test it. If it's working fine we should update the CG.
> 
> Thanks
> Federico
> 
> 
> Notable changes:
> 
> - Upgrade to **Debian 8 Jessie** and **live-build 4**.
> - **Interactive Git setup** at first startup to create user's `~/.gitconfig` 
> and download LilyPond git repositories (which were previously included 
> out-of-date in the image).
> - Installation simplified through preseed.cfg: no need to choose a repository 
> mirror or a root password (defaults to httpredir.debian.org and sudo).
> - `.bashrc` improved: terminal prompt shows git branch, plus other fixes.
> - Live option removed from the boot menu.
> - Add new lilypond dependency: fonts-texgyre.
> - Add a few packages: less, gedit, geany, spice-vdagent (to enable clipboard 
> sharing in QEMU).
> - Chromium has replaced Iceweasel (a.k.a. Firefox) as default browser.
> 
> You can check the integrity of the file with this command:
> 
>   $ md5sum lilydev-4.0-i386.hybrid.iso
>   9da792275907b44cd6b98f67b64a33f5  lilydev-4.0-i386.hybrid.iso
> 
> 
> 
> 
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel


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

Re: LilyDev version 4.0 released

[Federico Bruni]

Il giorno dom 25 ott 2015 alle 21:14, Paul Morris 
 ha scritto:
I’ve installed and used the new LilyDev 4 and am glad to report 
that everything is working well.  Thanks for updating it.


Thanks, I'm glad that it's useful


  Here are a couple minor things I’ve noticed:

- gedit wasn't installed on my instance for some reason.


It's because I forgot it while rearranging configuration files:
https://github.com/fedelibre/LilyDev/commit/ffeb242eac86530b4e0c70261c4c558f9c1e8d43

Or maybe I decided that Geany was enough. But I can put gedit back in 
the list.




- nano is already set up as the default editor (which is great for 
those like myself who don’t have a clue about vi/vim) so it 
probably makes sense to edit the CG[1] to make it clearer that if 
you’re using LilyDev you don’t need to bother with setting nano 
as the editor with git config.


[1] 
http://lilypond.org/doc/v2.19/Documentation/contributor/setting-up#configuring-git


LilyDev uses the $EDITOR variable


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

Re: Allure and git-cl troubleshooting

[Paul Morris]

> On Oct 25, 2015, at 4:13 PM, Federico Bruni  wrote:
> 
> Il giorno dom 25 ott 2015 alle 20:48, Paul Morris  ha 
> scritto:
>> urllib2.URLError: > certificate verify failed (_ssl.c:581)>
> 
> Installing the package ca-certificates should fix it (I added it to LilyDev 
> after generating the ISO you are using...).

Thanks Federico.  I did that, tried it again, and got a different error:

Upload server: codereview.appspot.com (change with -s/--server)
Email (login for uploading to codereview.appspot.com) [paulwmor...@gmail.com]:
paulwmor...@gmail.com
Password for paulwmor...@gmail.com:
Traceback (most recent call last):
 File "/home/paul/git-cl/git-cl", line 629, in 
   sys.exit(main(sys.argv))
 File "/home/paul/git-cl/git-cl", line 623, in main
   return func(argv[2:])
 File "/home/paul/git-cl/git-cl", line 334, in CmdUpload
   issue, patchset = upload.RealMain(['upload'] + upload_args + args)
 File "/home/paul/git-cl/upload.py", line 2342, in RealMain
   response_body = rpc_server.Send("/upload", body, content_type=ctype)
 File "/home/paul/git-cl/upload.py", line 383, in Send
   self._Authenticate()
 File "/home/paul/git-cl/upload.py", line 428, in _Authenticate
   super(HttpRpcServer, self)._Authenticate()
 File "/home/paul/git-cl/upload.py", line 318, in _Authenticate
   auth_token = self._GetAuthToken(credentials[0], credentials[1])
 File "/home/paul/git-cl/upload.py", line 262, in _GetAuthToken
   response = self.opener.open(req)
 File "/usr/lib/python2.7/urllib2.py", line 437, in open
   response = meth(req, response)
 File "/usr/lib/python2.7/urllib2.py", line 550, in http_response
   'http', request, response, code, msg, hdrs)
 File "/usr/lib/python2.7/urllib2.py", line 475, in error
   return self._call_chain(*args)
 File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
   result = func(*args)
 File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
   raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found




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

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

Paul Morris wrote Sunday, October 25, 2015 7:48 PM

> Below is an error I got trying to upload with git-cl, the new Allura version 
> that’s in LilyDev4.  I followed James and Phil’s recent email exchange about 
> how to do config with Allura server url, source forge account, bearer token, 
> etc.  
> 
> Any ideas on why it’s not working?  Do I need to be an authorized user on the 
> Allura tracker, perhaps?

Maybe not the cause of this particular problem, but only authenticated 
developers are permitted to edit tickets, which is what git-cl needs to do.  
Anyone submitting a patch is de facto a developer, so all you need to do is 
Join (see the Join button top right on the Issues page) the TestLilyIssues 
project and announce on the devel list what username you have chosen and we'll 
authorise you as a Developer.

Trevor

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

Re: Allure and git-cl troubleshooting

[Paul Morris]

> On Oct 25, 2015, at 4:32 PM, Trevor Daniels  wrote:
> 
> Maybe not the cause of this particular problem, but only authenticated 
> developers are permitted to edit tickets, which is what git-cl needs to do.  
> Anyone submitting a patch is de facto a developer, so all you need to do is 
> Join (see the Join button top right on the Issues page) the TestLilyIssues 
> project and announce on the devel list what username you have chosen and 
> we'll authorise you as a Developer.

Ok, my username on sourceforge is paulwmorris.

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

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

Paul, you wrote Sunday, October 25, 2015 8:45 PM


>> On Oct 25, 2015, at 4:32 PM, Trevor Daniels  wrote:
>> 
>> Maybe not the cause of this particular problem, but only authenticated 
>> developers are permitted to edit tickets, which is what git-cl needs to do.  
>> Anyone submitting a patch is de facto a developer, so all you need to do is 
>> Join (see the Join button top right on the Issues page) the TestLilyIssues 
>> project and announce on the devel list what username you have chosen and 
>> we'll authorise you as a Developer.
> 
> Ok, my username on sourceforge is paulwmorris.

Thanks Paul - should be good to go now.

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

Allure and git-cl troubleshooting

[Paul Morris]

Greetings devs,

Below is an error I got trying to upload with git-cl, the new Allura version 
that’s in LilyDev4.  I followed James and Phil’s recent email exchange about 
how to do config with Allura server url, source forge account, bearer token, 
etc.  

Any ideas on why it’s not working?  Do I need to be an authorized user on the 
Allura tracker, perhaps?

-Paul


[lilypond-git (whiteout-style)]$ git cl upload origin/master
 Documentation/changes.tely | 
40 
 Documentation/fr/notation/rhythms.itely|  
2 +-
 Documentation/notation/rhythms.itely   |  
2 +-
 Documentation/snippets/blanking-staff-lines-using-the--whiteout-command.ly |  
8 
 Documentation/snippets/new/using-the-whiteout-property.ly  |  
6 +++---
 Documentation/snippets/using-the-whiteout-property.ly  |  
4 ++--
 input/regression/markup-syntax.ly  |  
3 +--
 input/regression/whiteout-lower-layers.ly  | 
10 +-
 input/regression/whiteout.ly   | 
20 
 lily/grob.cc   | 
16 +++-
 lily/lily-imports.cc   |  
1 -
 python/convertrules.py |  
7 +++
 scm/define-grob-properties.scm | 
18 --
 scm/define-grobs.scm   |  
2 +-
 scm/define-markup-commands.scm | 
42 +-
 scm/stencil.scm| 
24 
 16 files changed, 113 insertions(+), 92 deletions(-)
Upload server: codereview.appspot.com (change with -s/--server)
Email (login for uploading to codereview.appspot.com) [paulwmor...@gmail.com]: 
paulwmor...@gmail.com
Password for paulwmor...@gmail.com: 
Traceback (most recent call last):
  File "/home/paul/git-cl/git-cl", line 629, in 
sys.exit(main(sys.argv))
  File "/home/paul/git-cl/git-cl", line 623, in main
return func(argv[2:])
  File "/home/paul/git-cl/git-cl", line 334, in CmdUpload
issue, patchset = upload.RealMain(['upload'] + upload_args + args)
  File "/home/paul/git-cl/upload.py", line 2342, in RealMain
response_body = rpc_server.Send("/upload", body, content_type=ctype)
  File "/home/paul/git-cl/upload.py", line 383, in Send
self._Authenticate()
  File "/home/paul/git-cl/upload.py", line 428, in _Authenticate
super(HttpRpcServer, self)._Authenticate()
  File "/home/paul/git-cl/upload.py", line 318, in _Authenticate
auth_token = self._GetAuthToken(credentials[0], credentials[1])
  File "/home/paul/git-cl/upload.py", line 262, in _GetAuthToken
response = self.opener.open(req)
  File "/usr/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
  File "/usr/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
  File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 1240, in https_open
context=self._context)
  File "/usr/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)
urllib2.URLError: 


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

Issue 4504 whiteout-style

[Paul Morris]

Greetings LilyPond devs,

I’m attaching patches for review for issue 4504 – implementing the 
whiteout-style approach instead of separate whiteout and whiteout-box commands. 
 

I tried to upload to Rietveld using Phil's new git-cl (from Federico's new 
LilyDev4) but so far no luck.  So I thought I’d go ahead and email it, if only 
for my own sense of having reached some milestone.  I’ll send a separate 
message about the git-cl error.

-Paul


Includes commits:

Issue 4504/6 update changes.tely

Issue 4504/5 edits to docs

Issue 4504/4 edits to tests

Issue 4504/3 run scripts/auxiliar/update-with-convert-ly.sh

Issue 4504/2 convert-ly rule: whiteout-box --> whiteout

Issue 4504/1 whiteout-box --> whiteout-style

Introduce whiteout-style, with options of
'box and 'outline, as a grob property to be
used with the whiteout grob property, and as
an optional property of the whiteout markup
command.

Remove the whiteout-box grob property and
markup command, and use whiteout-style
instead.

Make the box style of whiteout the default
style again, as it was before issue 4418.




0001-Issue-4504-1-whiteout-box-whiteout-style.patch
Description: Binary data



0002-Issue-4504-2-convert-ly-rule-whiteout-box-whiteout.patch
Description: Binary data



0003-Issue-4504-3-run-scripts-auxiliar-update-with-conver.patch
Description: Binary data



0004-Issue-4504-4-edits-to-tests.patch
Description: Binary data



0005-Issue-4504-5-edits-to-docs.patch
Description: Binary data



0006-Issue-4504-6-update-changes.tely.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel