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 woul
2012/1/12 -Eluze :
> 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
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
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
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 r
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 lik
Status: Accepted
Owner:
New issue 2214 by idragos...@gmail.com: "fatal error" reported when version
is too old but correct output is still generated
http://code.google.com/p/lilypond/issues/detail?id=2214
compiling a ly file with obviously wrong version number yields
GNU LilyPond 2.15.2
