"Trevor Daniels" <[email protected]> writes: > David, you wrote Saturday, July 07, 2012 5:13 AM > > >> "Trevor Daniels" <[email protected]> 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 first occurence of "issue" or "Issue" >> followed by a number. Here is your text: > > Ah, right. Found it. It is only _after_ this test fails to find > a number that it looks for a number in brackets, which is > where I was expecting it to look. So in this case it ignored > the correct number in brackets in the commit line. > > I guess my attention was more on fighting vi than making > sure I entered the correct issue number again.
Set the environment variable EDITOR to an editor you would like better. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
