From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/4] Update mu and autoload mu4e.
Date: Wed, 11 May 2016 18:00:37 +0200 [thread overview]
Message-ID: <87a8jwtwii.fsf@gnu.org> (raw)
In-Reply-To: <87bn4cn83z.fsf@gmail.com> (Alex Kost's message of "Wed, 11 May 2016 14:32:00 +0300")
Alex Kost <alezost@gmail.com> skribis:
> 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.
Right, sorry. So everything is fine with patch #2 applied from my POV.
:-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-05-11 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 10:21 [PATCH 0/4] Update mu and autoload mu4e Alex Kost
2016-05-08 10:21 ` [PATCH 1/4] gnu: mu: Use 'modify-phases' Alex Kost
2016-05-09 20:14 ` Ludovic Courtès
2016-05-08 10:21 ` [PATCH 2/4] gnu: mu: Install emacs files in a proper place Alex Kost
2016-05-09 20:16 ` Ludovic Courtès
2016-05-10 8:21 ` Alex Kost
2016-05-10 13:23 ` Ludovic Courtès
2016-05-08 10:21 ` [PATCH 3/4] gnu: mu: Install emacs autoloads Alex Kost
2016-05-09 20:17 ` Ludovic Courtès
2016-05-08 10:21 ` [PATCH 4/4] gnu: mu: Update to 0.9.16 Alex Kost
2016-05-09 20:17 ` Ludovic Courtès
2016-05-08 16:11 ` [PATCH 0/4] Update mu and autoload mu4e Leo Famulari
2016-05-09 20:11 ` Ludovic Courtès
2016-05-10 8:21 ` Alex Kost
2016-05-10 13:23 ` Ludovic Courtès
2016-05-11 11:32 ` Alex Kost
2016-05-11 16:00 ` Ludovic Courtès [this message]
2016-05-12 10:03 ` Alex Kost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8jwtwii.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).