LGTM
I tried to look through the patch, but the page breaker has become so
much your domain that I cannot say anything useful regarding this
patch.
On Fri, Mar 13, 2009 at 6:22 PM, Joe Neeman wrote:
> I have a (largish, sorry) code review up for new min-systems-per-page, max-
> systems-per-page
Am 23.03.2009 um 18:03 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 4:45 PM
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
In any event, hopefully this is an acceptable patch. Whether or not
introduction of sing
consider it an official response. Even then, I think this should be
implemented completely on the scheme side; frankly if you're using
specialized programs, you could just as well write a .ly that wraps
toplevel-music-handler to do the work for you, without any change to
lilypond proper.
On Mon,
James E. Bailey wrote Monday, March 23, 2009 4:45 PM
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
In any event, hopefully this is an acceptable patch. Whether or
not
introduction of single-staff polyphony should be kept at this
point
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
Am 23.03.2009 um 14:54 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 0
Am 23.03.2009 um 16:50 schrieb Francisco Vila:
2009/3/23 Carl D. Sorensen :
git format-patch is what you type at the command line.
I have git version 1.5.6.3 and both git-format-patch and
git[nohyphen]format-patch do work.
James, what's the output of git --version?
git version 1.6.2.1
_
Ahh, right. Thanks Carl.
This doesn't actually do what I wanted, but it
does show me how to go about it. I'll see if
I can develop this into a Scheme function to
revert all the autoBeamSettings in a given
time signature. My first frog assignment!
It might take some time ...
Trevor
- Ori
2009/3/23 Francisco Vila :
> I have git version 1.5.6.3 and both git-format-patch and
> git[nohyphen]format-patch do work.
>
> James, what's the output of git --version?
>From your patch I see it is 1.6.2.1 ; has the hyphenated command been
deprecated? this form is still useful to invoke man page
2009/3/23 Carl D. Sorensen :
> git format-patch is what you type at the command line.
I have git version 1.5.6.3 and both git-format-patch and
git[nohyphen]format-patch do work.
James, what's the output of git --version?
--
Francisco Vila. Badajoz (Spain)
The incredible carnival of Badajoz
htt
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
Am 23.03.2009 um 14:54 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey
wrote:
Yes, I d
On 3/23/09 8:19 AM, "Trevor Daniels" wrote:
>
>
> James E. Bailey wrote March 23, 2009 12:43 PM
>>
>> Am 23.03.2009 um 13:24 schrieb Trevor Daniels:
>>
>> I'd like to say that I think removing polyphony here is a viable
>> solution, but I don't really believe that. Vocal music is heavily
>
Am 23.03.2009 um 15:54 schrieb Graham Percival:
In any event, hopefully this is an acceptable patch. Whether or not
introduction of single-staff polyphony should be kept at this
point in
the LM (since doing so does not follow Documentation policy) is a
different conversation.
The patch look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Freitag, 6. März 2009 schrieb Reinhold Kainhofer:
> A few days ago, I decided it's finally time to learn what all that
> hype about AJAX is about. What would be a better guinea pig than
> trying to implement a seach box in our docs??? Well -- it tur
On Mon, Mar 23, 2009 at 03:15:51PM +0100, James E. Bailey wrote:
>
> Am 23.03.2009 um 14:54 schrieb Graham Percival:
>
>> Good point. There should be a file called
>> 0001-something
>> in the top of the git directory. That's what you send. I'll add
>> this to the CG.
>
> Is it just me, or did th
James E. Bailey wrote March 23, 2009 12:43 PM
Am 23.03.2009 um 13:24 schrieb Trevor Daniels:
Hi James
The main difficulty I have with this simple change is that Voices
have not been introduced at this point in the Tutorial. They are
not mentioned in the Learning Manual until Chapter 3.
Am 23.03.2009 um 14:54 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
Yes, I did git commit -a and had the line : Modified:
Documen
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
>
> Am 23.03.2009 um 14:14 schrieb Graham Percival:
>
>> On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
>>>
>>> Yes, I did git commit -a and had the line : Modified: Documentation/
>>> user/tutorial.itely in that fil
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
Yes, I did git commit -a and had the line : Modified: Documentation/
user/tutorial.itely in that file. The problem is that I don't have
git-format-patch. bash reports command not f
Am 23.03.2009 um 14:14 schrieb Graham Percival:
After a few more painful iterations, the CG will contain exactly
the commands you need, so you won't *need* to know anything about
git. If you want to learn more, there's CG 1.4, but I personally
haven't read it and don't plan to do so. Ever[1].
On 3/23/09 6:25 AM, "James E. Bailey" wrote:
>>
>> Are you using Git? then use git-format-patch to generate the patch;
>> otherwise, use diff -u to obtain a diff with context lines.
>>
>> --
>> Francisco Vila. Badajoz (Spain)
>>
>> The incredible carnival of Badajoz
>> http://www.flickr.com/
James E. Bailey a écrit :
Incidentally, although the instructions in the Contributor's Guide are
generally simple enough for even me to follow, apparently they're
missing something because the git-format-patch HEAD doesn't work.
If you have a recent Git, it should probably be
git format-patch
James E. Bailey wrote:
Am 23.03.2009 um 13:50 schrieb Francisco Vila:
2009/3/23 James E. Bailey :
Incidentally, although the instructions in the Contributor's Guide are
generally simple enough for even me to follow, apparently they're
missing
something because the git-format-patch HEAD does
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
>
> Yes, I did git commit -a and had the line : Modified: Documentation/
> user/tutorial.itely in that file. The problem is that I don't have
> git-format-patch. bash reports command not found.
Sorry, you're (quite sensibly) looki
Am 23.03.2009 um 13:50 schrieb Francisco Vila:
2009/3/23 James E. Bailey :
Incidentally, although the instructions in the Contributor's Guide
are
generally simple enough for even me to follow, apparently they're
missing
something because the git-format-patch HEAD doesn't work.
It is HEA
2009/3/23 James E. Bailey :
> Incidentally, although the instructions in the Contributor's Guide are
> generally simple enough for even me to follow, apparently they're missing
> something because the git-format-patch HEAD doesn't work.
It is HEAD^ after your commit
--
Francisco Vila. Badajoz (
Incidentally, although the instructions in the Contributor's Guide
are generally simple enough for even me to follow, apparently they're
missing something because the git-format-patch HEAD doesn't work.
Am 23.03.2009 um 13:27 schrieb Trevor Daniels:
Sorry - forgot to cc the list
Trevor
--
> I'm not top posting.
Hello John,
I am really sorry to reply too late. I am recently busy to get and prepare for
the new job.
I released the new patch for ja doc. It provides files for NR and some fixes.
http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html
Add "Documentation/ja/u
Trevor forgot to cc the list.
Am 23.03.2009 um 13:24 schrieb Trevor Daniels:
Hi James
Thanks for doing this, but it doesn't seem to apply. I'm not
familiar enough with patches to identify the problem with
certainty, but git apply says "Error: no changes" and terminates.
It would be best
Sorry - forgot to cc the list
Trevor
- Original Message -
From: "Trevor Daniels"
To: "James E. Bailey"
Sent: Monday, March 23, 2009 12:24 PM
Subject: Re: an LM update
Hi James
Thanks for doing this, but it doesn't seem to apply. I'm not
familiar enough with patches to identify
Am 23.03.2009 um 13:06 schrieb Francisco Vila:
2009/3/23 James E. Bailey :
Attached is my attempt to make a .diff. It's my first time, so if
I didn't
do it right, let me know. It's a learning process for me.
Are you using Git? then use git-format-patch to generate the patch;
otherwise, use
2009/3/23 James E. Bailey :
> Attached is my attempt to make a .diff. It's my first time, so if I didn't
> do it right, let me know. It's a learning process for me.
Are you using Git? then use git-format-patch to generate the patch;
otherwise, use diff -u to obtain a diff with context lines.
--
Am 17.03.2009 um 10:39 schrieb Trevor Daniels:
Hi James
You wrote Tuesday, March 17, 2009 9:00 AM
On 17.03.2009, at 00:47, Carl D. Sorensen wrote:
On 3/16/09 11:52 AM, "James E. Bailey"
wrote:
On 16.03.2009, at 16:43, Graham Percival wrote:
c) Can we just make the change so th
This isn't an official response, but you'll probably be asked to
rework this patch as -ddisplay-music. (i.e. one of the -d*
options)
Cheers,
- Graham
On Mon, Mar 23, 2009 at 12:07:10AM -0700, Pedro Kröger wrote:
>
> Hi,
>
> The patch in the attachment implements the command line option
> --di
Hi,
The patch in the attachment implements the command line option
--display-music. If it's on it will print the internal representation of
the score like \displayMusic and exit.
The main use for this option is to use the output of --display-music as
the input for other programs (it's easier to
34 matches
Mail list logo
