unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: guix-devel@gnu.org
Subject: [PATCH 0/4] Update mu and autoload mu4e.
Date: Sun,  8 May 2016 13:21:47 +0300	[thread overview]
Message-ID: <1462702911-18777-1-git-send-email-alezost@gmail.com> (raw)

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?

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.

Returning to mu4e, I see that (require 'mu4e) is recommended¹, but IMO
requiring features in your ".emacs" is a bad practice.  I recommend to
avoid it if possible, because requiring big packages can significantly
reduce start-up time of your Emacs.  Instead you can wrap your settings
with 'with-eval-after-load' and use 'autoload' function if you need to
"pick" some command from a package.  Alternatively there is
'use-package' package².

After this patchset, "M-x mu4e" will be available right away (do not
require mu4e, as it will not be needed).

[PATCH 1/4] gnu: mu: Use 'modify-phases'.
[PATCH 2/4] gnu: mu: Install emacs files in a proper place.
[PATCH 3/4] gnu: mu: Install emacs autoloads.
[PATCH 4/4] gnu: mu: Update to 0.9.16.

¹ http://www.djcbsoftware.nl/code/mu/mu4e/Minimal-configuration.html#Minimal-configuration
² https://github.com/jwiegley/use-package

             reply	other threads:[~2016-05-08 10:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-08 10:21 Alex Kost [this message]
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
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=1462702911-18777-1-git-send-email-alezost@gmail.com \
    --to=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).