Werner LEMBERG writes:
>> The line length in the patch is already limited to 80 characters.
>
> Indeed, the line length is OK in stafftab-engraver.scm, but both
> stafftab.ly and string-tunings-init.ly exceed the limit.
Ah, I see. Sorry about that. I already modified stafftab.ly to break
the d
>> To simplify the process, I suggest that you get write access to the
>> lilypond git repository so that you can add such incremental
>> patches to one or more separate branches (I like this method
>> bettern than the `modern' way of forking lilypond at github, then
>> followed by push requests) –
>> Just having a quick look (since I don't understand Tab notation at
>> all) I ask you the same as almost everybody else who commits a
>> patch the first time: Please try to limit the line length to 80
>> characters!
>
> The line length in the patch is already limited to 80 characters.
Indeed,
David Nalesnik writes:
> When I apply your patch and try to compile the example file I get:
>
> warning: cannot find or create new `StaffTab'
> warning: cannot find or create new `StaffTab'
> warning: cannot find or create new `StickVoice'
> warning: cannot find or create new `StickVoice'
> MIDI
Werner LEMBERG writes:
> Just having a quick look (since I don't understand Tab notation at
> all) I ask you the same as almost everybody else who commits a patch
> the first time: Please try to limit the line length to 80 characters!
The line length in the patch is already limited to 80 charact
> Here's the patch:
Just having a quick look (since I don't understand Tab notation at
all) I ask you the same as almost everybody else who commits a patch
the first time: Please try to limit the line length to 80 characters!
Werner
___
lilypond-
Hi Lukas,
once again, I am no expert on ancient notation. So I don't know whether the
length of the stems in your renaissance style are required to be exactly as long
as they are now. They roughly end in the middle of a staff space for notes on
this position and on a staff line for notes on a staf
On Mon, Feb 23, 2015 at 5:24 PM, David Nalesnik
wrote:
>
>
> On Mon, Feb 23, 2015 at 5:15 PM, David Nalesnik
> wrote:
>
>> Hi Ricardo,
>>
>> On Mon, Feb 23, 2015 at 4:42 PM, Ricardo Wurmus
>> wrote:
>>
>>>
>>> Here's the patch:
>>>
>>
>> When I apply your patch and try to compile the example fi
On Mon, Feb 23, 2015 at 5:15 PM, David Nalesnik
wrote:
> Hi Ricardo,
>
> On Mon, Feb 23, 2015 at 4:42 PM, Ricardo Wurmus
> wrote:
>
>>
>> Here's the patch:
>>
>
> When I apply your patch and try to compile the example file I get:
>
> warning: cannot find or create new `StaffTab'
> warning: canno
Hi Ricardo,
On Mon, Feb 23, 2015 at 4:42 PM, Ricardo Wurmus wrote:
>
> Here's the patch:
>
When I apply your patch and try to compile the example file I get:
warning: cannot find or create new `StaffTab'
warning: cannot find or create new `StaffTab'
warning: cannot find or create new `StickVoi
Hi,
I failed to authenticate with Rietveld via git-cl (using the web interface it
works just fine); the reason is given as "WebLoginRequired". Since I don't know
how to fix this, I'm sending my patch along with this email.
It adds new tunings for the Chapman Stick and a StaffTab engraver.
Here'
Werner LEMBERG gnu.org> writes:
> No. Not a patch, but a series of patches, adding the stuff in small,
> incremental steps that are easy to review. I'm willing to proof-read
> all changes to the Metafont sources.
>
> To simplify the process, I suggest that you get write access to the
> lilyp
Lukas Pietsch writes:
> Indeed, I quite agree it's a matter of how best to make the basic
> Lilypond system most efficiently extendable. I'd like to think of what
> I'm proposing as a thing with two layers.
>
> There is a set of core functional extensions that will just enhance
> the coverage of
David Kastrup gnu.org> writes:
> You state "The notation samples, which include numerous highly uncommon
> and idiosyncratic forms, will be encoded in the corpus in an XML-based
> format". If the forms are highly uncommon and idiosyncratic, can they
> be described by an XML-based expressions tha
>>I have a working draft of the Lilypond coding, which involves quite
>>a bit of Scheme code, a patched Lilypond font with a section of new
>>proposed glyphs, and a few minor patches to Lilypond's C++ codebase.
>>Unfortunately, owing to the latter, the whole system currently works
>>only with a pa
On 2/23/15 10:38 AM, "Lukas Pietsch" wrote:
>I have a working draft of the Lilypond coding, which involves quite a bit
>of
>Scheme code, a patched Lilypond font with a section of new proposed
>glyphs,
>and a few minor patches to Lilypond's C++ codebase. Unfortunately, owing
>to
>the latter, the
16 matches
Mail list logo
