<>.
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
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 missi
On Mon, 18 Jul 2005 23:40:01 -0700, Art Hixson <[EMAIL PROTECTED]>
wrote:
You can compile from the menu or the toolbar if you set the path to
Lilypond.exe in Plugins/Plugin Options/LilyPondTool/General inside
JEdit:
Lilypond command: C:\LilyBin\usr\bin\lilypond.exe
The compile button works OK.
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
> From: Art Hixson [mailto:[EMAIL PROTECTED]
> Sent: den 19 juli 2005 08:40
> To: lilypond-user@gnu.org
> Subject: Windows command prompt and lilypond 2.6 native windows
>
> Typing lilypond at the Windows command prompt produces no result.
> Whereas, from the Cygwin console I get the default s
