From: David Bremner <david@tethera.net>
To: Leo Vivier <zaephon@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 1/4] emacs: Implement notmuch-search-refine
Date: Wed, 03 Apr 2019 09:58:44 -0300 [thread overview]
Message-ID: <875zrv8cu3.fsf@tethera.net> (raw)
In-Reply-To: <87v9zvgv2y.fsf@hidden>
Leo Vivier <zaephon@gmail.com> writes:
> Discovering that severely undermined the raison d’être of this patch. I
> tried to do something else with it by having it mimic a similar function
> in mu4e where the point was put at the end of the previous search, but
> I’ve found very little use for it.
>
> I think it’s safe to abandon this patch.
>
Thanks for the followup. I'll mark it as obsolete for now.
All the best,
David
prev parent reply other threads:[~2019-04-03 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 15:36 [PATCH 1/4] emacs: Implement notmuch-search-refine zaephon
2019-04-03 10:21 ` David Bremner
2019-04-03 11:57 ` Leo Vivier
2019-04-03 12:58 ` 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=875zrv8cu3.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=zaephon@gmail.com \
/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).