From: Alex Kost <alezost@gmail.com>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add emacs-mew.
Date: Wed, 25 Jan 2017 12:29:14 +0300 [thread overview]
Message-ID: <877f5jv66t.fsf@gmail.com> (raw)
In-Reply-To: <20170124.210806.158906060366823689.post@thomasdanckaert.be> (Thomas Danckaert's message of "Tue, 24 Jan 2017 21:08:06 +0100 (CET)")
Thomas Danckaert (2017-01-24 21:08 +0100) wrote:
> From: Thomas Danckaert <thomas.danckaert@gmail.com>
> Subject: [PATCH] gnu: Add emacs-mew.
> Date: Tue, 24 Jan 2017 18:01:11 +0100 (CET)
>
>> From 3759a0a4720165e0443bdb7522f6b4b7515aec6f Mon Sep 17 00:00:00 2001
>> From: Thomas Danckaert <thomas.danckaert@gmail.com>
>> Date: Tue, 24 Jan 2017 09:41:42 +0100
>> Subject: [PATCH] gnu: Add emacs-mew.
>>
>> * gnu/packages/mail.scm (emacs-mew): New variable.
>
> I've just discovered this patch doesn't add the package to emacs'
> load-path, so please disregard for now. (and/or tell me how to fix
> this :) )
This could happen if it adds itself to a sub-directory of
"/share/emacs/site-lisp". In 'magit' package, for example, it is fixed
by using "lispdir" makeflag. Since this package uses a full GNU Build
System, there should probably be "--with-lispdir" configure flag.
BTW, I can't apply this patch on the current master.
--
Alex
next prev parent reply other threads:[~2017-01-25 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 17:01 [PATCH] gnu: Add emacs-mew Thomas Danckaert
2017-01-24 20:08 ` Thomas Danckaert
2017-01-25 9:29 ` Alex Kost [this message]
2017-02-01 7:18 ` Thomas Danckaert
2017-02-01 9:34 ` Alex Kost
2017-02-01 10:56 ` Thomas Danckaert
2017-02-02 8:56 ` Alex Kost
2017-02-02 18:41 ` Thomas Danckaert
2017-02-03 9:39 ` Alex Kost
2017-02-03 12:22 ` Thomas Danckaert
2017-02-03 19:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877f5jv66t.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.