Re: Enhancement request: Termination message for lilypond compilations

2010-03-27 Thread Graham Percival
On Fri, Mar 26, 2010 at 12:14:50PM +, 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

Re: Enhancement request: Termination message for lilypond compilations

2010-03-26 Thread Bertalan Fodor (LilyPondTool)
(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). Doesn't LilyP

Re: Enhancement request: Termination message for lilypond compilations

2010-03-26 Thread Ian Hulin
On 25/03/10 00:22, Han-Wen Nienhuys wrote: On Wed, Mar 24, 2010 at 6:31 PM, Ian Hulin 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:

Re: [frogs] Re: Enhancement request: Termination message for lilypond compilations

2010-03-25 Thread James Lowe
hello, Mark Polesky wrote: 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. Actually with windo

Re: [frogs] Re: Enhancement request: Termination message for lilypond compilations

2010-03-25 Thread 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 li

Re: [frogs] Re: Enhancement request: Termination message for lilypond compilations

2010-03-25 Thread James Lowe
Hello Mats Bengtsson wrote: > > > Han-Wen Nienhuys wrote: >> >> 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 informati

Re: Enhancement request: Termination message for lilypond compilations

2010-03-25 Thread Han-Wen Nienhuys
On Thu, Mar 25, 2010 at 5:00 AM, Mats Bengtsson 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 do

Re: Enhancement request: Termination message for lilypond compilations

2010-03-25 Thread Mats Bengtsson
Han-Wen Nienhuys wrote: On Wed, Mar 24, 2010 at 6:31 PM, Ian Hulin 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 do

Re: Enhancement request: Termination message for lilypond compilations

2010-03-24 Thread Han-Wen Nienhuys
On Wed, Mar 24, 2010 at 6:31 PM, Ian Hulin 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

Enhancement request: Termination message for lilypond compilations

2010-03-24 Thread 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... Interpreti