Am 28.04.2015 um 13:38 schrieb Werner LEMBERG:
Patch counted down - please push
https://codereview.appspot.com/232850043/
I don't have git account.
David, please change that :-)
Werner
IIRC one has to go to the Savannah page and request to be included in
the project. This request w
Am 28.04.2015 um 16:31 schrieb David Kastrup:
pkx1...@gmail.com writes:
author Masamichi Hosoda
Tue, 28 Apr 2015 13:29:52 + (14:29 +0100)
committer James Lowe
Tue, 28 Apr 2015 14:02:06 + (15:02 +0100)
commit 8dd74d9902782edbd3a1f0dddcaeca29759b7be1
Am 04.05.2015 um 00:15 schrieb David Kastrup:
CG 3.3.4 git-cl configuration
>add how to set the EDITOR variable for git cl, namely:
>export EDITOR=/usr/bin/nano
Nano does not offer point-and-click in connection with LilyPond I think.
I don't think so either. But I don't see why that should
Sorry if this raises old stuff again.
For me many of your requirwments could be rather easily (and partially
automatically ) be handled with an integrated system of code, review and
issues, i.e. a system that provides something like pull requests.
In addition to many of your list items this woul
Am 06.05.2015 um 07:34 schrieb Federico Bruni:
2015-05-06 7:19 GMT+02:00 Janek Warchoł :
as I've already mentioned, I've already started working on a new
LilyDev. I'm going to use tools that should make it easy to build
different versions of LilyDev (e.g. 32-bit and 64-bit, possibly also
bas
Am 07.05.2015 um 13:06 schrieb David Kastrup:
Phil Holmes writes:
I've just started working again on some mensural music with associated
modern transcription. The ancient score is about 8 pages long. With
2.18.2 one of the pieces takes 97 seconds to compile. With 2.19.19 it
takes 37 secon
Am 25. Mai 2015 15:18:46 MESZ, schrieb David Kastrup :
>pat...@gnu.org writes:
>
>> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
> 2df342bbb164aeb3de0ec17304de90d178f1fd52
>> 12:38:18 test-master-lock and PID entry exist but previous Patchy
>> run (PID 10274) died, resetting te
I do run Gitlab but can't give any serious feedback. It's like Github, but we
had some limitations with assignment of pull request IIRC.
In all it's maybe not extensive enough for LilyPond, but maybe it can be
integrated with other tools. For example there's gitlab-ci that can be
integrated.
Hi David (hm, it's a bit unfortunate that you're both called David ...),
it's great to see some work going on in this field. David K's report is
an interesting update, and one can see you are already "into" it.
I can't really judge your example/question because it's over my head wrt
the diffe
Am 17.06.2015 um 10:19 schrieb Werner LEMBERG:
>
>> I take the point about not being greedy, but I wonder if we want to
>> retain an option to compile Allura from source.
>
> This is even the preferred installation way, right? However, 1GB of
> RAM should be fully sufficient for compilation, I
Am 01.07.2015 um 04:02 schrieb Andrew Levine:
> Hello -- I recently made a novel use of Lilypond by using Javascript to
> place English letters underneath notes in the SVG output, and allowing the
> user to play the song in an online game called Piano Typewriter. Is there
> any lists I can send t
Am 30.06.2015 um 21:04 schrieb Walter:
> Hi,
>
> I have been using OOoLilypond with Libreoffice for quite some time. I have
> tested the extension with LibreofficeDev 5.0 and the following error showed
> up: "com.star.comp.Writer.TextDocument: document type not supported by
> OOoLilypond" (Syste
Am 11. Juli 2015 09:23:44 MESZ, schrieb Federico Bruni :
>Il giorno ven 10 lug 2015 alle 20:49, Paul Morris
> ha scritto:
>> My thinking is that it would be good to move some or all of the
>> examples page[1] to the main column of the home page where the news
>> is now. That clearly shows wha
he documentation? Just compare
http://lilypond.org to
http://lilypond.org/doc/v2.18/Documentation/web/index.html
and the respective paths in the build directory.
Am 18.07.2015 um 23:35 schrieb David Kastrup:
> Federico Bruni writes:
>
>> Il giorno sab 18 lug 2015 alle 20:42, David Kastru
Am 19.07.2015 um 07:26 schrieb Werner LEMBERG:
> As a preliminary I want to mention that in general I can imagine that
> we separate the top-level entry page of lilypond.org from the texinfo
> system. Somewhere we could have a `doc' subdirectory, and from there
> on everything is generated with
Am 12.08.2015 um 16:18 schrieb tisimst:
> I just thought I'd ask since your message implies it, but do you still
> plan on following the "dev" list?
This is a question that came to my mind also, but maybe it should better
be posted on the -dev list ;-)
Urs
_
I've written something that removes duplicate markups (resulting from
partcombine). Maybe that's interesting for you?
I can't look it up without computer but you could try locating it at
git.openlilylib.org
-> das trunkne lied
-> code (files?)
-> library/ly/something
HTH
Urs
Am 22. August 201
Am 2. September 2015 07:30:09 MESZ, schrieb Federico Bruni :
>Hi folks
>
>I know that a lot of time has been invested on Allura, especially by
>Trevor.
>So I feel uneasy in writing this email, but I have the feeling that the
>
>time
>costraint didn't help to make the best decision for the new is
Am 09.09.2015 um 15:56 schrieb Simon Albrecht:
> Hello,
>
> Trevor has already introduced a warning to use delimiting for .ly
> code blocks. Now I noticed that Allura imposes some code highlighting
> by default, and pygments (the tool used) doesn’t make a good guess on
> the language. Unfort
Am 08.10.2015 um 11:32 schrieb Werner LEMBERG:
> I was quite impressed seeing the following video.
>
> https://www.facebook.com/verge/videos/975966512439692/
Indeed. I just forgot sharing that link here too ...
>
> If writing music like this *really* works, I could imagine that even I
> would
Am 16.10.2015 um 08:40 schrieb Federico Bruni:
> yes, try:
>
> lilypond -dpreview -dbackend=svg test.ly
>
But doesn't this output the first system only?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lily
Dear developers,
most of you will know or at least have noticed that I have thought about
integrating LilyPond and the XML based MEI format. If not you might
consider reading my current post on http://lilypondblog.org for an
introduction. Today I would like to make kind of an announcement and
call
Am 19.10.2015 um 18:36 schrieb David Kastrup:
> Urs Liska writes:
>
>> I think this is a huge opportunity to bring LilyPond forward. First
>> this will bring us a whole new range of users and use cases, maybe
>> even to a point where a general audience will take no
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. Apart
Am 24. Oktober 2015 10:05:55 MESZ, schrieb Richard Shann
:
>On Sat, 2015-10-24 at 01:39 +0200, Simon Albrecht wrote:
>> 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
other typesetting software) in such a complete and definite way.
>
> _______
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
--
Urs Liska
www.openlilylib.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
t;> please tell me what you think. We should have good arguments in order
>> not to slip through the net ...
>>
>> Best
>> Urs
>>
>> ___
>> lilypond-devel mailing list
>> lilypond-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
--
Urs Liska
www.openlilylib.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
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 w
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
Am 28. Oktober 2015 22:14:21 MEZ, schrieb Simon Albrecht
:
>Hello David,
>
>On 28.10.2015 22:05, David Sankel wrote:
>> Would anyone object to a patch where I add a
>> '-dpreview-include-all-systems' option to lilypond?
>
>Generally I’d say that patches are welcome, but certainly it makes
>sense
Welcome to LilyPond and this list, John,
Am 10.11.2015 um 16:36 schrieb John Gourlay:
> I’m an aspiring LilyPond contributor who needs a mentor. How can I get one?
I'm not sure you can "get one" here because there are simply too few
developers around.
But if you continue asking questions on this
Am 10.11.2015 um 21:47 schrieb John Gourlay:
> Mike,
>
> Yes, I am the spacing-a-line-of-music John Gourlay, pleased that my early
> contributions have turned out to be useful. I’ve been out of the loop for
> about 30 years, however, so it won’t happen that I’ll be doing any mentoring
> myself
Hi devs,
do I read the docs right in that additional include paths *have* to be
specified on the command line, with one or multiple --include options?
Has noone asked until now for being able to have LilyPond look for an
environment variable to add include paths?
I think many users will have thei
ht?), select the Oauth tab and create
> your own 'Bearer token' - it should be obvious how to do that. Then you
> can use that value as the final entry for your git-cl config when it
> asks you for it.
>
> Now it should all work,
>
> James
>
>
>
>
>
> Th
That was the first thing I did when things didn't work ...
Urs
>
> Trevor
>
> - Original Message -
> From: "Trevor Daniels"
> To: "Urs Liska"
> Cc: "Lily-Devel List"
> Sent: Thursday, November 19, 2015 3:18 PM
> Subject: Re:
it
> asks you for it.
>
> Now it should all work,
>
> James
>
>
>
>
>
> The Allura Server URL is
>
> On 19/11/15 13:57, Urs Liska wrote:
>> I've implemented a fix for this (hey, my first working C++ patch :-) )
>> but now I'm stumbling
Am 20.11.2015 um 00:57 schrieb Trevor Daniels:
> Urs Liska wrote Thursday, November 19, 2015 11:20 PM
>
>> However, I have a question: Where are the CLI messages defined that are
>> used in the git-cl process? This is still talking about Google issue
>> tracker items.
>
Am 20.11.2015 um 10:38 schrieb Phil Holmes:
> - Original Message - From: "Urs Liska"
> To: "Trevor Daniels" ; "James" ;
> "Phil Holmes"
> Cc: "lilypond-devel"
> Sent: Thursday, November 19, 2015 11:59 PM
> Subjec
Is this correct in the new tracker:
Update status and label but leave the issue open?
I assume it will be closed after being veified?
Urs
Ursprüngliche Nachricht
Von: Urs Liska
Gesendet: 25. November 2015 13:58:02 MEZ
An: "[testlilyissues:issues]
Am 28. November 2015 17:27:01 MEZ, schrieb Phil Holmes :
>- Original Message -
>From: "Kieren MacMillan"
>To: "Phil Holmes"
>Cc: "Lilypond-User Mailing List" ;
>"lilypond-devel"
>
>Sent: Saturday, November 28, 2015 4:08 PM
>Subject: Re: improving ottavation
>
>
>Hi Phil,
>
>Thanks for
Am 15.12.2015 um 09:06 schrieb James:
> Ticket created at:
> https://sourceforge.net/rest/p/testlilyissues/issues/4698/
http://sourceforge.net/p/testlilyissues/issues/4698/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/ma
Hi,
I just looked again at my attempts to get beam subdivision on the right
track. Unfortunately I need some help understanding
Beaming_pattern::beamify in beaming-pattern.cc.
If I'm not mistaken the calculation of the beam count iterates over the
infos_ struct, whose members contain information
Am 18.12.2015 um 17:49 schrieb Urs Liska:
> I have
> infos_[i].start_moment_
> to determine the moment of the *current* beam
Oops, that should of course read "the current *stem*"
___
lilypond-devel mailing list
lilypond-
Am 18.12.2015 um 18:35 schrieb Carl Sorensen:
>
> On 12/18/15 9:49 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Urs Liska" behalf of u...@openlilylib.org> wrote:
>
>
>> If I could either retrieve the start_moment of the note *after* the
The editor that is opened depends on the EDITOR environment variable so you can
use whatever you want.
HTH
Urs
Am 21. Dezember 2015 20:14:57 MEZ, schrieb Simon Albrecht
:
>Hello,
>
>after a long time I’ve now tried and uploaded a patch again. Two
>questions on the git cl process:
>What exact v
Hi all,
for a patch I'm currently finishing I have to update the documentation,
concretely one of the "selected snippets".
I'm not sure where I have to do that. Is that something I should do in
Documentation/snippets or should that be done in the LSR?
TIA
Urs
Am 21.12.2015 um 22:19 schrieb Urs Liska:
> Hi all,
>
> for a patch I'm currently finishing I have to update the documentation,
> concretely one of the "selected snippets".
> I'm not sure where I have to do that. Is that something I should do in
> Documentat
Just used the current git-cl for the first time and noticed a *minor*
glitch.
This link in the console output:
Ticket created at:
https://sourceforge.net/rest/p/testlilyissues/issues/4704/
points to the raw (JSON?) data. In order to provide a useful clickable
link the "rest/" should be removed
Am 22.12.2015 um 20:51 schrieb Carl Sorensen:
> Copy the snippet to Documentation/snippets/new.
>
> Remove the machine-generated header.
>
> Make your changes.
>
> Submit the patch.
OK, that is more or less what I did (in patch set 2).
The only thing that is left for me to update is *not* to inc
Am 23.12.2015 um 10:06 schrieb d...@gnu.org:
> On 2015/12/23 07:59:26, git wrote:
>> Revert changes to snippets file
>
> At the current point of time, you only added
> Documentation/snippets/new/xxx.ly while keeping
> Documentation/snippets/xxx.ly unchanged. That's the right organisation
> for a
28 Dec 2015 15:15:43 +
Von:Urs Liska
Antwort an: [testlilyissues:issues]
<4...@issues.testlilyissues.p.re.sf.net>
An: [testlilyissues:issues] <4...@issues.testlilyissues.p.re.sf.net>
* *labels*: --> Fixed_2_19_35
* *status*: Started --> Fixed
* *Comment*:
P
Am 28.12.2015 um 16:33 schrieb David Kastrup:
> Urs Liska writes:
>
>> Hi all,
>>
>> I've just pushed my patch for #4704, having reworked the branch to five
>> discrete commits (removing detours but separating work on different
>> files/tasks).
>&
Am 13.01.2016 um 13:55 schrieb Menu Jacques:
> Hello folks,
>
> ‘sortly’ instead of ‘shortly’.
Well, I think this is more a conceptual conflict than a typo :-/
>
> JM
>
> --
>
> 14.7 Grand LilyPond Input Syntax Standardization (GLISS)
>
> Summary
>
> • Start: sortly after 2.14 comes out,
Am 14.01.2016 um 16:34 schrieb Simon Albrecht:
> On 14.01.2016 16:20, d...@gnu.org wrote:
>> The name is rather clumsy (and it does not help that the issue report
>> talks about "\RemoveEmptyStavesFirst" while the actual patch and the
>> Rietveld review has "\RemoveEmptyStavesAll").
>
> That’s al
I have created a new boolean context property by
- adding an entry in define-context-properties.scm
- setting the default in engraver-init.ly
- retrieving it in a class's (Beaming_option) from_context method
However, I would like to add another context property (and modify the
added one) from bool
Am 18.01.2016 um 13:43 schrieb g...@ursliska.de:
> This is a great enhancement.
>
> I commented on one typo, but I saw two issues (I'll add images to the
> lilypond-devel copy of this message as soon as it pops up):
>
> 1)
> In one file the instrument name was severely truncated
(BeiMannern ...
Am 18.01.2016 um 11:31 schrieb Urs Liska:
> And how do I retrieve the value of the property in a C++ class?
> I see this in bar-number-engraver.cc:
>
> SCM alternative_style = get_property
> ("alternativeNumberingStyle");
> string text_tag = &
Am 18.01.2016 um 16:17 schrieb Paul Morris:
>> On Jan 18, 2016, at 7:43 AM, g...@ursliska.de wrote:
>>
>> This is a great enhancement.
> Thanks Urs.
>
>> I commented on one typo, but I saw two issues (I'll add images to the
>> lilypond-devel copy of this message as soon as it pops up):
>>
>> 1)
>
Am 18.01.2016 um 16:35 schrieb Urs Liska:
>>> 2)
>>> >> In another file with three staves (staff + piano staff) the vertical
>>> >> spacing of the systems is unusably large.
>> > How do these compare with ly:one-line-breaking ? (I might try
Am 18.01.2016 um 11:31 schrieb Urs Liska:
> I have created a new boolean context property by
> - adding an entry in define-context-properties.scm
> - setting the default in engraver-init.ly
> - retrieving it in a class's (Beaming_option) from_context method
>
> Howev
Hi devs,
please consider
#(if (ly:get-option 'point-and-click)
(let ((point-and-click (ly:get-option 'point-and-click)))
(display point-and-click)))
Can this ever print anything else than #t ?
As far as I can see
(ly:get-option 'point-and-click)
can return either #t or #f, is t
Starting the next round somewhat earlier ...
Surprisingly there also will be a Google Summer of Code 2016, and I
think we should be better prepared this time and not miss a slot due to
lack of students.
Mentoring organizations apply between 8-19 February, students 14-25 March.
IIRC in our case th
LGTM.
There's the question about the mentors themselves. There are people on this
list who don't seem to be around anymore.
But we should deal with the *content* in a separate patch.
Urs
Am 24. Januar 2016 02:45:07 MEZ, schrieb paulwmor...@gmail.com:
>Please review. Thanks, -Paul
>
>https://c
Hi all,
now that is-absolute? is not broken anymore (see #4746 and #4747) I'd
like to raise the question of its *behaviour* - which seems somewhat
inconsistent to me.
Currently this function behaves differently on Windows and elsewhere,
and I think this shouldn't be the case.
is-absolute? expect
Am 25.01.2016 um 10:07 schrieb David Kastrup:
> Urs Liska writes:
>
>> Hi all,
>>
>> now that is-absolute? is not broken anymore (see #4746 and #4747) I'd
>> like to raise the question of its *behaviour* - which seems somewhat
>> inconsistent to
e.
I think this should be a project that can be handled successfully in a
GSoC project (and most of it is *not* an all-or-nothing endeavour), and
I would be willing to mentor it.
Urs
Am 21.01.2016 um 17:02 schrieb Urs Liska:
> Starting the next round somewhat earlier ...
>
> Surprisingly t
Am 26.01.2016 um 10:21 schrieb David Kastrup:
> Urs Liska writes:
>
>> Would it be an acceptable/interesting project to bring the ScholarLY
>> library to a finished state and (optionally) integrate it with
>> LilyPond?
> Personally I don't think "integr
Am 25.01.2016 um 11:55 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 25.01.2016 um 10:07 schrieb David Kastrup:
>>
>>> What actual problem are you trying to address here?
>> LilyPond will consider "C:\\some\\path" an absolute path when compiled
&g
Am 26.01.2016 um 17:45 schrieb Trevor Daniels:
> Simon Albrecht wrote Monday, January 25, 2016 8:03 PM
>
>> How should I (and James) interpret the silence here? Any more opinions?
> If a user has requested additional characters which have an html character
> (non-numeric) definition and a devel
Am 27. Januar 2016 05:34:46 MEZ, schrieb paulwmor...@gmail.com:
>Now that ly:one-line-auto-height is in master, this patch set updates
>the docs so it and ly:one-page-breaking are both present and accounted
>for. -Paul
LGTM
>
>
>https://codereview.appspot.com/288910043/diff/1/Documentation/not
Am 27. Januar 2016 02:37:17 MEZ, schrieb Paul Morris :
>> On Jan 26, 2016, at 5:24 AM, David Kastrup wrote:
>>
>>> So my question could be rephrased: Would it be acceptable to suggest
>a
>>> GSoC project if such an external library is *not* going to be
>included
>>> in LilyPond directly? With r
I forgot to mention that I asked those currently listed as mentors. I'll report
when all have responded.
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://list
Am 27.01.2016 um 21:02 schrieb Paul Morris:
> So students can find us as one of the GNU projects, we should get LilyPond
> listed on the GNU GSoC suggestions page. Here’s the one for last summer:
> http://www.gnu.org/software/soc-projects/ideas-2015.html
>
> Seems we should just have a listin
ent could get started on step
5, but I wouldn't expect it from a novice. Of course, during the
bonding period I might change my expectations.
"
Am 21.01.2016 um 17:02 schrieb Urs Liska:
> Starting the next round somewhat earlier ...
>
> Surprisingly there also will be a Goo
Hi developers,
this is pretty urgent, and I start a new thread for all those who may
not have followed up on
http://lists.gnu.org/archive/html/lilypond-devel/2016-01/msg00139.html.
We want to review our suggestions for Google Summer of Code projects.
But it seems although the projects listed on h
d and Guile 2.0 interoperability? Like with mentors
> from both
> projects. I assume that would be too difficult a task at this point, at
> least I think
> that was the thinking last year.
>
Would be great to have ...
Urs
>
--
Urs Liska
www.openlilylib.org
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 03.02.2016 um 12:14 schrieb Federico Bruni:
> Hi Urs
>
> I jump in late to ask if the transition to texi2any might be added to
> the list.
> It might not be a sexy project but it's very needed and we all know
> how much the documentation is important for LilyPond.
>
> If Graham confirms his av
Hi Paul,
Am 27.01.2016 um 02:37 schrieb Paul Morris:
> While we’re at it, one thing I’ve thought about is simplifying vertical
> spacing changes. Basically something like this[1] but possibly integrated
> into LilyPond. One idea is that alongside padding, minimum-distance, and
> basic-distanc
Am 8. Februar 2016 15:35:33 MEZ, schrieb paulwmor...@gmail.com:
.
>
>> Hm, my intention was to draw the attention to the fact that this
>project relates
>> to actual engraving quality. But I've taken your suggestion.
>
>Hmm... that's a good idea. Maybe add this to the title? "Improve
>engraving
Am 12. Februar 2016 12:41:30 MEZ, schrieb James :
>Hello,
>
>Here is the current patch countdown list. The next countdown will be on
>February 15th.
>
...
>
>
>4763 Web: Review GSoC page - Urs Liska
>https://sourceforge.net/p/testlilyissues/issues/4763
>http://co
Am 13.02.2016 um 14:16 schrieb James Lowe:
> Urs,
>
> On 12/02/16 11:47, Urs Liska wrote:
>>
>> Am 12. Februar 2016 12:41:30 MEZ, schrieb James :
>>> Hello,
>>>
>>> Here is the current patch countdown list. The next countdown will be on
>>&
Am 17.02.2016 um 17:47 schrieb Simon Albrecht:
>> Waiting for a patch like that to pass before review is pointless if
>> there is going to be a reluctance or even refusal to allow it to make
>> it to master in the end.
>>
>> However, is there a particular reason for this question?
>
> No, just a
I know this has been discussed in various flavors over the years, but I
need to raise the issue once more. Please note that this actually
encloses two questions.
Would it be possible to make LilyPond work in a server mode where the
whole Guile environment is loaded only once and the running server
I'm sorry but I don't get this.
Urs
Am 17.02.2016 um 22:48 schrieb Abraham Lee:
> This sounds a lot like lilybin.com <http://lilybin.com>...
>
> - Abraham
>
> On Wed, Feb 17, 2016 at 2:45 PM, Urs Liska <mailto:u...@openlilylib.org>> wrote:
>
>
Hi David,
nice to read that.
I think coming to GSoC with an idea is more important than the listed mentor
availability. Continuing on the Scheme/XML track would be very rewarding.
However, for some reasons I'd try to go into a more generic direction. This
could be very suitable for integratio
Am 18.02.2016 um 09:44 schrieb James Lowe:
> I hope this isn't off-topic but could we get together with the
> Philomelos people?
>
> https://github.com/Philomelos/lilypond-musicxml2ly-dev
>
> I am not sure of the motivation to fork, but if it was just because no
> one was working on MusicXML and
Hi all,
now that our modified GSoC page is online we should think about
spreading the word.
Of course the mentoring project applications are not done yet, but I
think we should act as if it were clear that we can offer that project.
So, as the student application window starts March 14th I think w
Hi David,
thank you for your explanation, which is the base for a (presumably more
complicated) follow-up question.
Am 17.02.2016 um 23:31 schrieb David Kastrup:
> Urs Liska writes:
>
>> I know this has been discussed in various flavors over the years, but I
>> need to raise t
Am 22.02.2016 um 12:27 schrieb David Kastrup:
> Urs Liska writes:
>
>> So, let's assume we already had implemented a server daemon mode for
>> LilyPond.
>> Would it be possible to make that daemon keep a representation of the
>> *parsed* document in m
Hi Sharon,
Am 22.02.2016 um 20:22 schrieb Sharon Rosner:
>> I worked on a large score with about 100 A3 pages with 13 point staff
>> size (~ 50 minutes of huge orchestra).
>>
>> Compiling the full score using manual breaks took around 7 minutes, with
>> the console output seemingly indicating the
Hi Abraham,
Am 23.02.2016 um 13:56 schrieb Abraham Lee:
> Dear Dev team,
>
> ...
>
> I'm not sure what prompted
> Han-wen or Jan or whoever to set a default value to it, but I wonder if
> it's time for it to go?
>
> Just some thoughts. I love the quality of LP scores. Removing the default
> taglin
Hello Nathan,
welcome to the lilypond-devel list. I hope we'll find a way for you to
join us sustainably :-)
Your post is not fully clear, though (at least to me), as I think it
gives too little information to estimate your experience (combined with
the willingness to learn).
If you want to go f
Am 02.03.2016 um 23:52 schrieb Simon Albrecht:
> Hello,
>
> I noticed that there have been many ‘Issues to verify’ around, so I
> started to catch up with these. Now the question is: Shouldn’t we only
> mark issues as verified, when the change is already included in an
> official release?
> For c
Hi Jeffery,
Am 03.03.2016 um 06:03 schrieb jeffery shivers:
> Dear LilyPond team,
>
> I'd like to apply for GSoC to contribute to ScholarLY as
> a student with Urs Liska.
This is great news!
>
> I've been a user of LilyPond and LaTeX for a while now,
> an
Am 07.03.2016 um 05:48 schrieb Carl Sorensen:
> On 3/6/16 9:33 PM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on
> behalf of Nathan Chou" on behalf of starry...@gmail.com> wrote:
>
> ...
>
>> Also regarding GSoC, currently allowing spanners to cross voices seems to
>> be of most interest
Hi guys,
it seems there's the chance this year that we end up with more GSoC
applications than available slots. Right now there are four people
having expressed interest in it, and my impression so far is that the
majority (or even all) may go the way through to an application.
That raises the qu
Am 07.03.2016 um 09:26 schrieb David Kastrup:
> Urs Liska writes:
>
>> Hi guys,
>>
>> it seems there's the chance this year that we end up with more GSoC
>> applications than available slots. Right now there are four people
>> having expressed interes
Am 07.03.2016 um 09:58 schrieb David Kastrup:
> Urs Liska writes:
>
>> Am 07.03.2016 um 09:26 schrieb David Kastrup:
>>> Urs Liska writes:
>>>
>>>> Hi guys,
>>>>
>>>> it seems there's the chance this year that we end up wit
to tackle
that, but unfortunately only after other things which I don't really
have enough time for either ...
Best
Urs
> Best, Simon
>
> _______
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
--
U
Hi devs,
we have a potential student looking for a GSoC project
(http://lists.gnu.org/archive/html/lilypond-devel/2016-03/msg6.html
and following messages). He has expressed interest in the "Allow
spanners to cross voices" project where I am listed as
potential/secondary mentor. However, I hav
501 - 600 of 754 matches
Mail list logo
