Hello all,
after some discussions on the frog list I created a patch improving the
use of the 'transparent property. As Neil suggested, an invisible grob
should have no whiteout, and this is what the patch does.
After grepping through the code, I don't think that this will influence the
overall
Le 17 juin 2010 à 17:31, David Kastrup a écrit :
> Carl Sorensen writes:
>
>> On 6/17/10 8:59 AM, "David Kastrup" wrote:
>>
>>>
>>>
>>> Hi,
>>>
>>> I have a question about developing Emacs input and major modes for
>>> Lilypond. What would be the right way to go forward for me?
>>>
>>> I
Nicolas Sceaux writes:
> Le 17 juin 2010 à 17:31, David Kastrup a écrit :
>
>> Carl Sorensen writes:
>>
>>> On 6/17/10 8:59 AM, "David Kastrup" wrote:
>>>
I have a question about developing Emacs input and major modes for
Lilypond. What would be the right way to go forward for me?
On 6/18/10 10:07 PM, "Kieren MacMillan"
wrote:
>
> In the short term, I'm considering creating a Tempo context, which only prints
> out tempo indications (akin to the TimeSig context of yore). This context
> could then be placed in the \score wherever one needs it, solving (1), (2),
> and (4)
Le 19 juin 2010 à 14:23, David Kastrup a écrit :
> It would appear pretty nonsensical for me to ignore your work on lyqi
> (which, in turn, appears to be slated to replace most of the existing
> lilypond-mode functionality).
Indeed, I do not use LilyPond-mode anymore.
> If it is compatible with
Marc,
The code looks great to me. Please email me a patch (so it will have you as
the author) and I will push it.
Thanks,
Carl
On 6/19/10 3:11 AM, "Marc Hohl" wrote:
> Hello all,
>
> after some discussions on the frog list I created a patch improving the
> use of the 'transparent property.
> "Nicolas" == Nicolas Sceaux writes:
Nicolas> Several years ago, I used a midi keyboard to enter the notes: one
hand
Nicolas> on the midi keyboard, and one hand on the computer keyboard, to set
Nicolas> durations, because I'm a lame keyboard player. But it turned out
that
I'm slightly uncomfortable giving "default values" in an .itely file,
but IIRC the rest of spacing.itely does that anyway, so whatever.
Thanks, pushed.
Cheers,
- Graham
On Sun, Jun 13, 2010 at 4:29 PM, Francisco Vila wrote:
> Hello,
> The attached patch adds a minimal example of what the new ve
Nicolas Sceaux writes:
> Le 19 juin 2010 à 14:23, David Kastrup a écrit :
>
>> It would appear that you work on MacOSX or so. Can you check whether
>> some variation of the Midi test code using make-serial-process I posted
>> recently could be made to work on your setup? If it did, this would b
Hi Carl,
> The first option is best, in my opinion.
Thanks.
> The down side to this approach is that you will need to have a separate
> music expression to pass to the Tempo context. I suppose that this
> expression can be the "master" expression (i.e. the expression that contains
> just skips
2010/6/19 Kieren MacMillan :
> Hey y'alls,
>
> I'm trying to solve the age-old [for me] problem of MetronomeMark
> placement.
:-)
I complained a lot about the bad "tempo indications" placement, I'm
really glad to see people trying to solve it.
Thanks!
> There are [at least] four issues that nee
Carl Sorensen schrieb:
Marc,
The code looks great to me. Please email me a patch (so it will have you as
the author) and I will push it.
Here it is.
Thank you,
Marc
Thanks,
Carl
On 6/19/10 3:11 AM, "Marc Hohl" wrote:
Hello all,
after some discussions on the frog list I created
Le 19 juin 2010 à 16:15, David Kastrup a écrit :
> Nicolas Sceaux writes:
>
>> Le 19 juin 2010 à 14:23, David Kastrup a écrit :
>>
>>> It would appear that you work on MacOSX or so. Can you check whether
>>> some variation of the Midi test code using make-serial-process I posted
>>> recently c
Nicolas Sceaux writes:
> Le 19 juin 2010 à 16:15, David Kastrup a écrit :
>
>> Nicolas Sceaux writes:
>>
>>> Le 19 juin 2010 à 14:23, David Kastrup a écrit :
>>>
It would appear that you work on MacOSX or so. Can you check whether
some variation of the Midi test code using make-seri
On Sat, Jun 19, 2010 at 3:02 AM, Kieren MacMillan
wrote:
> An excellent idea... and I don't only say that because I'd already set
> something like that in motion. ;)
> I've contacted my alma mater and have initiated just such a conversation --
> will report back as things progress.
Ditto here.
Thank you Patrick, I have reinstalled imagemagick also, and now it was
finally working.
It took me some time to get familiar with vmware, Linux (again),
Eclipse CDT, GIT, Lily etc :).
Thanks for the patience :).
I've separated the warnings patch
(http://codereview.appspot.com/1724041/show).
Thank you Patrick!
All of your comments have been incorporated into a new patch, which draws
the svgs a-ok (see attached).
~Mike
On 6/19/10 12:42 AM, "pnor...@gmail.com" wrote:
> Hi Mike,
>
> This is very impressive. Thanks for your work on this. I just have a
> few comments for you about t
Hello,
This is a feature I've wanted to add to LilyPond for a while, and I've
posted a patch set on Rietveld:
http://codereview.appspot.com/1730044/show
Any comments are appreciated, especially regarding the syntactic
requirements of the new command.
Thanks,
Patrick
___
> This is a feature I've wanted to add to LilyPond for a while, and I've
> posted a patch set on Rietveld:
>
> http://codereview.appspot.com/1730044/show
>
> Any comments are appreciated, especially regarding the syntactic
> requirements of the new command.
Looks good to me. It would be nice i
Werner LEMBERG writes:
>> This is a feature I've wanted to add to LilyPond for a while, and I've
>> posted a patch set on Rietveld:
>>
>> http://codereview.appspot.com/1730044/show
>>
>> Any comments are appreciated, especially regarding the syntactic
>> requirements of the new command.
>
> Loo
>> Looks good to me. It would be nice if I could say
>>
>> \path #0.25 #'miter #'square ##f #samplePath
>>
>> instead of using numbers for the second and third parameter. Is this
>> possible?
>
> How about defining constants path:miter and path:square instead? Then
> \path does not need speci
21 matches
Mail list logo
