John Mandereau [Thu, 2 Aug 2012 21:25:54 +0000 (23:25 +0200)]
Remove StepMake as a separate package
Rationale:
* there are no publicly-known current usage cases of StepMake outside
LilyPond,
* StepMake installation has been disabled for a decade,
* generic templates (stepmake/stepmake) have been so heavily
customized lately for our heavy documentation that they can no longer
be qualifed as "generic",
* only a few build scripts have remained in stepmake/bin, whereas
most of them now live in scripts/build.
This commit removes everything in stepmake/ except included makefiles;
scripts that are still used are moved to config/ (Autoconf helpers) or
scripts/build (build and install scripts).
Remove config make target to avoid potential conflict with new
config/ directory.
For clarity, a merge of all stepmake templates, from stepmake/stepmake
and make/ into stepmake/ (or similar), will be done in another commit.
John Mandereau [Wed, 1 Aug 2012 10:22:43 +0000 (12:22 +0200)]
Make distributed tarball from Git file list
This removes the requirement of having a GNUmakefile
in each and every directory of the source tree; this commit
also deletes GNUmakefiles made unnecessary this way.
dist-toplevel-txt-files toplevel target is also removed,
because it is unneeded outside of dist target and it
prevents linking of toplevel generated txt docs to
distdir when these docs are already generated.
In addition, on suggestions from Han-Wen, if dist is made with a
source directory tracked by Git, then
* the source directory is required to have no uncommitted changes nor
non-ignored untracked files,
* the time stamp of all files in the tarball is set to the time stamp
of the head of the checked-out branch.
Benkő Pál [Sat, 21 Jul 2012 07:21:06 +0000 (09:21 +0200)]
small changes of the line_count fixing series
- enhance support of non-standard staves by checking staff bounds or
being on staff line by juggling not line_count but staff_span or on_line
- eliminate an unnecessary call and a warning
Benkő Pál [Thu, 19 Jul 2012 21:07:57 +0000 (23:07 +0200)]
time signature positioning for non-standard staves
the only non-standardness the old code catered for is altered line-count.
the aim here is to position time signature similarly with any of the following:
\override StaffSymbol #'line-count = #'4
\override StaffSymbol #'line-positions = #'(-2 0 2 4)
\override StaffSymbol #'line-positions = #'(-4 -2 0 2)
Properly implement fromproperty markup handing in the pdftitle header field
The pdftitle header field is obtained by trying to convert the markup into a pure string.
Fromproperty markups need to be handled specially, since we have to mimick the header field
lookup in the conversion function... Thus we have to pass the header block to the
markup->string function and extract the header property values for fromproperty markups.
To keep the previous public API without the header argument working, the header
block is passed as an optional argument.
To prevent infinite loops, after looking up a header field, we temporarily
set it to an empty string for the following lookups. This is done by creating
a temporary guile module with that variable cleared.
David Kastrup [Sun, 29 Jul 2012 14:05:10 +0000 (16:05 +0200)]
Unify the lexer's idea of words and commands across all modes.
A "word" (a string recognized even when not quoted) and a "command"
(something starting with \ and followed by letters and other folderol,
indicating a Scheme control sequence or similar) get the same syntax
in all modes:
A "word" is a sequence of alphabetic characters possibly containing
single dashes or underlines inside (not at the beginning or end).
David Kastrup [Mon, 30 Jul 2012 16:10:13 +0000 (18:10 +0200)]
Issue 2705: Parse music inside of output definitions in "notes" mode.
This makes \midi { \tempo 4. = 120 } work properly (without parsing
4. as a REAL token).
The next token after music will in rare circumstances be scanned still
in the lexer's "notes" mode. This could be problematic because of the
currently different word syntax of "notes" and "INITIAL" mode
(cf. issue 2702).
David Kastrup [Fri, 27 Jul 2012 18:38:15 +0000 (20:38 +0200)]
Issue 1650: merge multiple header specifications.
Books get initialized from $defaultheader, this is what toplevel \header will
set, and scores and bookparts are initialized empty so that they will end up
combined with their respective (possibly implicit) books.
When other MIDI midi events (such as an instrument change) occur
simultaneously with note(s), they should be placed in the MIDI file
before the note-on events, otherwise there is no way to (reliably)
affect the first note in a score.
David Kastrup [Mon, 23 Jul 2012 10:25:26 +0000 (12:25 +0200)]
Issue 2692: Let ly:make-moment accept rationals for main and grace timing
For compatibility reasons, it remains possible to write two numbers
specifying numerator and denominator instead of the rationals. These
forms cannot be mixed, and the two-argument form is disambiguated by
the sign of the second argument: if it is positive, it can only be a
denominator and not a grace timing.
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.
projects / lilypond.git / log