From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/4] gnu: mu: Install emacs files in a proper place.
Date: Tue, 10 May 2016 11:21:43 +0300 [thread overview]
Message-ID: <8760um727c.fsf@gmail.com> (raw)
In-Reply-To: <87mvnzould.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 09 May 2016 22:16:30 +0200")
Ludovic Courtès (2016-05-09 23:16 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> * gnu/packages/mail.scm (mu)[arguments]: Add 'patch-configure.ac' phase
>> to avoid adding "mu4e" sub-directory to 'lispdir' variable.
>
> [...]
>
>> + ;; By default, elisp code goes to "share/emacs/site-lisp/mu4e",
>> + ;; so our Emacs package can't find it. Setting "--with-lispdir"
>
> Should be “--lispdir”, I think.
No, it is literally called “--with-lispdir”. Look at AM_PATH_LISPDIR in
(info "(automake) Public Macros")
--
Alex
next prev parent reply other threads:[~2016-05-10 8:21 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 [this message]
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=8760um727c.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).