Re: Windows command prompt and lilypond 2.6 native windows

[Trent J]

<<Apparently there's a still a strong relationship to Bash here.  This thing certainly isn't Windows friendly >>.

Yes there is, hopefully the kinks will be worked out but there are work arounds in the meantime. Although I find the processing to be slow so that bar by bar entry takes up too much time. Haven't been able to get the linux version of lilypond working (some libc++ library is missing... and I'm not brave enough to compile the thing myself...) to compare the speeds of the version.

Point and Click is still a no go with jEdit but it's fairly simple to have line numbers displayed in jEdit and all you have to do is hover the mouse of over the note in the PDF to find the line number where that note is on.

I've also noted that the windows version of Lilypond has problems with spaces in names of folders and files. So I install in C:\Lilypond directory and not the program files. I was able to get point and click working with VIM but again you needed to install Vim in a directory with no spaces e.g. C:\Vim\

I am still wondering whether the 'native' version of Lilypond should only be aimed at beginners to it's simple drag and drop interface (although to get the conversion programs with python is a steep learning curve) and the windows cgywin for advanced users offering all the bells and whistles. If I could get the linux version up and running I would use it. But might have to wait for a new version for that to happen. But in the meantime windows and native does work .. there's just a bit of coercion needed.

 

Trent

From: Art Hixson <address@hidden>
To: Trent J <address@hidden>
CC: address@hidden
Subject: Re: Windows command prompt and lilypond 2.6 native windows
Date: Tue, 19 Jul 2005 21:57:06 -0700

Apparently there's a still a strong relationship to Bash here.  This thing certainly isn't Windows friendly.

Trent J wrote:

>Yes I had the same problems with native lilypond but there are some
>work arounds.
>
>Setting path to lilypond.exe doesn't work as there are some problems
>later with missing files that are there.
>
>The way I use jEdit with Lilypond is to load the file into jEdit. I
>press the make lilypond file icon. It has a fit because it can't
>find bash (even if you have the native mode clicked). This leaves
>the console window open from wich you can type:
>
>"C:\Lilypond\usr\bin\Lillypond" "C:\Scores\01Son.ly"
>
>You need the quote marks the first is a direct path to where your
>lilypond.exe is installed and the next quoted item is the direct
>path of the file name. You don't have to retype this everytime you
>wish to make the pdf just use the arrow up and it will remember your
>list command (similar to dos)
>
>Trent
>
>
>
>
>From: Art Hixson <address@hidden>
>To: address@hidden
>Subject: Windows command prompt and lilypond 2.6 native windows
>Date: Mon, 18 Jul 2005 23:40:01 -0700
>
>Typing lilypond at the Windows command prompt produces no result.  
>Whereas, from the Cygwin console I get the default sample .ly file.
>I can compile a .ly file from Cygwin but not from the Windows
>prompt.  Why?
>
>It seems the only way I can send a .ly file to the Windows install
>is by dragging the file icon to the Lilypond icon on the desktop.  
>That's really painfully awkward!
>
>I really like jEdit,  because it's cultivated for Lilypond and
>Python, but I have to have Bash there just to run it anyway.  It can
>be pointed to the Windows install, of course. But I was much happier
>with the overall way things worked when Lilypond was installed in
>Cygwin.  I'd love to have Linux up on this machine, but don't have
>that option.
>
>
>
>
>--
>No virus found in this outgoing message.
>Checked by AVG Anti-Virus.
>Version: 7.0.323 / Virus Database: 267.9.1/51 - Release Date:
>2005/07/18
>
>
>
>_______________________________________________
>lilypond-user mailing list
>address@hidden
>http://lists.gnu.org/mailman/listinfo/lilypond-user
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.0.323 / Virus Database: 267.9.2/52 - Release Date:
>2005/07/19
>
>



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.9.2/52 - Release Date: 2005/07/19