* Documentation/topdocs/INSTALL.texi: give even more detailed orders.

[lilypond.git] / Documentation / topdocs / INSTALL.texi

diff --git a/Documentation/topdocs/INSTALL.texi b/Documentation/topdocs/INSTALL.texi
index 6437694eac730cefd3df832f65fcff8e80ac5c35..7c34d3c6a3bc14f5a0c8776ff4057adc5e7141bd 100644 (file)
--- a/Documentation/topdocs/INSTALL.texi
+++ b/Documentation/topdocs/INSTALL.texi
@@ -16,7 +16,7 @@
 @section Downloading
 
 Even numbered versions are `stable' (2.0, 1.8 etc), while odd version
-are development releases (1.9, 1.7 etc).  Building LilyPond is an
+are development releases (2.1, 1.9, etc).  Building LilyPond is an
 involved process, so if possible, download a precompiled binary from
 @uref{http://www.lilypond.org/,the lilypond site}.
 
@@ -26,8 +26,7 @@ involved process, so if possible, download a precompiled binary from
 Download source tarballs from here:
 @itemize @bullet
 @item Download development releases from
-@uref{ftp://ftp.lilypond.org/pub/LilyPond/} by FTP and
-@uref{http://www.lilypond.org/ftp/} by HTTP.
+@uref{http://www.lilypond.org/download/} by HTTP.
 @item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror).
 @end itemize
 
@@ -239,26 +238,30 @@ to your @var{load-path}. Append the following line (modified) to your
 
 @section Vim mode
 
-@c lilypond.words.el for vim auto-completion?
-A Vim mode for entering music and running LilyPond is contained in
-the source archive. Append the content of @file{vimrc} to @file{~/.vimrc}
-to get shortcuts. Install file @file{lilypond.words.el} to @file{~/.vim/} to 
-get auto-completion. Syntax highlighting you get by installing files
-@file{lilypond.vim} and @file{lilypond.words.vim} to @file{~/.vim/syntax/} 
-and appending the following to @file{~/.vim/filetype.vim}:
-@quotation
+A Vim mode for entering music and running LilyPond is contained in the 
+source archive. For version 6.2 and newer, Vim-mode works directly after 
+installing LilyPond. Otherwise, complete the following two steps.
+
+For earlier versions (and if @code{$VIM} environment variable does not
+fall-back to @file{/usr/local/share/vim}, see @code{:version} in vim), 
+the LilyPond file type is detected if your file @file{~/.vim/filetype.vim} @c
+has the following content:
 @example
-       " my filetype file
        if exists("did_load_filetypes")
-         finish
+         finish
        endif
        augroup filetypedetect
-         au! BufRead,BufNewFile  *.ly          setfiletype lilypond
-       augroup
+         au! BufNewFile,BufRead *.ly           setf lilypond
+       augroup END
+@end example
+If Vim has been (pre-)installed to @file{/usr/...} (or any other place) 
+instead of @file{/usr/local/...}, then @file{/usr/local/share/vim} may not 
+be specified in your @code{$VIMRUNTIME} environment variable and you have to 
+include this path explicitly by appending the following line to your 
+@file{~/.vimrc}:
+@example
+       set runtimepath+=/usr/local/share/vim/
 @end example
-@end quotation
-
-
 
 @section Problems
 
@@ -267,6 +270,20 @@ reports to @email{bug-lilypond@@gnu.org}.
 
 Bugs that are not fault of LilyPond are documented here.
 
+@subsection Bison 1.875
+
+There is a bug in bison-1.875: compilation fails with "parse error
+before `goto'" in line 4922 due to a bug in bison. To fix, either
+recompile bison 1.875 with the following fix:
+
+@example
+   $ cd lily; make out/parser.cc
+   $ vi +4919 out/parser.cc
+   # append a semicolon to the line containing "__attribute__ ((__unused__))
+   # save
+   $ make
+@end example
+
 @subsection Linking to kpathsea
 
 If kpathsea and the corresponding header files are installed in some