Issue 103460043: Report bad return values in user-readable form

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 103460043: Report bad return values in user-readable form (Closed)

Can't Edit
Can't Publish+Mail
Start Review

Created:
9 years, 11 months ago by dak

Modified:
9 years, 7 months ago

Reviewers:

CC:
lilypond-devel_gnu.org

Visibility:
Public.

More Reviews

Description

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.

Patch Set 1 #

Created: 9 years, 11 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+2 lines, -1 line)			Patch
	M	scm/ly-syntax-constructors.scm	View		1 chunk	+2 lines, -1 line	0 comments	Download