Re: lilycontrib

2009-12-28 Thread Ian Hulin
A related question, Does wish (and therefore lilypond-git) run in the bash shell provided by git on Windows, if not, in the words of NASA: Houston, we have a problem. . . Cheers, Ian ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: lilycontrib

2009-12-28 Thread Carl Sorensen
On 12/28/09 4:59 AM, Ian Hulin i...@hulin.org.uk wrote: A related question, Does wish (and therefore lilypond-git) run in the bash shell provided by git on Windows, if not, in the words of NASA: Houston, we have a problem. . . On my Parallels version of XP, when I downloaded and

Re: lilycontrib

2009-12-28 Thread Graham Percival
On Mon, Dec 28, 2009 at 11:59:19AM +, Ian Hulin wrote: A related question, Does wish (and therefore lilypond-git) run in the bash shell provided by git on Windows, if not, in the words of NASA: Houston, we have a problem. . . Dscho offered to make a custom git installer for windows,

Re: lilycontrib

2009-12-28 Thread Mark Polesky
lilycontrib-0.52.tcl to the Git/bin/ directory, and from Git Bash I just do: $ lilycontrib-0.52.tcl and it works fine. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilycontrib

2009-12-28 Thread Ian Hulin
*haven't* got a problem. Mark, this means you've got the option in your re-design of the CG chapter headings to have a split between * contributors using the git GUI and lilypond-git (formerly lilycontrib) * contributors using git and git-cl from the bash shell instead of * contributors working

Re: lilycontrib

2009-12-28 Thread Carl Sorensen
?) in the CG, that's fine. Thanks, all, for confirming we *haven't* got a problem. Mark, this means you've got the option in your re-design of the CG chapter headings to have a split between * contributors using the git GUI and lilypond-git (formerly lilycontrib) * contributors using git

Re: lilycontrib

2009-12-28 Thread Graham Percival
lilycontrib) * contributors using git and git-cl from the bash shell Actually, I think it's a three-way split: * those using lily-git (not lilypond-git, that's the name of the directory) This option requires no knowledge of git at all -- just use the 3 buttons * those using git

Re: lilycontrib

2009-12-28 Thread Trevor Daniels
Graham Percival wrote Monday, December 28, 2009 8:09 PM Why discuss git gui at all? Just give the command-line options. No. Git GUI and gitk provide a far easier way to work with branches than the command line. If the intention is to help people move up to developing why deliberately

Re: lilycontrib

2009-12-28 Thread Trevor Daniels
Carl Sorensen wrote Monday, December 28, 2009 8:03 PM Actually, I think it's a three-way split: * those using lily-git (not lilypond-git, that's the name of the directory) This option requires no knowledge of git at all -- just use the 3 buttons * those using git gui * those using

Re: lilycontrib

2009-12-27 Thread Graham Percival
On Sat, Dec 26, 2009 at 12:30:11PM -0700, Carl Sorensen wrote: Currently, lilycontrib uses ~/lilypond/, which may conflict with an installed LilyPond directory. Should we change the directory to ~/lilypond-git, or ~/lilypond-src? Let's do ~/lilypond-git, since that reinforces the notion

Re: lilycontrib

2009-12-27 Thread Carl Sorensen
On 12/27/09 11:01 AM, Graham Percival gra...@percival-music.ca wrote: On Sat, Dec 26, 2009 at 12:30:11PM -0700, Carl Sorensen wrote: Currently, lilycontrib uses ~/lilypond/, which may conflict with an installed LilyPond directory. Should we change the directory to ~/lilypond-git

lilycontrib

2009-12-26 Thread Carl Sorensen
We recently had some discussion about the directory for the local repository. Currently, lilycontrib uses ~/lilypond/, which may conflict with an installed LilyPond directory. Should we change the directory to ~/lilypond-git, or ~/lilypond-src? It's trivial to do in lilycontrib. Thanks, Carl