Re: Compilation Progress Messages - a suggestion

[ian_hulin]

Hi Graham,

Thanks for the info.

 I know about -V (--verbose), but as you rightly point out you only really
need that amount of information if you're doing some detailed
problem-solving in the score.

 I'm really talking about the information messages Lily gives my default. 
You're often forced into using -V and picking through loads of just to
establish exactly where in the process the compilation coughed and
spluttered.

  I think by default Lily should tell the user what the end result of the
overall process is, and the current message about producing the .ps file is
just plain confusing.  If you're looking to cherry-pick a minimum amount of
work out of what I suggested in the original post fixing those two would be
great from the non-developer user's point of view

Cheers


Ian Hulin


Graham Percival-2 wrote:
> 
> ian_hulin wrote:
>> Each pass of the compilation starts with a {whatever}ing ... type
>> message,
>> may have a progress message ([1] [2] [3] or suchlike), and is terminated
>> by
>> a 'successful completion' message.  Obviously there would also be
>> messages
>> to inform the user if the particular phase of the compilation failed.
> 
> You can get a lot more information about the compilation process by 
> doing lilypond -V foo.ly  (if you're using the command-line version). 
> Most users don't want to see that much info, so we don't display it by 
> default.
> 
> I'm not certain how to get -V if you're using one of the graphical 
> editors, though.
> 
> Cheers,
> - Graham
> 
> 
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Compilation-Progress-Messages---a-suggestion-tf3049542.html#a8486987
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.