[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form |
Date: |
Sun, 15 Jun 2014 12:36:23 +0000 |
Status: Started
Owner: address@hidden
Labels: Type-Enhancement Patch-new
New issue 3954 by address@hidden: Patch: Report bad return values in
user-readable form
http://code.google.com/p/lilypond/issues/detail?id=3954
Report bad return values in user-readable form
An error message like
markup-def.ly:11:20: error: music function cannot return
(#<procedure line-markup (layout props args)> (Test))
is not really user-readable. At the price of some possible ambiguity,
using a LilyPond syntax form like
markup-def.ly:11:20: error: music function cannot return \markup \line {
Test}
is quite preferable.
http://codereview.appspot.com/103460043
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
- [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form,
lilypond <=
- Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form, lilypond, 2014/06/15
- Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form, lilypond, 2014/06/15
- Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form, lilypond, 2014/06/17
- Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form, lilypond, 2014/06/20
- Re: [Lilypond-auto] Issue 3954 in lilypond: Patch: Report bad return values in user-readable form, lilypond, 2014/06/20