| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
The StaffTab notation is a system combining graphic elements of
tablature with standard music notation and Emmett Chapman's finger
symbols for notating tapping on a Chapman Stick.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Since those lose their point of reference, expanding them
prior to retrograding keeps the results sane.
|
| |
| |
| |
| |
| |
| | |
Also changes argument \= to be a key.
Backport-by: David Kastrup <dak@gnu.org>
|
|/ |
|
|
|
|
|
|
|
| |
\afterGrace had its fraction determining the position of the aftergrace
notes hardwired to be read from the parser variable afterGraceFraction.
This change here allows for optionally specifying it right as the first
argument of the \afterGrace command.
|
|
|
|
| |
Midi_control_change_performer
|
| |
|
| |
|
|
|
|
| |
It was removed by a simplistic convert-ly rule.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
for staves with custom line positions and ledger
lines that appear inside the staff.
|
|
|
|
| |
Transform them to "\\\""
|
| |
|
|
|
|
|
| |
This is sort of arbitrary currently but matches the kind of syntax
accepted by \override/\revert due to their definition in the parser.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Issue 4772
This addresses a bug report where
dynamics in a ChoirStaff implicitly
created a PianoStaff, sporting
spurious InstrumentNames.
|
|
|
|
|
|
|
|
|
|
|
| |
Issue 4748
Provides aliases
auml, Auml, ouml,Ouml,uuml,Uuml
They were requested by a user
http://lists.gnu.org/archive/html/lilypond-user/2016-01/msg00577.html
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Better code formatting in some alists.
Previously, the 110-character lines
made it difficult to read; the new
version is also in line with what
the NR says.
Extending: comment TODO remark Telling
the user that he might be confused about
something (while he doesn’t understand
what exactly that is) only adds to confusion;
Use a properly formatted example;
This should actually show how reformatting
Scheme code makes it easier to read; however,
it uses tabs and the result in both HTML
and PDF is messy.
The new version uses normal spaces only
and should be consistent as well as clear.
Other minor wording and punctuation improvements
Capitalize LilyPond correctly
Fix typo in LM
There was an unmatched parenthesis in the text;
changed into a comma.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue 4744
It has been noted several
times that we should have
a companion for RemoveEmptyStaves
and to also set remove-first to ##t.
A doc snippet, removing-the-first-empty-line.ly,
has become obsolete with these changes.
Contains commits:
Add missing word in changes.tely
Add changes entry for RemoveEmptyStavesAll
Use RemoveEmptyStavesAll for ossia example in
Notation Reference
This rewrites documentation for
RemoveEmptyStaves and adds
information on the newly added
RemoveEmptyStavesAll.
Add RemoveEmptyStavesAll command
Introduce a new context modification
identifier, RemoveEmptyStavesAll,
to complement RemoveEmptyStaves.
It sets both the remove-empty
and remove-first properties
of VerticalAxisGroup to ##t.
|
|
|
|
|
| |
\tweak should only tweak music as of issue 4533, so move the action of
issue 4500 into \propertyTweak's definition instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Werner L reported in 2012 that LP
emits a space glyph referencing
the century schoolbook font at the
top of every page.
If you use gs (old and current) or
pdfcrop to crop output with multiple
pages and print-page-number = ##f
there is excessive white space at the
top of even pages.
ghostscript should handle that better
but a recent gs bug report
http://bugs.ghostscript.com/show_bug.cgi?id=696445
was closed as "WONTFIX".
There is a workaround within lilypond:
\paper {
[...]
oddHeaderMarkup = \markup \null
evenHeaderMarkup = \markup \null
}
Changing " " to "" cured the problem
and appears to have no negative side
effects. Bounding boxes are affected
by this patch certainly so will have
effects in situations where snippets
are used by other third party
programs.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
issue 4655
restores the arguments of determine-frets (changed with issue 4643)
to the previous state, changes the code of determine-frets to rely
on the newly created supportNonIntegerFret-context-property
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
issue 4643
micro-tones in TabStaff are now printable. Unless the chosen
string-tuning will allow it, this feature is disabled for
FretBoards.
- changing determine-frets (adding an optional argument) and
fret-number-tablature-format
- adding a regtest with quarter-tone-string-tuning
- documenting it in Documentation/notation/fretted-strings.itely
and Documentation/changes.tely
|
| |
|
| |
|
| |
|
|
|
|
| |
They are now called as \once \partcombine*
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One music type and concept less to worry about.
Since this tracks the partcombine decisions via context properties,
using one forced partcombine override in one voice will not be cancelled
by another forced partcombine in another.
In the event stream, \once\override is indistinguishable from
\override ... \revert so in order to be able to implement
\once\partcombine ... in one voice, we have to retain any permanent
\partcombineForce in the other.
|
| |
|
| |
|
| |
|