lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Improving the Contributors Guide and LilyDev


From: Paul Morris
Subject: Re: Improving the Contributors Guide and LilyDev
Date: Mon, 4 May 2015 21:02:28 -0400

> On May 3, 2015, at 6:15 PM, David Kastrup <address@hidden> wrote:
> 
>> CG 3.3.4 Making Patches
>> "git format-patch origin" doesn't work if you type it in literally,
>> but gives "ambiguous argument 'origin' " message.
> 
> Shouldn't happen unless you managed to create either a local branch
> named "origin" or a file with that name in the current directory.

Ok, I’ll have to look into this further when I get a chance.  If “git 
format-patch origin” works for others on LilyDev then there’s no need to edit 
this.


> On May 3, 2015, at 9:02 PM, Urs Liska <address@hidden> wrote:
> 
> Am 04.05.2015 um 00:15 schrieb David Kastrup:
>>> CG 3.3.4 git-cl configuration
>>> >add how to set the EDITOR variable for git cl, namely:
>>> >export EDITOR=/usr/bin/nano
>> Nano does not offer point-and-click in connection with LilyPond I think.
> 
> I don't think so either.  But I don't see why that should matter here. 
> Without setting EDITOR to something different, e.g. nano, the user will be 
> facing vi during the submission process. And for most of the new people this 
> is really frightening. So this is actually important information.

Yep, having your keyboard suddenly stop working like you expect it to in the 
middle of creating your first commit or patch set can be rather maddening.  
Also if you follow the CG you might set the editor for git to nano, but when 
you use git-cl you get vi again.  So I think the default LilyDev editor should 
be nano and also explain how to change it (for git-cl) in the CG.

(I assume there are other ways of getting point-and-click if needed.)

-Paul





reply via email to

[Prev in Thread] Current Thread [Next in Thread]