Re: [PATCH 0/4] Update mu and autoload mu4e.

[Alex Kost <alezost@gmail.com>]

Ludovic Courtès (2016-05-10 16:23 +0300) wrote:

> Alex Kost <alezost@gmail.com> skribis:
>
>> Ludovic Courtès (2016-05-09 23:11 +0300) wrote:
>>
>>> Alex Kost <alezost@gmail.com> skribis:
>>>
>>>> Hello, does anyone use mu4e (emacs interface for 'mu')?  If you do, may
>>>> I ask how?  By adding "~/.guix-profile/share/emacs/site-lisp/mu4e" to
>>>> 'load-path' manually and requiring mu4e?
>>>
>>> I don’t use it, but…
>>>
>>>> Our Emacs doesn't look in sub-directories of "share/emacs/site-lisp"
>>>> (only in "guix.d" subdir), so mu4e is not found automatically...
>>>> I've just thought that it would probably be better to look at site-lisp
>>>> subdirs and not to use a special "guix.d" directory, but it's for a
>>>> separate thread.
>>>
>>> … I would just move ‘mu4e’ under ‘guix.d’, no?
>>
>> Why?  magit, geiser, paredit, emms, w3m, wget (and probably some others)
>> are all in 'site-lisp'.  Do you think they also should be moved into
>> sub-directories?  I don't mind but…
>
> Ah no, you’re right.  Then at least “mv mu4e/*.el .”?

Sorry, what do you mean?  My patch already puts elisp files in
"site-lisp" directory.

> The main problem seems to be this mu4e/ sub-directory.

Yes, and it is fixed with PATCH 2.  Currently *.el[c] files go to
"site-lisp/mu4e" directory so our emacs doesn't find them.  To fix it I
add a phase to patch "configure.ac" and the elisp files will go to
"site-lisp", as the GNU Build System originally wants.

To clear it all up, this package modifies 'lispdir' automake variable,
so if you do this:

  ./configure --with-lispdir=/tmp/mu4e-elisp-files

The elisp files will go to "/tmp/mu4e-elisp-files/mu4e" directory.  I
just removed this violent modification, so *.el files go where they
should (without additional "mu4e" level).

-- 
Alex