The syntax still uses the deprecated infix style
@code{\[ music expr \]}. For consistency reasons, it will eventually
-be changed to postfix style @code{note\[ ... note\]}.
+be changed to postfix style @code{note\[ @dots{} note\]}.
@c Alternatively, the file
@c @file{gregorian-init.ly} can be included; it provides a scheme
All other neumes, including the single-note neumes with a
different shape such as the @emph{virga}, are in principle
considered as ligatures and should therefore be placed
-between @code{\[...\]}.
+between @code{\[@dots{}\]}.
@c Regarding the @emph{punctum}, @code{b} and @code{\[ b \]} are
@c equivalent.
@example
\layout @{
- ...
+ @dots{}
\context @{
\Voice
\remove "Stem_engraver"
@example
\new Voice = "tenor" @var{music}
-...
+@dots{}
\new Lyrics \lyricsto "tenor" @var{lyrics}
@end example
There is an exception to this general rule: just one of the
@code{Voice} contexts in a @code{Staff} context or in a
-@code{<<...>>} construct will always persist to the end of the
-enclosing @code{Staff} context or @code{<<...>>} construct, even
+@code{<<@dots{}>>} construct will always persist to the end of the
+enclosing @code{Staff} context or @code{<<@dots{}>>} construct, even
though there may be periods when it has nothing to do. The context
to persist in this way will be the first one encountered in the
-first enclosed @code{@{...@}} construct, ignoring any in enclosed
-@code{<<...>>} constructs.
+first enclosed @code{@{@dots{}@}} construct, ignoring any in enclosed
+@code{<<@dots{}>>} constructs.
Any context can be kept alive by ensuring it has something to do at
every musical moment. @code{Staff} contexts are kept alive by
@emph{etc.}
@}
@{
- @emph{..music..}
+ @emph{@dots{}music@dots{}}
@}
@end example
\with @{
[context settings for this context instance only]
@} @{
-...
+ @dots{}
@}
@end example
properties.
@code{fontSize} is a special property: it is equivalent to
-entering @code{\override ... #'font-size} for all pertinent
+entering @code{\override @dots{} #'font-size} for all pertinent
objects. Since this is a common change, the special
property (modified with @code{\set}) was created.
@end lilypond
-@item @code{<< \new Staff ... >>}
+@item @code{<< \new Staff @dots{} >>}
@tab more staves
@tab
@lilypond[relative=1]
@funindex{\chords}
-@code{\chords @{ ... @}} is a shortcut notation for
-@code{\new ChordNames @{ \chordmode @{ ... @} @}}.
+@code{\chords @{ @dots{} @}} is a shortcut notation for
+@code{\new ChordNames @{ \chordmode @{ @dots{} @}}.
@lilypond[verbatim,quote,ragged-right]
\chords {
@code{BassFigure} objects. Figured bass can also be displayed
in @code{Staff} contexts.
-@code{\figures@{ ... @}} is a shortcut notation for
-@code{\new FiguredBass @{ \figuremode @{ ... @} @}}.
+@code{\figures@{ @dots{} @}} is a shortcut notation for
+@code{\new FiguredBass @{ \figuremode @{ @dots{} @} @}}.
Although the support for figured bass may superficially resemble chord
@example
\score @{
-...
+ @dots{}
@}
@end example
Comments are one exception to this general rule. (For others see
@ref{File structure}.) Both single-line comments and comments
-delimited by @code{%@{ .. %@}} may be placed anywhere within an
+delimited by @code{%@{ @dots{} %@}} may be placed anywhere within an
input file. They may be placed inside or outside a @code{\score}
block, and inside or outside the single music expression within a
@code{\score} block.
@example
\score @{
- @var{..music..}
+ @var{@dots{}music@dots{}}
@}
@end example
@example
\markup @{
- @var{..text..}
+ @var{@dots{}text@dots{}}
@}
@end example
@example
\score @{
- @var{..}
+ @var{@dots{}}
@}
\markup @{
- @var{..}
+ @var{@dots{}}
@}
\score @{
- @var{..}
+ @var{@dots{}}
@}
@end example
\header @{ piece = "Romanze" @}
@}
\markup @{
- ..text of second verse..
+ @dots{}text of second verse@dots{}
@}
\markup @{
- ..text of third verse..
+ @dots{}text of third verse@dots{}
@}
\score @{
@dots{}
A single-line comment, introduced by a leading @code{%} sign.
@item
-A multi-line comment delimited by @code{%@{ .. %@}}.
+A multi-line comment delimited by @code{%@{ @dots{} %@}}.
@end itemize
@example
@code{variable} = @code{\markup} @{
- ...
+ @dots{}
@code{\on-the-fly} \@var{procedure} @var{markup}
- ...
+ @dots{}
@}
@end example
@example
@code{\on-the-fly \first-page}
@code{\on-the-fly \last-page}
- @code{@{ \markup ... \fromproperty #'header: ... @}}
+ @code{@{ \markup @dots{} \fromproperty #'header: @dots{} @}}
@end example
determines if the output is a single page.
The syntax of a footnote in stand-alone text with automatic marks is
@example
-\markup @{ ... \auto-footnote @var{text} @var{footnote} ... @}
+\markup @{ @dots{} \auto-footnote @var{text} @var{footnote} @dots{} @}
@end example
The elements are:
The syntax of a footnote in stand-alone text with custom marks is
@example
-\markup @{ ... \footnote @var{mark} @var{footnote} ... @}
+\markup @{ @dots{} \footnote @var{mark} @var{footnote} @dots{} @}
@end example
The elements are:
@example
\include "parts/VI.ly"
\include "parts/VII.ly"
-... etc
+@dots{} etc
@end example
Files which are to be included can also contain @code{\include}
libA.ly
A1.ly
A2.ly
- ...
+ @dots{}
@end example
@noindent
#(ly:set-option 'relative-includes #t)
\include "A1.ly"
\include "A2.ly"
-...
+@dots{}
% return to default setting
#(ly:set-option 'relative-includes #f)
@end example
@example
\include "VI.ly"
\include "VII.ly"
-... etc
+@dots{} etc
@end example
Files which are to be included in many scores may be placed in
@verbatim
showLastLength = R1*5
-\score { ... }
+\score { @dots{} }
@end verbatim
@noindent
@example
\score @{
- @var{...music...}
+ @var{@dots{}music@dots{}}
\midi @{ @}
@}
@end example
@example
\score @{
- @var{...music...}
+ @var{@dots{}music@dots{}}
\midi @{ @}
\layout @{ @}
@}
@example
\new Staff @{
\set Staff.midiInstrument = #"glockenspiel"
- @var{...notes...}
+ @var{@dots{}notes@dots{}}
@}
@end example
@example
\new Staff \with @{midiInstrument = #"cello"@} @{
- @var{...notes...}
+ @var{@dots{}notes@dots{}}
@}
@end example
@example
\score @{
- @var{...music...}
+ @var{@dots{}music@dots{}}
\midi @{
\tempo 4 = 72
@}
@example
\midi @{
- ...
+ @dots{}
\context @{
\Voice
\remove "Dynamic_performer"
@example
\score @{
- @var{..music..}
- \layout @{ .. @}
+ @var{@dots{}music@dots{}}
+ \layout @{ @dots{} @}
@}
\score @{
- \unfoldRepeats @var{..music..}
- \midi @{ .. @}
+ \unfoldRepeats @var{@dots{}music@dots{}}
+ \midi @{ @dots{} @}
@}
@end example
@example
\unfoldRepeats \articulate <<
- all the rest of the score...
+ all the rest of the score@dots{}
>>
@end example
line followed by optional parameters.
@example
-@var{time} @var{type} @var{...params...}
+@var{time} @var{type} @var{@dots{}params@dots{}}
@end example
This information can easily be read into other programs such as
c1
@end lilypond
-@item (volta @var{number}) ... (volta #f)
+@item (volta @var{number}) @dots{} (volta #f)
Create a new volta with the specified number. The volta bracket must
be explicitly terminated, or it will not be printed.
@itemize
@item
-If a manual beam is specified with @code{[..]} set the beam
+If a manual beam is specified with @code{[@dots{}]} set the beam
as specified, otherwise
@item
construct:
@example
-<< @{ \voiceOne ... @}
- \new Voice @{ \voiceTwo ... @}
+<< @{ \voiceOne @dots{} @}
+ \new Voice @{ \voiceTwo @dots{} @}
>> \oneVoice
@end example
@subsubsubheading The double backslash construct
-The @code{<< @{...@} \\ @{...@} >>} construct, where the two (or
+The @code{<< @{@dots{}@} \\ @{@dots{}@} >>} construct, where the two (or
more) expressions are separated by double backslashes, behaves
differently to the similar construct without the double backslashes:
@emph{all} the expressions within this construct are assigned
case the @code{\partcombine} function can be overriden with the
following commands:
-Commands ending in @code{...Once} apply only to the next note in the
+Commands ending in @code{@dots{}Once} apply only to the next note in the
music expression.
@itemize
@rinternals{Voice}.
@knownissues
-All @code{\partcombine...} functions can only accept two voices and are
+All @code{\partcombine@dots{}} functions can only accept two voices and are
not designed to work with lyrics; such that when one of the voices is
explicitly named in order to attach lyrics to it, the partcombiner will
stop working.
-@code{\partcombine...} functions cannot be placed inside a @code{\tuplet}
+@code{\partcombine@dots{}} functions cannot be placed inside a @code{\tuplet}
or @code{\relative} block.
If @code{printPartCombineTexts} is set and the two voices play the same
projects / lilypond.git / commitdiff