[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No progress messages on GUI under Windows 7

From: Phil Holmes
Subject: Re: No progress messages on GUI under Windows 7
Date: Thu, 17 Oct 2013 15:41:41 +0100

"Marek Klein" <address@hidden> wrote in message news:address@hidden
---------- Forwarded message ----------
From: Jeff Wahl <address@hidden>
Date: 2013/10/17
Subject: Re: No progress messages on GUI under Windows 7
To: Marek Klein <address@hidden>
Cc: Eluze <address@hidden>

On 10/16/2013 3:52 PM, Marek Klein wrote:

Forwarding to OP:

2013/10/14 Eluze <address@hidden>

Jeff Wahl wrote
> But I prefer to work with a GUI interface. Neither LilypondTool (no
> supported) under jEdit nor Frescobaldi will show progress messages from
> Lilypond 2.16 binaries in the respective console windows (of > LilypondTool
> or
> Frescobaldi). Both of these GUI interfaces will show the messages when
> using
> an older major version of Lilypond. What has changed (not explained in
> Lilypond documentation)?

what exactly used to be displayed (and is not displayed in newer versions)
when you run Lilypond from the command line. which versions were they?


bug squad member

With previous versions of Lilypond (2.12.3, 2.14.2) the GUI programs would
produce, in their console windows:

Starting lilypond-windows.exe 2.12.3 [Concerto in G Major.ly]...
Processing `C:/Users/Public/Music/Concerto in G Major.ly'
Interpreting music...
Interpreting music... [8][16][24][32]
Preprocessing graphical objects...
MIDI output to `Concerto in G Major.mid'...
Finding the ideal number of pages...
Fitting music on 1 or 2 pages...
Drawing systems...
Layout output to `Concerto in G Major.ps'...
Converting to `./Concerto in G Major.pdf'...
Completed successfully in 3.4".

This is what is produced from the command line (in terminal mode) as well,
with all versions of Lilypond I've tried.

Using Lilypond 2.16.2 or 2.17, through a GUI program, only the first and
last lines would show. No progress messages; these are always sent to the
log file on disk instead. The consoles might indicate a termination with an
error code; any explanation would be in the log file.

When I've looked at the Python code for Lilypond 2.16, I've seen changes to
the code for logging and printing messages to stdout and stderr.


This behaviour is by design.

Phil Holmes
Bug Squad

reply via email to

[Prev in Thread] Current Thread [Next in Thread]