David Kastrup [Thu, 19 Jul 2012 09:11:35 +0000 (11:11 +0200)]
reopened Issue 2584: please make partcombine merge slurs
This refrains from referencing a slur grob's direction field (often
inconclusive and not representative of the input), instead referencing
the direction of the causing event.
David Nalesnik [Tue, 17 Jul 2012 22:17:59 +0000 (17:17 -0500)]
Function for overriding broken spanners
The music function \alterBroken is intended to facilitate overrides
applied independently to the pieces of broken spanners--one of the
perennial difficulties faced by users of LilyPond (addressed in
Extending 2.6:"Difficult Tweaks"). The function aims at generalization
by allowing the user to specify the name of the spanner and the property
to be overridden.
The function will override unbroken spanners, but it will ignore
non-spanners with a warning.
The function calls \override and may be prefaced by \once (or followed by
a \revert of the relevant property).
David Kastrup [Thu, 28 Jun 2012 23:48:11 +0000 (01:48 +0200)]
Issue 2671: Provide functions ly:moment-main and ly:moment-grace
Those will usually be more convenient than using ly:moment-*-numerator
and ly:moment-*-denominator.
Also, (/ (ly:moment-*-numerator ...) (ly:moment-*-denominator ...))
can't deal with infinite moment components. This could theoretically
be amended by letting (ly:moment-*-denominator ...) resolve to
_inexact_ zero (in which case the division turns out ±inf.0), but that
is all rather hand-wavy and flimsy. Being able to access the
components directly is more straightforward.
David Kastrup [Sat, 14 Jul 2012 09:19:59 +0000 (11:19 +0200)]
Issue 2661: parser.yy: remove `fraction'
Previously the parser recognized fractions as well as the lexer. The effect
was that in certain contexts it was possible to use spaces around the slash.
This necessitated lookahead in parsing and is not apparently used anywhere.
It also does not help in making the input look consistent.
David Kastrup [Thu, 12 Jul 2012 11:16:30 +0000 (13:16 +0200)]
Rewrite incipit snippet using #{ ... #} in preference to Scheme
Using #{ ... #} extensively both illustrates better what is actually
happening LilyPond-wise as well as giving a better feeling about the
available power of #{ ... #} for replacing Scheme code.
David Kastrup [Thu, 5 Jul 2012 10:24:19 +0000 (12:24 +0200)]
Interpret #... inside of music lists as music instead of ignoring it
One consequence is that you get a warning for things like
\revert Score.BarLine #'space-alist #'cue-clef
which actually reverts the whole of space-alist, then ignores #'cue-clef.
Another is that things like $(set-accidental-style 'dodecaphonic)
can be written as #(set-accidental-style 'dodecaphonic) without
getting ignored in most situations.
Void expressions (like most definitions, or the result of calling
\void) are still silently ignored since they are regarded as
intentional.
David Kastrup [Mon, 2 Jul 2012 18:27:46 +0000 (20:27 +0200)]
Reject \footnote ... \default without grob specification
The behavior of \footnote ... \default without grob specification is,
for most purposes, indistinguishable from user error. In consequence,
it has been turned into user error.
As one consequence, support for the undocumented and inefficient
compatibility mode for use of not-actually-time-based footnotes as an
articulation (-\footnote ... \default) has been removed. This can
occur as the result of convert-ly from older variants of \footnote
syntax. Targetting a NO_SMART conversion error message of convert-ly
for this use case is so much more tricky and error-prone than printing
a warning at run-time that it has not been attempted.
Clean fonts and docs makefiles, trying to fix 'make -j' race conditions
On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo),
"make -j3 all" repeatedly calls fontforge before needed .pfb files are
generated and makeinfo/extract_texi_filenames/texi2omf before .texi
file has been generated/copied. Fix this by using order prerequisites
and adding targets to WWW-1 (first stage of doc build); order (rather
than ordinary) prerequisites avoid having always outdated targets,
which would trigger compilation at install.
Remove a rule for Info manual that is no longer needed and which might
short-circuit .dep file generation.
mf/GNUmakefile: also factorize prerequisites in fonts using a macro.
Julien Rioux [Tue, 26 Jun 2012 13:54:39 +0000 (09:54 -0400)]
lilypond-book: Remove trailing path separators in include paths.
Remove the trailing path separators ("/" or "\") in include paths
(e.g. "-I ./ -I ../ -I ../common/") as they are not necessary and
cause problems on windows. Solves issue 2623.
projects / lilypond.git / log