Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated
Janek Warchoł wrote > 2012/1/12 -Eluze > eluzew@ > : >> the word error should be reserved for severe situations, there are other >> words to direct the attention to such discrepancies. for the actual >> "error" >> a pointer, a note or another kind of message would suffice. > > I think it would be more informative it this was a Warning, not an > Error. Especially > > fatal error: failed files [..] > > is misleading in my opinion. I concur. "Warning: Version not found" explains what is going on, much better. As Gus Baird once said, when something goes wrong in a program, you should inform a user in the least surprising way. --- Christopher Heckman -- View this message in context: http://lilypond.1069038.n5.nabble.com/Issue-2214-in-lilypond-fatal-error-reported-when-version-is-too-old-but-correct-output-is-still-gened-tp84387p196421.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2214 in lilypond: fatal error reported when version is too old but correct output is still generated
2012/1/12 -Eluze elu...@gmail.com: the word error should be reserved for severe situations, there are other words to direct the attention to such discrepancies. for the actual error a pointer, a note or another kind of message would suffice. I think it would be more informative it this was a Warning, not an Error. Especially fatal error: failed files [..] is misleading in my opinion. Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2214 in lilypond: fatal error reported when version is too old but correct output is still generated
lilypond-4 wrote: Updates: Status: Invalid Comment #1 on issue 2214 by gra...@percival-music.ca: fatal error reported when version is too old but correct output is still generated This is deliberate to avoid misunderstandings in environments like frescobaldi and related lilypond IDEs. You'll note that we create the .pdf even though it reports an error. unbelievable! and even fatal! that's the wrong way around - do you believe anybody is going to check the log anymore? -- View this message in context: http://old.nabble.com/Issue-2214-in-lilypond%3A-%22fatal-error%22-reported-when-version-is-too-old-but-correct-output-is-still-generated-tp33125536p33126897.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2214 in lilypond: fatal error reported when version is too old but correct output is still generated
On Thu, Jan 12, 2012 at 02:29:05AM -0800, -Eluze wrote: lilypond-4 wrote: This is deliberate to avoid misunderstandings in environments like frescobaldi and related lilypond IDEs. You'll note that we create the .pdf even though it reports an error. unbelievable! and even fatal! that's the wrong way around - do you believe anybody is going to check the log anymore? huh? If we *don't* display an error, nobody on windows or osx is going to check the log. That's precisely why we show an error, so that GUI programs will (hopefully) direct the user's attention to that log. What's the big deal? If this bothers you, just make sure you write the correct version numbers. If you only use 2.14.0 syntax, then write 2.14.0 instead of 2.15.26. - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2214 in lilypond: fatal error reported when version is too old but correct output is still generated
Graham Percival-3 wrote: On Thu, Jan 12, 2012 at 02:29:05AM -0800, -Eluze wrote: lilypond-4 wrote: This is deliberate to avoid misunderstandings in environments like frescobaldi and related lilypond IDEs. You'll note that we create the .pdf even though it reports an error. unbelievable! and even fatal! that's the wrong way around - do you believe anybody is going to check the log anymore? huh? If we *don't* display an error, nobody on windows or osx is going to check the log. That's precisely why we show an error, so that GUI programs will (hopefully) direct the user's attention to that log. What's the big deal? If this bothers you, just make sure you write the correct version numbers. If you only use 2.14.0 syntax, then write 2.14.0 instead of 2.15.26. the word error should be reserved for severe situations, there are other words to direct the attention to such discrepancies. for the actual error a pointer, a note or another kind of message would suffice. I often compare the result of the newest version with an older one and to do that I would always have to change the version number. and I also have an own environment which after compilation checks the log for errors and warnings in different languages. if such are found the log is displayed instead of the pdf/png. so it would be nice to keep the words error and warning associated with serious matters! cheers Eluze -- View this message in context: http://old.nabble.com/Issue-2214-in-lilypond%3A-%22fatal-error%22-reported-when-version-is-too-old-but-correct-output-is-still-generated-tp33125536p33129135.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2214 in lilypond: fatal error reported when version is too old but correct output is still generated
Updates: Status: Invalid Comment #1 on issue 2214 by gra...@percival-music.ca: fatal error reported when version is too old but correct output is still generated http://code.google.com/p/lilypond/issues/detail?id=2214 This is deliberate to avoid misunderstandings in environments like frescobaldi and related lilypond IDEs. You'll note that we create the .pdf even though it reports an error. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
