[EMAIL PROTECTED] writes:
> Dear Lilypond,
>
> Jan assisted me through some problems I was having and I've been making sure things
>are working, but I have one more problem.
>
> I am not able to use the xdvi. I checked and doubled checked my syntax, with the
>tutorial and I'm entering everyth
I suggest you use Ghostview to viwe your PS files (as I do). I could not run
xdvi either from my PC. Ghostview can be get for free from several web
sites, look for it with any finder.
Carlos
- Original Message -
From: "Deborah Lowrey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wedn
Just a little note to let you know that the problems noted by Simon (bad
syntax of the `eval' command) is due to the different `eval' syntax in
Guile 1.4.x. Yesterday I installed Guile 1.5.6 on my home computer, and
any problem disappeared.
Perhaps somebody should correct `INSTALL.txt' (in Lilyp
> I don't understand.
>
> I'm using Guile 1.4, and it's fine for LilyPond 1.4.13 and 1.4.58.
> Maybe there are modified versions of Guile around, or maybe there's a
> problem with Guile 1.4.1?
>
> What lilypond version are you using, what guile version, and where did
> you get your guile?
>
> Jan.
Maurizio Tomasi <[EMAIL PROTECTED]> writes:
> Just a little note to let you know that the problems noted by Simon (bad
> syntax of the `eval' command) is due to the different `eval' syntax in
> Guile 1.4.x. Yesterday I installed Guile 1.5.6 on my home computer, and
> any problem disappeared.
>
>
Maurizio Tomasi <[EMAIL PROTECTED]> writes:
>> I'm using Guile 1.4, and it's fine for LilyPond 1.4.13 and 1.4.58.
-> 1.5.58
> Yes, you are right. In fact, I had no problems running version 1.4.13.
> The error messages came when I installed Lily 1.5.58 (NOT 1.4.58 as I said
> in my message ---
i installed guile-1.5.6 yesterday, and had a compilation error when i
tried recompiling lilypond. i think that was to do with cached
config-files. i started with a fresh code tree, and am now compiling
lilypond again.
it may take a while to finish (old machine), but i'll keep you posted.
greetin
> I'm using guile 1.4 and lilypond 1.5.58 too (or actually latest cvs,
> but I don't think there has been a fix).
This is strange. I downloaded Guile from the Guile Home Page under
www.gnu.org via anonymous CVS, and before upgrading to 1.5.6 I had serious
troubles running Lily 1.5.58 (I was not
Maurizio Tomasi <[EMAIL PROTECTED]> writes:
> In fact, `my-eval-in-module' is defined to be
> 'eval'
This is wrong. For guile < 1.5.x, it should be set to eval-in-module.
Hmm. What does
guile -c '(write (minor-version))'
say? I suspect it says "4.1", and that's why you're seeing this
p
[EMAIL PROTECTED] writes:
> > I'm using guile 1.4 and lilypond 1.5.58 too (or actually latest cvs,
> > but I don't think there has been a fix).
>
> This is strange. I downloaded Guile from the Guile Home Page under
> www.gnu.org via anonymous CVS, and before upgrading to 1.5.6 I had serious
> tr
> Hmm. What does
>
> guile -c '(write (minor-version))'
>
> say? I suspect it says "4.1", and that's why you're seeing this
> problem.
"Unfortunately" (!) my Lilypond system now runs well, so I erased
Guile 1.4.1 from my hard disk. Thus, I cannot run this test.
But I think my problem was
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> These reports about guile incompatibility are bogus.
I don't think so, I think these guys are using Guile 1.4.1. But this
could have been stated a bit clearer.
Unfortunately, what is actually Guile 1.4.0 gets called Guile 1.4, and
in addition, Gui
Hello Simon,
> > - Set the environment variable LILYPONDPREFIX to
> > the full path of the lilypond-1.5.58/ directory and
> > try to rerun the make command.
>
> [root@box lilypond-1.5.58]$ LILYPONDPREFIX=/usr/share/lilypond-1.5.58
> [root@box lilypond-1.5.58]$ LILYINCLUDE=$LILYPONDPREFIX/ly
hi david,
> If you define them in this way then only the shell knows about these
> variables. If you want that also the programs and scripts (like ly2dvi)
> that you call from the shell know them (and you do want that in this
> case), then you should use the "export" command before the definition
> "simon" == simon bailey <[EMAIL PROTECTED]> writes:
simon> hmm, that's what i thought as well, but when i tried exporting them, after
simon> setting them, i received an error message, so left it at that.
simon> [box]$ export $LILYPONDPREFIX
You should have said:
expo
Denemo version 0.6.0 is now available from:
http://sourceforge.net/projects/denemo
New Features:
Basic Support for Lyrics
Invisible Musical Objects
CSound Output
Along with various small bug fixes.
Lyrics are still at the testing stage and require looking at especially
syllable extenders.
Ad
Hi all
I am completely lost.
Problem: In LilyPond shell all the key commands return with an error message.
For example after typing
lilypond --version
the following message appears:
BASH: lilypond: command not found
The results are similar with commands python, ly2dvi, qswin32c
Please take a look at the following archived emails
http://www.mail-archive.com/lilypond-user@gnu.org/msg01060.html
http://www.mail-archive.com/lilypond-user@gnu.org/msg00857.html
from this mailing list, that should provide some hints
/Mats
___
Lily
Greetings,
I would like to put a large set of brackets around some notes like this:
____
| * * * * |
| | | | ||
| | | | ||
| | | | ||
| | | | ||
| ---
19 matches
Mail list logo
