James Lowe [Sun, 2 Aug 2015 13:11:22 +0000 (14:11 +0100)]
Doc: Usage - tidy up of external.itely file
Issue 4536
In preparation for some
work done on this file
I have tried to get some
consistency with regard
to white space / line breaks
between @nodes, @cindex et al
to make the file easier to
follow. Also I have corrected
very obvious errors and excessive
line lengths.
Thomas Morley [Thu, 30 Jul 2015 18:39:22 +0000 (20:39 +0200)]
Let \autochange accept optional arguments for the turning-point and clefs
Issue 4530
With the fix for issue 4465 bassStaffProperties and trebleStaffProperties are gone.
This patch reimplements the functionality to set clefs for the staves and offers the
possibility to set another turning-point apart from middle-C.
This is done with optional arguments for \autochange.
Two regtests are added to reflect these possibilities.
Documentation/notation/keyboards.itely is extended accordingly.
Also inserting the usual remarks about license, etc in autochange.scm.
James Lowe [Sat, 25 Jul 2015 09:53:23 +0000 (10:53 +0100)]
Doc: CG - Tightening up of the Bug Squad intro
Issue 4521
Moved some of the bug squad @section to
@subsection in an effort to 'tighten' up
the information. Reworded some of the
introduction section, trying to keep
it more succint.
James Lowe [Tue, 21 Jul 2015 15:58:53 +0000 (16:58 +0100)]
Doc: CG - removed information about test-patchy
test-patchy.py no longer works with
code.google.com and as we're moving
away from this tracker system, I am
taking the information out of the
CG regarding this script.
I have left the lilypond-patchy-staging
information in and adjusted the
troubleshooting section accordingly.
David Kastrup [Thu, 23 Jul 2015 16:19:58 +0000 (18:19 +0200)]
Issue 4519: event-chord-wrap! needs to call expand-repeat-notes!
The action of event-chord-wrap! will make it impossible to figure out
repeat notes (notes without pitch but with duration) but one must not
expand repeat notes before expanding chord repeats, and
event-chord-wrap! does expand chord repeats. So it needs to call
expand-repeat-chords! as well before doing its compatibility processing.
No point in joining and later splitting separate functions. The
original motivation might have been to reduce name space pollution, but
(scm ly-syntax-constructors) is a separate module by now.
David Kastrup [Sat, 18 Jul 2015 18:22:15 +0000 (20:22 +0200)]
Issue 4510: Change comments like Voice "1" to Voice = "1"
This corresponds closer to the syntax of \context/\new and makes it less
likely that the rather programmatic meaning of those comments gets lost
on readers and translators.
issue 3903/1: replace all occurrences of news.lilynet.net with archive.org URL
The command used is:
git grep -l 'news.lilynet.net' | xargs sed -i 's/news.lilynet.net/web.archive.org\/web\/20110325004849\/http:\/\/news.lilynet.net/g'
David Kastrup [Wed, 15 Jul 2015 21:30:30 +0000 (23:30 +0200)]
Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes
There is still one shortcoming: the percent repeats will not contain any
material apart from the percent itself. In particular, no Timing
changes will be repeated. If there are meter changes or \partial
commands inside of percent repeats, they need to occur in parallel
passages outside of any percent repeat, if necessary in a separate
"timing track".
David Kastrup [Sun, 12 Jul 2015 16:30:46 +0000 (18:30 +0200)]
Issue 4498: Provide music functions property{Override,Revert,Set,Unset}
The previous music functions `override' and `revert' (intentionally
colliding with the respective keywords) are removed. It would have been
too confusing to have collisions for `set' and `unset' as well which are
just too similar to existing Scheme constructs.
A convert-ly rule for the previous calls override/revert is not
attempted: they have not yet been documented and have been available
only for one unstable version. Whoever happened to use them already is
capable of replacing them.
\markup \bold-red "text"
\markuplist \column-lines \bold-red { One Two Three }
Please note that in order for \markup to recognize the resulting markup
command inside of markup expressions, the identifier to which the
resulting markup command is assigned needs to have "-markup" appended to
its name: LilyPond encodes markup command names in this manner so that
markup commands can use the same name as other entities outside of
markup mode.
Note also that this will not work with the markup macro since the latter
additionally requires the definition of a suitable make-bold-red-markup
command.
David Kastrup [Thu, 9 Jul 2015 12:54:14 +0000 (14:54 +0200)]
Issue 4487/2: Allow for chaining of several partial functions in a row
Chaining only works when all function calls except the last one have all
arguments supplied already, with their last argument being the rest of
the chained call.
David Kastrup [Thu, 9 Jul 2015 20:09:42 +0000 (22:09 +0200)]
Issue 4486: Improve `music-function' and `music-function-error' in Syntax
Apart from correct behavior for fallback music expressions (create
copies and give them source location), it also streamlines the code a
bit and drops the historic `rest' argument to `music-function'.
David Kastrup [Sun, 12 Jul 2015 17:27:53 +0000 (19:27 +0200)]
Issue 4497: Fix non-rebase/convert of issue 4445 in parallel with issue 4442
Rerunning the conversion rule used in issue4442 fixes this issue. This
should have been a showstopper for commands such as \omit and \offset
but it appears that check-grob-path does not mind the spurious argument
at all.
Keith OHara [Sun, 28 Jun 2015 05:20:38 +0000 (22:20 -0700)]
Docs: remove implicit relative from translations; issue 4731
Apply 88cfc9ee61 to tranlations.
In order to prevent `diff` and `patch` from applying short changes
to the wrong examples, given that the context is in different langages,
this patch first used `sed` with
/^@lilypond\s*\[/,/@end lilypond/ s/^/;/
so each entire @lilypond example generated a diff hunk.
Dan Eble [Sat, 30 May 2015 16:46:44 +0000 (12:46 -0400)]
Issue 4485: Refactor \partcombine and \autochange iterators
Move the \partcombine context state machine from C++ to Scheme and
move the part-specific work into a new Part_combine_part_iterator.
What remains in Part_combine_iterator is multi-measure rest handling.
The part-specific work is now nothing more than changing context at
specified times, which is basically what \autochange does. There are
still some differences, but most of the implementation of both is now
in the common base Change_sequence_iterator.