Hi Jean & everybody,
Am 23.05.22 um 19:33 schrieb Jean Abou Samra:
If you have a core dump, that normally means you encountered a
bug in LilyPond. Having such a crash is quite rare, so it seems
like bad luck if you hit one as a new user
That's what I told Andrea when she asked me (we're at the
Hi,
Again, please keep the list in copy. In your mail client, you
should see lilypond-devel@gnu.org in the To: or CC: field.
You will normally find a "Reply to all" button that you can
use instead of just "Reply" in order to keep all recipients.
That way, everyone can keep helping you, not just m
Le 23/05/2022 à 20:09, Andrea lienbacher a écrit :
Dear Jean!
Thank for your support!:)
Alternatively, you might have tried to process a huuuge score
to the point that your computer couldn't cope anymore. (That
would normally not happen before hundreds of pages, or large
nesting levels.)
I mad
>> Iam a very new user of Lilypond (MacOS). Yesterday i made a new
>> sheet. Suddenly after texting, there was the information “core
>> dump”. Today i tried to see, whats going on. After that, my mac
>> hangs up and react at nothing. So i had to delete Lilypond, bc
>> nothing else worked. Can yo
On 2022-05-23 11:09, Andrea lienbacher wrote:
Hello!
Iam a very new user of Lilypond (MacOS). Yesterday i made a new sheet.
Suddenly after texting, there was the information “core dump”. Today i
tried to see, whats going on. After that, my mac hangs up and react at
nothing. So i had to delete
Guten Morgen Andrea. Ich leite Ihre Frage an die E-Mail-Liste der
Lilypond-Entwickler weiter. Einige der Entwickler sind deutschsprachig
und werden Ihre Frage viel besser beantworten können als ich. Willkommen
bei Lilypond!
Colin
On 2022-05-23 11:09, Andrea lienbacher wrote:
Hello!
Iam a ve
David Kastrup writes:
> lilypond-lfe9kunurqglq9buahr...@public.gmane.org writes:
>
>> Updates:
>> Labels: -Patch-countdown Patch-push
>>
>> Comment #23 on issue 4365 by
>> pkx1...-re5jqeeqqe8avxtiumw...@public.gmane.org: Patch: non-member
>> is_smob<>(), is_derived_smob<>(), etc.
>> https://
lilypond-lfe9kunurqglq9buahr...@public.gmane.org writes:
> Updates:
> Labels: -Patch-countdown Patch-push
>
> Comment #23 on issue 4365 by
> pkx1...-re5jqeeqqe8avxtiumw...@public.gmane.org: Patch: non-member
> is_smob<>(), is_derived_smob<>(), etc.
> https://code.google.com/p/lilypond/issues
Dear Kristof,
Am 2015-04-20 um 11:16 schrieb Kristof Bastiaensen:
I have a hard time to believe that anyone actually uses the part combiner
seriously, but please prove me wrong.
I'm using the partcombiner with all my orchestral scores. For an example
see my edition of Schubert's Stabat Mater
Hi Dan,
It's been a long time I wrote this code, so it may take me some time to
incorporate it
and produce samples. I can do this if there is interest in my
part-combiner.
Those samples wouldn't show the heuristics I used though, for that you'd
have to look into the code comments. I can show a b
> Comment #7 on issue 4345 by kristofbastiaensen: Patch: Part combiner: allow
> a2 chords
> https://code.google.com/p/lilypond/issues/detail?id=4345
>
> I've put up my code on github: https://github.com/kuribas/part-combiner
>
> I honestly don't understand why they kept the broken part combiner…
> Comment #3 on issue 4293 by lemzw...@googlemail.com: Patch: Various
> fixes/improvements in connection with Smob allocation
> https://code.google.com/p/lilypond/issues/detail?id=4293
>
> David, in such cases please proceed immediately!
+1
Trevor
_
On 15/10/14 09:47, lilypond-lfe9kunurqglq9buahr...@public.gmane.org wrote:
> Updates:
> Status: Fixed
> Labels: -Type-Enhancement -Patch-push Type-Maintainability
> Fixed_2_19_16
>
> Comment #13 on issue 4156 by dak-mXXj517/z...@public.gmane.org: Patch:
> Define Smob<> constructors.
> http
Am 01.05.2014 11:24, schrieb James:
On 30/04/14 23:57, Urs Liska wrote:
Would someone please be so kind an push the attached patch?
And/Or maybe someone might consider giving me push access? The email
address to the account(s) is lilyli...@googlemail.com
Best
Urs
done.
James
Thanks.
@Davi
On 30/04/14 23:57, Urs Liska wrote:
Would someone please be so kind an push the attached patch?
And/Or maybe someone might consider giving me push access? The email
address to the account(s) is lilyli...@googlemail.com
Best
Urs
done.
James
___
lil
Would someone please be so kind an push the attached patch?
And/Or maybe someone might consider giving me push access? The email
address to the account(s) is lilyli...@googlemail.com
Best
Urs
Original-Nachricht
Betreff: Re: Issue 3905 in lilypond: Patch: Doc: Clarify grace
2014-04-01 18:05 GMT+02:00 Urs Liska :
> Would please someone push the attached patches?
pushed to staging as
$ git log --oneline -2
b03be2f Issue 3890: Add doc for dodecaphonic-first accidental style
deb20df Issue 3890: Add dodecaphonic-first accidental style
___
Would please someone push the attached patches?
Thanks
Urs
Original-Nachricht
Betreff: Re: Issue 3890 in lilypond: Patch: Add dodecaphonic-first
accidental style
Datum: Tue, 01 Apr 2014 15:31:31 +
Von:lilyp...@googlecode.com
An: lilyli...@googlemail.com
Am 27.01.2014 12:24, schrieb David Kastrup:
Urs Liska writes:
Would somebody please be so kind and push the attached patch?
...
Pushed to staging as
commit 73346163907e09dd0c1e7d6956770379f8bc3971
Author: Urs Liska
Date: Mon Jan 27 11:48:24 2014 +0100
Thanks.
I'm really bad at t
Urs Liska writes:
> Would somebody please be so kind and push the attached patch?
> From: Urs Liska
> Date: Mon, 27 Jan 2014 11:48:24 +0100
> Subject: [PATCH] Issue 3804:Web:Text-input: make LM reff more friendly
Pushed to staging as
commit 73346163907e09dd0c1e7d6956770379f8bc3971
Author: Urs
Would somebody please be so kind and push the attached patch?
Thanks
Urs
Original-Nachricht
Betreff: Re: Issue 3804 in lilypond: Patch: Web: Text-input: make LM
reference more friendly.
Datum: Fri, 24 Jan 2014 13:32:36 +
Von:lilyp...@googlecode.com
An: lilyli
Trevor Daniels wrote
> It seems you're not authorised to change the labels, so I've done it for
> you.
Ok, thanks!
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Lilypond-auto-Issue-3818-in-lilypond-Patch-stencil-scm-addmake-path-
> Comment #3 on issue 3818 by paulwmor...@gmail.com: Patch: stencil.scm: add
> make-path-stencil function
> http://code.google.com/p/lilypond/issues/detail?id=3818
>
> Attempting to change label to "new" to trigger automated tests. I don't
> see any interface for editing labels, just this com
David Kastrup schrieb:
>Urs Liska writes:
>
>> I keep getting these messages although David has pushed the patch.
>How
>> can I (or someone) make the tracker aware of the push?
>
>Usually the state should be updated by the pusher. If you are aware of
>an inconsistency, however, it won't go awa
...@googlemail.com
Betreff: Re: Issue 3719 in lilypond: Patch: CG: Add comment about git-cl editor
Comment #8 on issue 3719 by pkx166h: Patch: CG: Add comment about git-cl
editor
http://code.google.com/p/lilypond/issues/detail?id=3719
Patch counted down - please push
It's because when someone p
Urs Liska writes:
> I keep getting these messages although David has pushed the patch. How
> can I (or someone) make the tracker aware of the push?
Usually the state should be updated by the pusher. If you are aware of
an inconsistency, however, it won't go away by ignoring it.
I find it curio
in lilypond: Patch: CG: Add comment about git-cl editor
Comment #8 on issue 3719 by pkx166h: Patch: CG: Add comment about git-cl
editor
http://code.google.com/p/lilypond/issues/detail?id=3719
Patch counted down - please push
--
You received this message because you are the owner of the issue
find some nodes, but all of
them are unrelated to my patch.
I assume these are just pointers to incomplete translations?
Would someone be so kind to push the two patches?
TIA
Urs
Original-Nachricht
Betreff:Re: Issue 3732 in lilypond: Patch: Website: Rewrite Features
p
James writes:
> On 23/12/13 12:26, Urs Liska wrote:
>> Am 23.12.2013 13:02, schrieb David Kastrup:
>>> Urs Liska writes:
>>>
Am 23.12.2013 12:45, schrieb Urs Liska:
> Attached is an updated patch using @command instead of @code.
> Rebased patch passes make doc (issues in other
On 23/12/13 12:26, Urs Liska wrote:
Am 23.12.2013 13:02, schrieb David Kastrup:
Urs Liska writes:
Am 23.12.2013 12:45, schrieb Urs Liska:
Attached is an updated patch using @command instead of @code.
Rebased patch passes make doc (issues in other subthread solved).
Thanks for pushing
Urs
Urs Liska writes:
> Am 23.12.2013 13:02, schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Am 23.12.2013 12:45, schrieb Urs Liska:
>>>
Attached is an updated patch using @command instead of @code.
Rebased patch passes make doc (issues in other subthread solved).
Thanks for p
Am 23.12.2013 13:02, schrieb David Kastrup:
Urs Liska writes:
Am 23.12.2013 12:45, schrieb Urs Liska:
Attached is an updated patch using @command instead of @code.
Rebased patch passes make doc (issues in other subthread solved).
Thanks for pushing
Urs
Sorry, found an error after reading
Am 22.12.2013 12:06, schrieb David Kastrup:
Urs Liska writes:
Am 22.12.2013 10:54, schrieb David Kastrup:
I see that you used @code{vi} and @code{git-cl} rather than @command{vi}
and @command{git-cl}: any particular reason for that?
I was suggested to use that on Rietveld.
So, no, no parti
Original-Nachricht
Betreff: Re: Fwd: Re: Issue 3719 in lilypond: Patch: CG: Add comment
about git-cl editor
Datum: Sun, 22 Dec 2013 13:13:54 +0100
Von: Urs Liska
An: David Kastrup
Am 22.12.2013 11:59, schrieb Urs Liska:
I don't see that logfile in input/regre
Urs Liska writes:
> Am 22.12.2013 10:54, schrieb David Kastrup:
>
>> I see that you used @code{vi} and @code{git-cl} rather than @command{vi}
>> and @command{git-cl}: any particular reason for that?
>
> I was suggested to use that on Rietveld.
> So, no, no particular reason.
Yes, I know: I'm not
Am 22.12.2013 10:54, schrieb David Kastrup:
Urs Liska writes:
Would somebody please be so kind and push the attached patch.
I rebased on origin/master and ran ct-section source-code.
make doc gave an error, but this pointed to
"fatal error: failed files: "60/lily-338514d2.ly""
so I think I c
Urs Liska writes:
> Would somebody please be so kind and push the attached patch.
>
> I rebased on origin/master and ran ct-section source-code.
>
> make doc gave an error, but this pointed to
> "fatal error: failed files: "60/lily-338514d2.ly""
> so I think I can ignore this?
Actually, you can'
- Original-Nachricht
Betreff: Re: Issue 3719 in lilypond: Patch: CG: Add comment about git-cl
editor
Datum: Sun, 22 Dec 2013 08:20:56 +
Von: lilyp...@googlecode.com
An: lilyli...@googlemail.com
Updates:
Labels: -Patch-countdown Patch-push
Comment #6 on issue 3719 by pkx166h: Patch: CG: A
Am 20.12.2013 11:25, schrieb David Kastrup:
Would you suggest to put such a series in a separate "thread" (by a
>merge no-ff) or not.
Usually not. But some of that might be pulled into a single commit.
>
OK, thanks.
Urs
___
lilypond-devel mailin
Urs Liska writes:
> Am 20.12.2013 11:12, schrieb David Kastrup:
>> As the typical victims for pushers are often able to grant push access,
>> you'll probably not have to go through this very often before they beg
>> you to accept push access.
>
> I think I will do that soon.
> Some time in the pa
Am 20.12.2013 11:12, schrieb David Kastrup:
As the typical victims for pushers are often able to grant push access,
you'll probably not have to go through this very often before they beg
you to accept push access.
I think I will do that soon.
Some time in the past I would have considered it a
Urs Liska writes:
> Am 20.12.2013 10:45, schrieb Trevor Daniels:
>>> 3)
>>> >What to do if my branch contains more than one commit?
>>> >Should I squash them so the patch is one (big) commit? I wouldn't like
>>> >that, for example because I would separate commits that move stuff (e.g.
>>> >to oth
Thanks for the explanations.
Basically everything is like I would have expected, but I think I will
try to add some explanations to CG when I've time.
Urs
Am 20.12.2013 11:00, schrieb David Kastrup:
Urs Liska writes:
Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
Updates:
La
Urs Liska wrote Friday, December 20, 2013 9:48 AM
> Am 20.12.2013 10:45, schrieb Trevor Daniels:
>>> 3)
>>> >What to do if my branch contains more than one commit?
>>> >Should I squash them so the patch is one (big) commit? I wouldn't like
>>> >that, for example because I would separate commits
Urs Liska writes:
> Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
>> Updates:
>> Labels: -Patch-countdown Patch-push
>>
>> Comment #4 on issue 3718 by pkx166h: Patch: Web: Reword contactUsAbout
>> macro
>> http://code.google.com/p/lilypond/issues/detail?id=3718
>>
>> Patch counted do
Am 20.12.2013 10:45, schrieb Trevor Daniels:
Am 19.12.2013 11:32, schrieblilyp...@googlecode.com:
>>Patch counted down - please push
>
>What should I do now?
>The CG says I should "send the patch to my mentor", but obviously this
>isn't applicable.
Create a git format patch, post it on -dev an
Am 20.12.2013 10:45, schrieb Trevor Daniels:
3)
>What to do if my branch contains more than one commit?
>Should I squash them so the patch is one (big) commit? I wouldn't like
>that, for example because I would separate commits that move stuff (e.g.
>to other website nodes) from commits that chan
Urs Liska wrote Friday, December 20, 2013 9:28 AM
> Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
>> Patch counted down - please push
>
> What should I do now?
> The CG says I should "send the patch to my mentor", but obviously this
> isn't applicable.
Create a git format patch, post
Am 19.12.2013 11:32, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-countdown Patch-push
Comment #4 on issue 3718 by pkx166h: Patch: Web: Reword contactUsAbout
macro
http://code.google.com/p/lilypond/issues/detail?id=3718
Patch counted down - please push
What should I do now?
Apparently not posted on the issue itself, so replying to the list.
"m...@mikesolomon.org" writes:
> On 30 mars 2013, at 08:27, lilyp...@googlecode.com wrote:
>> commit 6e4e69f2735a764eab2e6f70f83546461da0203b
>> Author: Mike Solomon
>> Date: Fri Mar 29 05:55:13 2013 +0100
>>
>>Uses sp
On 30 mars 2013, at 08:27, lilyp...@googlecode.com wrote:
> Updates:
> Labels: -Patch-push
>
> Comment #8 on issue 3256 by d...@gnu.org: Patch: Eliminates side poisition
> calculations for system-start-text grobs.
> http://code.google.com/p/lilypond/issues/detail?id=3256
>
> This patch ha
Marc Hohl writes:
> If this erroneous use of reduce cannot be resolved quickly, it would
> be best to raise an issue for this.
I can't even judge if it is erroneous (namely leading to wrong results),
and that's what makes it a problem.
> Well, a do loop in scheme felt kinda weird, but map didn'
Am 16.02.2013 09:29, schrieb David Kastrup:
Marc Hohl writes:
Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com:
Status: Started
Owner: d...@gnu.org
Labels: Type-Enhancement Patch-new
New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme
programming contest
http://code.googl
Marc Hohl writes:
> Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com:
>> Status: Started
>> Owner: d...@gnu.org
>> Labels: Type-Enhancement Patch-new
>>
>> New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme
>> programming contest
>> http://code.google.com/p/lilypond/issues/de
Marc Hohl writes:
> Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com:
>> Status: Started
>> Owner: d...@gnu.org
>> Labels: Type-Enhancement Patch-new
>>
>> New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme
>> programming contest
>> http://code.google.com/p/lilypond/issues/de
2013/2/15 Marc Hohl :
> Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com:
>
>> Status: Started
>> Owner: d...@gnu.org
>> Labels: Type-Enhancement Patch-new
>>
>> New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme
>> programming contest
>> http://code.google.com/p/lilypond/issue
Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com:
Status: Started
Owner: d...@gnu.org
Labels: Type-Enhancement Patch-new
New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme
programming contest
http://code.google.com/p/lilypond/issues/detail?id=3182
Defuse the obfuscated Sc
Am 12.11.2012 10:39, schrieb lilyp...@googlecode.com:
Comment #9 on issue 2948 by d...@gnu.org: Patch: Applies scheme
indentation according to the GNU guidelines
http://code.google.com/p/lilypond/issues/detail?id=2948
Regarding http://codereview.appspot.com/6814080#msg2>: I have
tried lookin
Am 12.11.2012 10:39, schrieb lilyp...@googlecode.com:
Comment #9 on issue 2948 by d...@gnu.org: Patch: Applies scheme
indentation according to the GNU guidelines
http://code.google.com/p/lilypond/issues/detail?id=2948
Regarding http://codereview.appspot.com/6814080#msg2>: I have
tried lookin
Am 29.09.2012 17:01, schrieb lilyp...@googlecode.com:
Comment #1 on issue 2868 by mts...@gmail.com: Patch: Various clean-ups
in stems and beams.
http://code.google.com/p/lilypond/issues/detail?id=2868#c1
Various clean-ups in stems and beams.
*) Eliminates code dups for Kievan work.
*) Transf
Am 24.09.2012 12:55, schrieb David Kastrup:
Marc Hohl writes:
Am 24.09.2012 12:04, schrieb lilyp...@googlecode.com:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2856 by d...@gnu.org: Patch: Get along with use of
grob-property instead of grob-property-path in overrides
Marc Hohl writes:
> Am 24.09.2012 12:04, schrieb lilyp...@googlecode.com:
>> Status: New
>> Owner:
>> Labels: Type-Enhancement Patch-new
>>
>> New issue 2856 by d...@gnu.org: Patch: Get along with use of
>> grob-property instead of grob-property-path in overrides
>> http://code.google.com/p/
Am 24.09.2012 12:04, schrieb lilyp...@googlecode.com:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2856 by d...@gnu.org: Patch: Get along with use of
grob-property instead of grob-property-path in overrides
http://code.google.com/p/lilypond/issues/detail?id=2856
Get al
Jean-Charles Malahieude writes:
> Le 20/09/2012 19:15, Marc Hohl disait :
>> Am 20.09.2012 18:17, schrieb lilyp...@googlecode.com:
>>> [...]
>>>
>>> Oh. \omit is actually even better, isn't it?
>> Yes, I like it!
>>>
>>> I'll likely change that, short of protests. Still, something more
>>> conv
Le 20/09/2012 19:15, Marc Hohl disait :
Am 20.09.2012 18:17, schrieb lilyp...@googlecode.com:
[...]
Oh. \omit is actually even better, isn't it?
Yes, I like it!
I'll likely change that, short of protests. Still, something more
convincing for \single would be nice.
Yes, but I still have no
Werner LEMBERG writes:
>> Still, something more convincing for \single would be nice.
>
> \immediate?
How is \once not immediate? Or actually any override? At least I am
not convinced.
Another thought I had was to punt and not create a separate command, but
just let \tweak itself take an over
> Still, something more convincing for \single would be nice.
\immediate?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Am 20.09.2012 18:17, schrieb lilyp...@googlecode.com:
[...]
Oh. \omit is actually even better, isn't it?
Yes, I like it!
I'll likely change that, short of protests. Still, something more
convincing for \single would be nice.
Yes, but I still have no clue ...
_
On 10 sept. 2012, at 11:12, lilyp...@googlecode.com wrote:
> Updates:
> Status: Started
>
> Comment #32 on issue 2801 by d...@gnu.org: Patch: Approximates cross-staff
> slurs in VerticalAxisGroup vertical-skylines.
> http://code.google.com/p/lilypond/issues/detail?id=2801
>
> Mike, I jus
Am 06.09.2012 08:59, schrieb lilyp...@googlecode.com:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2813 by mts...@gmail.com: Patch: Allows user to set
ChordName text
http://code.google.com/p/lilypond/issues/detail?id=2813
Allows user to set ChordName text
http://coder
Am 31.08.2012 11:58, schrieb John Mandereau:
Il giorno gio, 30/08/2012 alle 09.29 +0200, Marc Hohl ha scritto:
Am 30.08.2012 06:46, schrieb lilyp...@googlecode.com:
Comment #6 on issue 2790 by grenoui...@lilynet.net: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/de
Il giorno gio, 30/08/2012 alle 09.29 +0200, Marc Hohl ha scritto:
> Am 30.08.2012 06:46, schrieb lilyp...@googlecode.com:
> >
> > Comment #6 on issue 2790 by grenoui...@lilynet.net: Patch: bar-line
> > interface part 2/2
> > http://code.google.com/p/lilypond/issues/detail?id=2790#c6
> >
> > Build
Am 30.08.2012 06:46, schrieb lilyp...@googlecode.com:
Comment #6 on issue 2790 by grenoui...@lilynet.net: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790#c6
Build results are available at
http://grenouille.lilynet.net/patches-tests/2790/test-results
Am 30.08.2012 00:07, schrieb David Kastrup:
Marc Hohl writes:
Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/det
Marc Hohl writes:
> Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
>> Updates:
>> Labels: -Patch-new Patch-needs_work
>>
>> Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
>> interface part 2/2
>> http://code.google.com/p/lilypond/issues/detail?id=2790#c3
>>
>> Patchy th
Hello,
On 29 August 2012 22:44, Marc Hohl wrote:
> Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
>>
>> Updates:
>> Labels: -Patch-new Patch-needs_work
>>
>> Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line interface
>> part 2/2
>> http://code.google.com/p/lilypond/issues
Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790#c3
Patchy the autobot says: lots of: +programming er
On Mon, Jul 30, 2012 at 02:57:06PM +0100, Graham Percival wrote:
>
> ok, but are we stepping in the right direction here? I mean, if
> \relative c' {
> \tempo "Allegro" 4. = 60
> }
> works but
> \midi {
> \tempo "Allegro" 4. = 60
> }
> fails, I wouldn't blame anybody for being sur
Graham Percival writes:
> On Mon, Jul 30, 2012 at 03:48:48PM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > Does this affect
>> >
>> > {
>> > \tempo 4. = 120
>> > c2 d
>> > %\tempo "Adagio" 4. = 43.5
>> > \tempo "Adagio" 4. = 43
>> > e4. d8 c2
>> > }
>> >
>> > ?
>>
>
On Mon, Jul 30, 2012 at 03:48:48PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > Does this affect
> >
> > {
> > \tempo 4. = 120
> > c2 d
> > %\tempo "Adagio" 4. = 43.5
> > \tempo "Adagio" 4. = 43
> > e4. d8 c2
> > }
> >
> > ?
>
> No.
(aside: do we want to disallow all d
Graham Percival writes:
> On Mon, Jul 30, 2012 at 01:12:44PM +0200, David Kastrup wrote:
>> Graham Percival writes:
>> > Could I have some examples? I just don't get this "word"
>> > business. Is there any syntax which was previously
>> > (theoretically) supported, which this patch breaks?
>>
On Mon, Jul 30, 2012 at 01:12:44PM +0200, David Kastrup wrote:
> Graham Percival writes:
> > Could I have some examples? I just don't get this "word"
> > business. Is there any syntax which was previously
> > (theoretically) supported, which this patch breaks?
>
> Here is one thing that can be
Graham Percival writes:
> On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote:
>
>> It turns out that this definition works with
>> both "make test" as well as "make doc" without requiring any change in the
>> LilyPond code base.
>
> That's certainly promising.
>
>> Discuss. This
David Kastrup writes:
> Except that \-o can be a MARKUPCOMMAND but not a DASHED_KEY_WORD which
> can't start with a dash as first character after the backslash. A
> DASHED_KEY_WORD can contain digits, but this is mostly useless since you
> can't use them except in INITIAL mode.
>
>>> One consequ
David Kastrup writes:
> Graham Percival writes:
>
>> On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote:
>
>>> Being able to access every definition equally
>>> well in every lexer mode is also an advantage. The word definition is
>>> palindromic: iff a character sequence is a wo
Graham Percival writes:
> On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote:
>>
>> Forwarding this from the lilypond-auto list since this review concerns
>> an important syntax change. GLISS material, in a manner. Consider it a
>> proposal for word and command syntax across _all_ l
On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote:
>
> Forwarding this from the lilypond-auto list since this review concerns
> an important syntax change. GLISS material, in a manner. Consider it a
> proposal for word and command syntax across _all_ lexer modes.
What's a "lexer mod
Forwarding this from the lilypond-auto list since this review concerns
an important syntax change. GLISS material, in a manner. Consider it a
proposal for word and command syntax across _all_ lexer modes.
Reasonably simple, and somewhat surprisingly not requiring any changes
in the entire .ly co
"Trevor Daniels" writes:
> David, you wrote Saturday, July 07, 2012 5:13 AM
>
>
>> "Trevor Daniels" writes:
>>
>>> Although I should have noticed the error when git cl asked me to
>>> confirm the issue number, why did it pick the wrong one initially?
>>> How does it make its initial guess?
>>
David, you wrote Saturday, July 07, 2012 5:13 AM
> "Trevor Daniels" writes:
>
>> Although I should have noticed the error when git cl asked me to
>> confirm the issue number, why did it pick the wrong one initially?
>> How does it make its initial guess?
>
> Simple enough. It looks for the f
"Trevor Daniels" writes:
> Trevor Daniels wrote Friday, July 06, 2012 11:21 PM
>
>> This is interesting. This should refer to issue 2560, as correctly
>> entered in the commit message, but git cl for some reason selected
>> issue 2540, and I failed to notice the error, and even copied it
>> when
Trevor Daniels wrote Friday, July 06, 2012 11:21 PM
> This is interesting. This should refer to issue 2560, as correctly entered
> in the commit message, but git cl for some reason selected issue 2540, and I
> failed to notice the error, and even copied it when composing my text.
Although I s
meone please
advise how best to correct this.
Trevor
- Original Message -
From:
To:
Sent: Friday, July 06, 2012 11:05 PM
Subject: Re: [Lilypond-auto] Issue 2540 in lilypond: Patch: Give \tweak an
optional grob parameter for tweaking indirect grobs
> Updates:
> Labels
On 25 juin 2012, at 18:44, David Kastrup wrote:
> lilyp...@googlecode.com writes:
>
>> Updates:
>> Status: Fixed
>> Labels: Fixed_2_15_41
>>
>> Comment #5 on issue 2624 by
>> mts...@gmail.com: Patch: Bumps Mike to
>> Frog meister
>> http://code.google.com/p/lilypond/issues/detail?id=26
lilyp...@googlecode.com writes:
> Updates:
> Status: Fixed
> Labels: Fixed_2_15_41
>
> Comment #5 on issue 2624 by
> mts...@gmail.com: Patch: Bumps Mike to
> Frog meister
> http://code.google.com/p/lilypond/issues/detail?id=2624
>
> Pushed as 9f225e28aa279fd4ce4d9ae9cfc1ee16a3f134e0.
>> (map! + '(1 2 3) '(4 5 6)) => (5 7 9)
>
> You must not! not! not! use map! on constant lists.
Interesting. This is something non-obvious, at least after reading
the Guile documentation. Now, knowing what you've just written, a
second read makes much more sense, and I can see that th
Werner LEMBERG writes:
>> If I break down the example I listed before, here are a few
>> useful ways of applying it:
>
> This is much easier to understand, thanks. However:
>
>> ; this $@ produces elements for a sequential music list via map!. Each
>> ; element is constructed from p, a list of
> If I break down the example I listed before, here are a few
> useful ways of applying it:
This is much easier to understand, thanks. However:
> ; this $@ produces elements for a sequential music list via map!. Each
> ; element is constructed from p, a list of pitches making up a chord,
> ; a
Werner LEMBERG writes:
> I find the above much too dense. It introduces three different pseudo
> operators in one rush. While tightly related, it should be done step
> by step. So this is a criticism of the R6RS docs (being a standard to
> be read by Scheme experts), not LilyPond. However, a
> The inspiration for this ,@ is described as
>
> If an `(unquote-splicing ...)' form appears inside a
> , then the s must evaluate to lists; the
> opening and closing parentheses of the lists are then "stripped
> away" and the elements of the lists are inserted in place of t
1 - 100 of 119 matches
Mail list logo
