2003-02-22 Han-Wen Nienhuys <hanwen@cs.uu.nl>
+ * input/test/*: lots of cleanups/comment-outs/removals in chord
+ examples
+
+ * input/regression/*: lots of cleanups/comment-outs/removals in chord examples
+
* scripts/lilypond-book.py (check_texidoc): add no-texidoc to options
* lily/new-chord-name-engraver.cc (process_music): give original
+\score { \notes { c4^"fixme"}}
+
%% This should only be necessary if your kpathsea setup is broken
%
% Make sure the correct msamxx.tfm is where lily can find it
\version "1.7.10"
\header {
-texidoc = "Jazz notation for chord names."
+texidoc = "Jazz notation for chord names.
+
+FIXME.
+
+"
+
}
+\score { \notes { c4^"fixme"}}
+
+%{
%% This should only be necessary if your kpathsea setup is broken
%
>
}
%% new-chords-done %%
+%}
\version "1.7.10"
+\score { \notes { c4^"fixme"}}
%{
"
}
+\score { \notes { c4^"fixme"}}
+
%{
efull = \chordnames {
+++ /dev/null
-\version "1.7.10"
-% the Gm7sus4/D chord prints as Gm/4/7/D
-% it took me quite a while by experiment to work out how to enter it -- PC
-
-% perhaps the current modifier approach is too simplistic
-
-
-
-gmsus=\notes\relative c \chords{
- g1
- % Gm7sus4: the hard way
- g1:3-.4.7
-
- % another hard way:
- \notes { << g' bes c d f >>1 }
-
- % bit easier:
- g1:m.4.7
-
- g1:m7.sus
- g1:m7.sus4
-
- % and finally:
- g1:m7.sus/d
-}
-
-\score{
- <
- \context ChordNames \gmsus
- \context Staff \gmsus
- >
-}
-%% new-chords-done %%
\header {
texidoc = "Ossias present alternatives for a piece. They are not
-really supported, but can be somewhat faked in lily".
+really supported, but can be somewhat faked in lily."
}
\score {
-
-\notes { c1 c1 < {\clef "treble" c1 c1 } \context Staff=stb{ c1 c1}>}
+\notes { c1 c1 <
+ {\clef "treble" c1 c1 }
+ \context Staff = stb { c1 c1 }
+ >
+}
}
%% new-chords-done %%