The patch was up for review for less than 90 minutes, and did not
receive approval from the Documentation Editor (who has some
suggestions for this patch).
Graham Percival [Mon, 25 Oct 2010 07:48:40 +0000 (08:48 +0100)]
convert-ly run: update some tricky files.
Ok, maybe they're not "tricky", but it's good to get these changes
handled. freboards was the only "trick" change where convert-ly
did the wrong thing and required manual attention.
Neil Puttock [Sun, 24 Oct 2010 23:10:29 +0000 (00:10 +0100)]
Fix #1355.
A derived smob cannot use the macro IMPLEMENT_TYPE_P () to export
its type predicate, since this relies on the IMPLEMENT_SMOBS ()
macro to initialize the class's smob tag and predicate function
(smob_p ()): IMPLEMENT_SMOBS () is reserved for use in base classes.
In the case of Stream_event, this results in both ly:stream-event?
and ASSERT_SMOB (Stream_event, ...) failing to distinguish
stream events from other Probs.
* lily/function-documentation.cc (init_func_doc):
add type predicate documentation for Stream_event
* lily/include/stream-event.hh:
remove declaration for Stream_event predicate
* lily/stream-event-scheme.cc:
implement ly:stream-event? manually
use LY_ASSERT_TYPE () instead of LY_ASSERT_SMOB ()
Graham Percival [Thu, 21 Oct 2010 08:05:22 +0000 (09:05 +0100)]
convert-ly: option to only modify changed files.
This useful for the regtests -- with the extra -d flag, we will
only change the \version string if the actual contents of the file
has changed. This lets us see which tests were modified, and
which tests were unchanged since the previous stable release.
However, the version string will still be updated to match the
last stable release.
Fix #903: a simpler syntax for note names language
This commit adds a new
\language "foo"
command, where "foo" is the (case-insensitive) name of
any supported language, e.g. "italiano", "suomi" etc.
This function may be used at top-level or anywhere else,
even in -dsafe mode.
Non-supported languages arguments are, well, not supported:
if no recognizable string is provided, ly:gulp-file will just
barf its standard error message.
To preserve full compatibility with existing code, this patch
leaves .ly language files unchanged (therefore, the old syntax
is still perfectly valid). Since all it does is extract the
pitchnames alist from whatever file it processes, more complex
files such as "arabic.ly" are not supported and will output
an error message explaining that \include should be used instead.
In spite of this limitation, this method is a convenient way
of presenting foreign users with a simplified syntax, without
having to bloat the parser with yet another keyword. Of
course, it may be superseeded in the future with a more
specialized implementation, possibly doing away with .ly files
(if we reach a point where preserving compatibility is no
longer an issue).
Add make-void-music function for syntax consistency.
We had make-sequential-music, make-simultaneous-music
and the like, but not make-void-music ('void Music is
used, for instance, in music-functions that only
override options etc.).
Patrick Schmidt [Sun, 19 Sep 2010 19:36:30 +0000 (21:36 +0200)]
doc additions power chords
additions to fretted-strings.itely description and examples for the use of the new command \powerChords
addition of two new modifiers to notation-appendices.itely
Graham Percival [Thu, 21 Oct 2010 07:34:01 +0000 (08:34 +0100)]
Doc: convert-ly on English docs.
I left most of the \RemoveEmptyStaff as it came from convert-ly;
some of the grammar is a bit weird, but the basic idea is still
there.
I excluded
Documentation/snippets/new/
changing-the-time-signature-without-affecting-the-beaming.ly
because convert-ly wasn't smart enough to update it, and neither
am I, since I know nothing about the new beaming code.
Ian Hulin [Mon, 18 Oct 2010 19:20:07 +0000 (20:20 +0100)]
T1265 - Remove deprecation warnings when running with Guile V2 Replace scm_str2symbol with scm_from_locale_symbol, scm_symbol2_string with scm_to_locale_symbol, also scm_num2int, scm_int2num, scm_num2double
This commit makes the code cleaner and more concise,
by removing several duplicate parts. Since I was the one
who last wrote this specific part, I'm feeling kind of
compelled to clean my own mess...