On Sat, Aug 17, 2013 at 12:33:39PM +, julien.ri...@gmail.com wrote:
> I did not touch that part specifically because I do not want to break
> anything with the current machine that runs this build. Is there a
> python2 on the host machine where this command would normally be run?
> AFAIK the py
On Fri, Aug 16, 2013 at 02:32:35PM +0100, Phil Holmes wrote:
> >On Fri, Aug 16, 2013 at 08:53:44AM +, k-ohara5...@oco.net wrote:
> >>I would be tempted to simply insert \bar "|." into the longer examples
> >>in the LM, with no explanation, so it is there for curious people to
> >>find, and show
2013/8/17 :
> On 2013/08/16 08:59:36, Graham Percival wrote:
>> I don't think we need to respond to every single doc suggestion;
>> often users are unaware of the trade-offs we've chosen or are
>> particularly focused on their application domain ("why bother with
>> stuff for singers? the LM shou
2013/8/18 Graham Percival :
> On Fri, Aug 16, 2013 at 02:32:35PM +0100, Phil Holmes wrote:
>> >On Fri, Aug 16, 2013 at 08:53:44AM +, k-ohara5...@oco.net wrote:
>> >>I would be tempted to simply insert \bar "|." into the longer examples
>> >>in the LM, with no explanation, so it is there for cur
LGTM
https://codereview.appspot.com/12945044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM (but i'm not a parser expert)
Sorry for a possibly ignorant question: will this patch also remove the
error in case of
mus = { a }
\mus
?
If not, would there be an easy way to fix that?
Janek
https://codereview.appspot.com/12945043/
___
lilypond
LGTM.
https://codereview.appspot.com/12732043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2013/08/18 10:20:07, janek wrote:
LGTM (but i'm not a parser expert)
I've no clue about the parser, from description:
LGTM
Sorry for a possibly ignorant question: will this patch also remove
the error in
case of
mus = { a }
\mus
?
No.
If not, would there be an easy way to fix that?
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: ; ;
; ; ;
;
Sent: Sunday, August 18, 2013 10:46 AM
Subject: Re: Adds bar line section to LM (Issue 3408) (issue 12724043)
On Fri, Aug 16, 2013 at 02:32:35PM +0100, Phil Holmes wrote:
>On Fri, Aug 16, 2013 at 08:5
still LGTM.
And i found a bug in side-position-interface during testing!
Janek
https://codereview.appspot.com/12844043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
2013/8/18 :
> On 2013/08/18 10:20:07, janek wrote:
>> Sorry for a possibly ignorant question: will this patch also remove
>> the error in case of
>> mus = { a }
>> \mus
>> ?
>
> No.
>
>> If not, would there be an easy way to fix that?
>
> Well, we could delete all functionality of \addlyrics etc
>
LGTM. Nice, clear description!
thanks,
Janek
https://codereview.appspot.com/9426044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi folks,
it's time to start collaborating on LilyPond ties with a bigger group
of people (you don't have to be a programmer to help!) :-)
The most important thing at the moment is to have many people - both
programmers and non-programmers - study the details of the problem and
proposed solution
PS if anyone needs *any* help with git, i'll gladly help!
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
WOW!! I've just found this patch and this is awesome!!
In my eyes, this single patch made LilyPond 2 times more user-friendly.
I think that this is totally worth of an entry in "changes" - i would be
soo sorry if i hadn't found this change by accident today. Would
you like to write one or sh
2013/8/18 Janek Warchoł :
> PS if anyone needs *any* help with git, i'll gladly help!
Hi Janek,
let me take you at your word.
Recently you posted
http://lists.gnu.org/archive/html/lilypond-devel/2013-08/msg00138.html
with the public branch
dev/frax/colorful-make
How do I get this branch?
I.e. w
Hi,
2013/8/18 Thomas Morley :
> 2013/8/18 Janek Warchoł :
>> PS if anyone needs *any* help with git, i'll gladly help!
>
> let me take you at your word.
excellent! I like it when my words are taken seriously :-)
> Recently you posted
> http://lists.gnu.org/archive/html/lilypond-devel/2013-08/ms
- Original Message -
From: "Janek Warchoł"
To: "Thomas Morley"
Cc: "LilyPond Developmet Team"
Sent: Sunday, August 18, 2013 3:24 PM
Subject: working with other git branches (was: Tie Crusade - what to do now)
Hi,
2013/8/18 Thomas Morley :
2013/8/18 Janek Warchoł :
PS if anyone ne
Hi,
2013/8/18 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>>
>> 2013/8/18 Thomas Morley :
>>> Recently you posted
>>> http://lists.gnu.org/archive/html/lilypond-devel/2013-08/msg00138.html
>>> with the public branch
>>> dev/frax/colorful-make
>>>
>>> How do I get this branch
Hi Janek,
2013/8/18 Janek Warchoł :
> Hi,
>
> 2013/8/18 Thomas Morley :
>> 2013/8/18 Janek Warchoł :
>>> PS if anyone needs *any* help with git, i'll gladly help!
>>
>> let me take you at your word.
>
> excellent! I like it when my words are taken seriously :-)
D)
>
>> Recently you posted
>> ht
Hi Harm,
2013/8/18 Thomas Morley :
> Hi Janek,
>
> 2013/8/18 Janek Warchoł :
>> Hi,
>>
>> 2013/8/18 Thomas Morley :
>>> 2013/8/18 Janek Warchoł :
PS if anyone needs *any* help with git, i'll gladly help!
>>>
>>> let me take you at your word.
>>
>> excellent! I like it when my words are taken
2013/8/18 Janek Warchoł :
> Hi Harm,
>
> 2013/8/18 Thomas Morley :
>> Hi Janek,
>>> side-question: what git version do you have? ('git --version')
>> git version 1.7.0.4
>> (from lilydevel)
>
> Ah, ok. Quite old, so i recommend to upgrade (can help you if needed).
Thanks! I think I'll need some
2013/8/18 Thomas Morley :
> 2013/8/18 Janek Warchoł :
>> Hi Harm,
>>
>> 2013/8/18 Thomas Morley :
>>> Hi Janek,
>
side-question: what git version do you have? ('git --version')
>>> git version 1.7.0.4
>>> (from lilydevel)
>>
>> Ah, ok. Quite old, so i recommend to upgrade (can help you if nee
Janek Warchoł writes:
> 2013/8/18 :
>> On 2013/08/18 10:20:07, janek wrote:
>>> Sorry for a possibly ignorant question: will this patch also remove
>>> the error in case of
>>> mus = { a }
>>> \mus
>>> ?
>>
>> No.
>>
>>> If not, would there be an easy way to fix that?
>>
>> Well, we could delete
2013/8/18 David Kastrup :
> It's not entirely clear since you can't write
>
> mus = \addlyrics ...
>
> anyway. The main problem is that \mus differs from #mus in that it
> needs to be evaluated _before_ a token can be handed to the parser.
> This will only change once every \xxx has the same token
Hi,
2013/8/17 Janek Warchoł :
>
> 2013/8/14 Thomas Morley :
>> The right place for them would be the LSR, _if_ the LSR would be able
>> to compile them and not use a LilyPond-version far too old for many of
>> my ideas.
>>
>> There were some insinuations on the list the last months (or was it a
>>
26 matches
Mail list logo
