[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: elpa startup



 ❦ 10 septembre 2015 16:43 +0100, "Barak A. Pearlmutter" <barak@pearlmutter.net> :

> I'm converting my most trivial emacs package, vala-mode-el, to
> elpa-vala-mode.  In vala-mode-el, the emacsen-startup file contains this
> snippet:
>
>     (autoload 'vala-mode "vala-mode" "Major mode for editing Vala code." t)
>     (add-to-list 'auto-mode-alist '("\\.vala$" . vala-mode))
>     (add-to-list 'auto-mode-alist '("\\.vapi$" . vala-mode))
>     (add-to-list 'file-coding-system-alist '("\\.vala$" . utf-8))
>     (add-to-list 'file-coding-system-alist '("\\.vapi$" . utf-8))

I am in a similar situation. I see that you did patch directly the mode
to add some autoload:

;;;###autoload
(add-to-list 'auto-mode-alist '("\\.vala$" . vala-mode))
;;;###autoload
(add-to-list 'auto-mode-alist '("\\.vapi$" . vala-mode))

Is that what we should do?

I am also concerned about what happens with the files that were created
in the *.emacsen-* files.

Should I put the content of my emacsen-remove at some point or will
emacsen-common execute it on upgrade?
-- 
How apt the poor are to be proud.
		-- William Shakespeare, "Twelfth-Night"

Attachment: signature.asc
Description: PGP signature


Reply to: