Cool. Maybe it makes sense to update the documentation to indicate the elisp files are in the precompiled tarball and just to point at them? That "make install" is a red herring.
On Fri, May 9, 2014 at 12:15 PM, R. Mattes <r...@mh-freiburg.de> wrote: > On Fri, 9 May 2014 13:44:31 -0500, Tim McNamara wrote > > [...snip...] > > (setq path > > > > "/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/Users/tim/bin:/Users/YOUR_USER_NAME/Applications/LilyPond.app/Contents/Resources/bin") > > (setenv "PATH" path) > > > > (setq load-path (append (list > > (expand-file-name"/Applications/LilyPond.app/Contents/Resources/share/emacs/site-lisp")) > load-path)) > > Much easier to do: > (add-to-list 'load-path > > (expand-file-name"/Applications/LilyPond.app/Contents/Resources/share/emacs/site-lisp")) > > > Cheers, Ralf Mattes > > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
