Re: Emacs 24, lilypond, compile-internal, compilation-start

[David Kastrup]

Brett Presnell <address@hidden> writes:

> I am using a recent development snapshot of GNU Emacs (version
> 24.3.50.1) and the lilypond-mode.el distributed with LilyPond version
> 2.16 and 2.17. The emacs function compile-internal has been
> deprecated/obsolete for some time now, and it has been removed
> entirely from Emacs 24.3.  As a result, LilyPond-compile-file does not
> work.

[...]

> And here's the patch for lilypond-mode.el:
>
> --- lilypond-mode.el-orig     2012-12-03 07:27:32.061164026 -0500
> +++ lilypond-mode.el  2012-12-10 13:08:07.046248289 -0500
> @@ -286,13 +286,13 @@
>  (defun LilyPond-compile-file (command name)
>    ;; We maybe should know what we run here (Lily, lilypond, tex)
>    ;; and adjust our error-matching regex ?
> -  (compile-internal
> +  (compilation-start
>     (if (eq LilyPond-command-current 'LilyPond-command-master)
>         command
>       ;; use temporary directory for Commands on Buffer/Region
>       ;; hm.. the directory is set twice, first to default-dir
>       (concat "cd " (LilyPond-temp-directory) "; " command))
> -   "No more errors" name))
> +   'LilyPond-mode #'(lambda (mode-name) "*LilyPond-compile*")))
>  
>  ;; do we still need this, now that we're using compile-internal?
>  (defun LilyPond-save-buffer ()

Check out <URL:http://code.google.com/p/lilypond/issues/detail?id=3018>.
I've decided to not fill in any of the default arguments for
compilation-start for now: that makes it more likely that older versions
of Emacs will work identically.

-- 
David Kastrup