Also, for all people installing from RPM:s, Debian packages or some other prepackaged form of Lilypond, the package will hopefully install the files in some directory that's already included in the load-path, which makes the suggested instruction less relevant. Probably, the people who build and install Lilypond themselved are more used to tweaking path variables than. I agree with Laura that there's a risk to stay with old versions of the files if you manually install them in a personal lisp directory instead of letting the load path point to the installation directory.
/Mats Quoting Laura Conrad <[EMAIL PROTECTED]>: > >>>>> "Heikki" == Heikki Johannes Junes <[EMAIL PROTECTED]> writes: > > > Heikki> Copy lilypond-mode.el, lilypond-font-lock.el and > Heikki> lilypond-indent.el to ~/site-lisp/ and lilypond-init.el to > Heikki> ~/site-lisp/site-init.d/. > > What I did was add my CVS lilypond directory to load-path, so that > when the .el files changed, I could use the new ones. > > > -- > Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) > (617) 661-8097 fax: (801) 365-6574 > 233 Broadway, Cambridge, MA 02139 > > > > _______________________________________________ > Lilypond-devel mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/lilypond-devel > _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
