Re: Behavior on Errors; Separate Run Output

[Phil Holmes]

"Christopher Heckman"  wrote in message 
news:caa_flenhqe+i9tvhwhsvcdjyfhvuadgqf_3gwej0k2wj69y...@mail.gmail.com...

These would probably count as "annoying" bugs.

(1) When I compile a Lilypond file that contains an error, Lilypond
should not open up the previous .pdf file: An error means I have to go
back to the file, which means closing the .pdf file first. (This could
be added in the form of a preferences menu with items like "behavior
upon error" and "behavior upon warning". Default would be "compile and
open output file".)

(2) When I compile a Lilypond file, make some changes, compile it
again, and so on, the various compilations in the log file are
continuous. Some sort of a separator (even if it's just hyphens)
should be put between compilings.

--- Christopher Heckman


As far as I'm aware, LilyPond itself does neither of these things.  Are you 
using a program such as Frescobaldi, and confusing what it does with what 
LilyPond does?


--
Phil Holmes



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Behavior on Errors; Separate Run Output

[Christopher Heckman]

These would probably count as "annoying" bugs.

(1) When I compile a Lilypond file that contains an error, Lilypond
should not open up the previous .pdf file: An error means I have to go
back to the file, which means closing the .pdf file first. (This could
be added in the form of a preferences menu with items like "behavior
upon error" and "behavior upon warning". Default would be "compile and
open output file".)

(2) When I compile a Lilypond file, make some changes, compile it
again, and so on, the various compilations in the log file are
continuous. Some sort of a separator (even if it's just hyphens)
should be put between compilings.

--- Christopher Heckman

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond