Enhancement request: Termination message for lilypond compilations

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Enhancement request: Termination message for lilypond compilations

Ian Hulin
I've always thought it a real shame that the standard set of messages from lilypond left you with a nagging sense of uncertainty whether it had actually completed or not.

Typically, you would see this:

$ Lilypond Exsultate.ly
GNU LilyPond 2.13.15                                                                  
Processing `Exsultate.ly'                                                             
Parsing...                                                                            
Interpreting music...                                                                 
Preprocessing graphical objects...                                                    
Solving 1 page-breaking chunks...[1: 1 pages]                                         
Drawing systems...                                                                    
Layout output to `Exsultate-Allegro.ps'...                                            
Converting to `./Exsultate-Allegro.pdf'...                                            
Interpreting music...                                                                 
Preprocessing graphical objects...                                                    
Solving 1 page-breaking chunks...[1: 1 pages]                                         
Drawing systems...                                                                    
Layout output to `Exsultate-Andante.ps'...                                            
Converting to `./Exsultate-Andante.pdf'...      
$
The program's told you it started converting .ps to the .pdf, but gives you no indication how it completed.

I've attached a patch to do this:
$ Lilypond Exsultate.ly
GNU LilyPond 2.13.17                                                                  
Processing `Exsultate.ly'                                                             
Parsing...                                                                            
Interpreting music...                                                                 
Preprocessing graphical objects...                                                    
Solving 1 page-breaking chunks...[1: 1 pages]                                         
Drawing systems...                                                                    
Layout output to `Exsultate-Allegro.ps'...                                            
Converting to `./Exsultate-Allegro.pdf'...                                            
Interpreting music...                                                                 
Preprocessing graphical objects...                                                    
Solving 1 page-breaking chunks...[1: 1 pages]                                         
Drawing systems...                                                                    
Layout output to `Exsultate-Andante.ps'...                                            
Converting to `./Exsultate-Andante.pdf'...      
success: Compilation successfully completed                                           
$

If there were any problems found the last line says
warning: Compilation completed with warnings or errors

It's available for review on rietveld http://codereview.appspot.com/736041

Cheers,

Ian Hulin


0001-Lilypond-issues-success-failure-termination-message.patch (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Enhancement request: Termination message for lilypond compilations

Mats Bengtsson-3


Han-Wen Nienhuys wrote:

> On Wed, Mar 24, 2010 at 6:31 PM, Ian Hulin <[hidden email]> wrote:
>  
>> I've always thought it a real shame that the standard set of messages from
>> lilypond left you with a nagging sense of uncertainty whether it had
>> actually completed or not.
>>
>> Typically, you would see this:
>>    
>
> Why don't you alias lilypond to
>
>   (lilypond "$*" && echo Success) || echo Failed
>
> simpler, and more conformant to the unix tradition ("no news is good news").
>  
We already print out a quite extensive log of information during the
processing (which probably is not conformant to the UNIX tradition), so
why is it so bad to also tell the user that the PDF was successfully
produced.

    /Mats

--
=============================================
        Mats Bengtsson
        Signal Processing
        School of Electrical Engineering
        Royal Institute of Technology (KTH)
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463
        Fax:   (+46) 8 790 7260
        Email: [hidden email]
        WWW: http://www.s3.kth.se/~mabe
=============================================


---
----
Join the Frogs!

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Enhancement request: Termination message for lilypond compilations

J_ames
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Enhancement request: Termination message for lilypond compilations

Mark Polesky
James Lowe wrote:
> So, from a non-Unix user who doesn't really 'know much
> stuff', I'd like to just add that I think it would be a
> nice step to know that the PDF was created, for example
> some earlier versions of Mac OS will not create the PDF if
> it is already open by another App, Windows likewise.

I seem to recall getting some sort of cryptic "permission
denied" error when trying to compile foo.ly while foo.pdf
was still open.  That was usually enough to remind me to
close the pdf, but it wasn't particularly informative.

So I'm not opposed to having some sort of conformation, but
a simple "\nDone.\n" would suffice.  Presumably the return
of the "$" prompt should signal completion as Han-Wen
implies, but of course not every user is at a command
prompt:

http://lists.gnu.org/archive/html/lilypond-devel/2009-07/msg00678.html

I have vague memories of being confused on Windows, not
using a command line (double-clicking my file icon).  If I
recall, the only output I could find was the resulting log
file, and I often felt under-informed whenever the process
would hang.

- Mark


     

---
----
Join the Frogs!

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Enhancement request: Termination message for lilypond compilations

J_ames
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Enhancement request: Termination message for lilypond compilations

Ian Hulin
In reply to this post by Ian Hulin
On 25/03/10 00:22, Han-Wen Nienhuys wrote:

> On Wed, Mar 24, 2010 at 6:31 PM, Ian Hulin<[hidden email]>  wrote:
>> I've always thought it a real shame that the standard set of messages from
>> lilypond left you with a nagging sense of uncertainty whether it had
>> actually completed or not.
>>
>> Typically, you would see this:
>
> Why don't you alias lilypond to
>
>    (lilypond "$*"&&  echo Success) || echo Failed
1. Lilypond is a multi-OS application, it doesn't just run under bash on
a Linux-derived OS (e.g cmd on Windows, running from detached "gui"
environment from JEdit or Frescobaldi - btw JEdit could also be running
under Windows).
>
> simpler, and more conformant to the unix tradition ("no news is good news").

2. Not necessarily transportable (see above).
3. "no news is good news" is also positive spin for "developers can't
bothered" or "developer can't be bothered with user perspective of using
the application". :-}

Seriously though, the current situation for Lilypond is inconsistent.
If you have a set of
        doing this. . .
        doing that. . .
        doing the other. . .

messages, your application should have the good manners to let the user
know it's finished
        doing . . .
and has either
        . . .succeeded
or
        . . .failed.
Cheers,
Ian




---
----
Join the Frogs!

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Enhancement request: Termination message for lilypond compilations

Graham Percival
On Fri, Mar 26, 2010 at 12:14:50PM +0000, Ian Hulin wrote:
> Seriously though, the current situation for Lilypond is inconsistent. If
> you have a set of
> doing this. . .
> doing that. . .
> doing the other. . .

I agree with this.  If LilyPond's successful output was more
terse, I'd agree with Han-Wen, but since we already spew out so
many things on the command-line, it makes sense to add a
"completed everything" or "5 pdf(s) created" or the same.

That said, I'd also like a -q option to lilypond, which would only
produce output for warnings or errors (i.e. no "calculating line
breaks / pages / creating ps / etc).  That way, everybody can get
what they want: unix-style "no news is good news", and
current-lilypond-style "keep the user informed".

Cheers,
- Graham

---
----
Join the Frogs!

Loading...