Test of link to controlling directions.

[lilypond.git] / Documentation / user / input.itely

diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely
index ddeb12a37d0cd2554e55c4e1b7788aeae10cc937..036367738b3f29df0ab23908576e8878afa73040 100644 (file)
--- a/Documentation/user/input.itely
+++ b/Documentation/user/input.itely
@@ -329,7 +329,7 @@ For more information on output formats, see @rprogram{Invoking lilypond}.
 
 @seealso
 
-Examples: @lsr{non-notation,clip-systems.ly}
+Examples: @c @lsr{non-notation,clip-systems.ly}
 
 
 @node Including LilyPond files
@@ -429,7 +429,7 @@ To use a Unicode escape sequence, use
 
 @seealso
 
-@lsr{text,utf-8.ly}
+@c @lsr{text,utf-8.ly}
 
 
 @node Different editions from one source
@@ -498,7 +498,7 @@ a piece of music with multiple @code{\tag} entries,
 
 @seealso
 
-Examples: @lsr{parts,tag@/-filter@/.ly}
+Examples: @c @lsr{parts,tag@/-filter@/.ly}
 
 
 @refbugs
@@ -511,12 +511,12 @@ sections.
 @section Common syntax issues TODO name?
 
 @menu
-* Up and down::                 
+* Controlling direction::       
 * Distances and measurements MAYBE MOVE::  
 @end menu
 
-@node Up and down
-@subsection Up and down
+@node Controlling direction
+@subsection Controlling direction
 
 TODO: everything
 
@@ -537,6 +537,10 @@ Also cover
 
 Maybe rename section to "directions".
 
+Also mention \override Foo #'direction = #'DOWN.
+
+also mention the typical \fooDown, \fooNeutral predefined commands.
+
 
 @node Distances and measurements MAYBE MOVE
 @subsection Distances and measurements MAYBE MOVE
@@ -558,6 +562,7 @@ TODO: staff spaces, #UP #DOWN #LEFT #RIGHT.  Maybe move into tweaks?
 * Skipping corrected music::    
 * context list FIXME::          
 * another thing FIXME::         
+* Input modes FIXME::           
 @end menu
 
 @node Displaying LilyPond notation
@@ -637,6 +642,22 @@ voices and staves, saving even more time.
 @node context list FIXME
 @subsection context list FIXME
 
+>> > > - list of contexts: my *danger unmaintainable* 
+>> > > alarm just went off.  I'm 
+
+I knew it would... And leaving out some of them is perfectly fine
+with me.
+I do think that a list like this, with the main contexts and a
+brief
+description of  what they do (perhaps also with a note about what
+default
+behaviour is associated with each of them, but this may be
+unmanageable),
+should be there, and then we could simply list the remaining ones
+without
+further explanation and with links to the IR.
+
+
 The Master Of All Contexts
 ==========================
 
@@ -787,4 +808,28 @@ Which are rules of the underlying language, and which are
 LP-specific?
 
 
+@node Input modes FIXME
+@subsection Input modes FIXME
+
+\notemode
+
+\notemode turns the front end of LilyPond into note mode
+(which is the default parsing mode).
+It's certainly useful in certain situations, for example if you
+are in \lyricmode or \chordmode or ... and want to insert
+something that only can be done with \notemode syntax.
+
+See for example
+http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00418.html
+http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00218.html
+http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00236.html
+http://lists.gnu.org/archive/html/lilypond-user/2006-11/msg00061.html
+
+
+\chords
+\drums
+\fretmode ?
+
+
+