From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] build: drop variable HAVE_EMACS. use WITH_EMACS instead
Date: Wed, 12 Jun 2019 20:00:35 -0300 [thread overview]
Message-ID: <87d0jicsto.fsf@tethera.net> (raw)
In-Reply-To: <m2r27yhb8n.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> On Tue, Jun 11 2019, David Bremner wrote:
>
>> The extra flexibility of having both HAVE_EMACS (for yes, there is an
>> emacs we can use) and WITH_EMACS (the user wants emacs support) lead
>> to confusion and bugs. We now just force WITH_EMACS to 0 if no
>> suitable emacs is detected.
>
> LGTM.
pushed to master
d
prev parent reply other threads:[~2019-06-12 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 0:12 [PATCH] build: drop variable HAVE_EMACS. use WITH_EMACS instead David Bremner
2019-06-12 19:09 ` Tomi Ollila
2019-06-12 23:00 ` David Bremner [this message]
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=87d0jicsto.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).