2008/1/30, Risto Vääräniemi [EMAIL PROTECTED]:
On Jan 30, 2008 11:19 AM, Valentin Villenave wrote:
There's a much simpler solution: I could just make a patch against
lilypond's GUB NSIS script to call lilypond instead of
lilypond-windows when double-clicking on a .ly file.
Why are there
2008/1/29, Mats Bengtsson [EMAIL PROTECTED]:
If you instead run
lilypond-windows -dgui somefile.ly
(which is exactly what happens when you double-click on the file) then you
get the truncated .log file. The only difference between these two
executables
is that the -windows version is linked
Hi,
OFFTOPIC
On Jan 30, 2008 11:19 AM, Valentin Villenave wrote:
There's a much simpler solution: I could just make a patch against
lilypond's GUB NSIS script to call lilypond instead of
lilypond-windows when double-clicking on a .ly file.
Why are there two executables anyway? Do they
It seems that there is some difference between what ends up on the log file
if you run on Windows or if you run on some other operating system.
I don't have a Windows box with LilyPond installed, in front of me, but
when I run
lilypond -dgui yourfile.ly
in Linux, which should produce a log file
Trevor Daniels wrote:
...
So there does seem to be a problem with capturing all
the console output to the log file under XP.
Exactly! It's probably related to how the buffers are flushed when the
program terminates. Actually, it turns out that the difference is not
between
Windows and
On Jan 29, 2008 2:42 PM, Trevor Daniels wrote:
If I run this program by double-clicking the ly
file under XP I see the same logfile as Jay:
I get the same results as Trevor and I agree that it would be nice to
be able to get the same logs either by double-clickling the file or
calling lilypond
Sent: 29 January 2008 12:19
To: Jay Ricketts
Cc: lilypond-user@gnu.org
Subject: Re: Error trapping \chordmode in LP
2.11.37 for Windows
It seems that there is some difference between
what ends up on the log file
if you run on Windows or if you run on some other
operating system.
I don't have
Thanks for taking a look.
Running from the command prompt when I get a truncated log file is an
acceptable workaround for me. I'll leave it to the list's judgment whether
to add this to the bug list or not.
Thanks again,
Jay
On Jan 29, 2008 8:44 AM, Mats Bengtsson [EMAIL PROTECTED] wrote:
Hi all,
just about tore out my hair trying to figure out what was going on - I had a
simple little score for the Danish Amen - wouldn't compile, gave no error
messages in the log. I had cloned a much larger more complex piece into a
template, then edited to produce this. Finally, 45 minutes
