From: Rainer M Krug <R.M.Krug@gmail.com>
To: notmuch@notmuchmail.org
Cc: public-notmuch-gxuj+Tv9EO5zyzON3hdc1g@plane.gmane.org,
Rainer M Krug
<public-R.M.Krug-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>
Subject: Re: adding emacs-snapshot as alternative to emacs
Date: Fri, 22 Jun 2012 09:14:26 +0200 [thread overview]
Message-ID: <4FE41B52.1000604@gmail.com> (raw)
In-Reply-To: <87txy4cxix.fsf@zancas.localnet>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 21/06/12 20:47, David Bremner wrote:
> Rainer M Krug <R.M.Krug@gmail.com> writes:
>
>>>
>>> Here's what I'm using to get it to build right.
>>
>> Thanks - installs nicely.
>>
>> Would it be possible to include this in the source?
>>
>> Rainer
>
> See
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677900
>
> And yes, I'm the grinch.
OK - I accept the reasoning behind not adding emacs-snapshot as an alternative to the defaults.
But as I guess as quite a few are using emacs-snapshot and notmuch, it would make sense to just
add a patch to the source which one could execute to add emacs-snapshot to the list of alternative
dependencies. This would make the process more transparent and possibly easier to debug if errors
occur.
Cheers,
Rainer
>
> d
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/kG1IACgkQoYgNqgF2egrbOACggXJZxR7kQoQ+LxWZp/0cJLWB
e2cAn3qhB3bHSZQvHvBgChUemSfMUeUH
=r4H/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-06-22 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 16:25 adding emacs-snapshot as alternative to emacs Rainer M Krug
2012-06-21 17:11 ` Jeremy Nickurak
2012-06-21 18:37 ` Rainer M Krug
2012-06-21 18:47 ` David Bremner
2012-06-22 7:14 ` Rainer M Krug [this message]
2012-06-22 10:23 ` David Bremner
2012-06-22 10:32 ` Dmitrijs Ledkovs
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE41B52.1000604@gmail.com \
--to=r.m.krug@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=public-R.M.Krug-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
--cc=public-notmuch-gxuj+Tv9EO5zyzON3hdc1g@plane.gmane.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://yhetil.org/notmuch.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).