unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: v3 support undo in emacs frontend.
Date: Thu,  3 Feb 2022 10:32:42 -0400	[thread overview]
Message-ID: <20220203143254.3344753-1-david@tethera.net> (raw)

This obsoletes the series at [1].  Unlike that series it does not
modify the CLI, only the emacs front end. I realized we were already
expanding thread queries into lists of message-ids, which was my main
worry about query stability.

I am currently trying to track down a race condition in one of the new
tests, which is why the series is still marked RFC/WIP.

[1]: id:20220129194439.2790761-1-david@tethera.net

 [RFC PATCH v2 01/12] doc/emacs: add minimal documentation for
 [RFC PATCH v2 02/12] test: split variable settings to their own file
 [RFC PATCH v2 03/12] test/emacs: split out emacs related tests
 [RFC PATCH v2 04/12] test/emacs: write *Notmuch errors* buffer from
 [RFC PATCH v2 05/12] perf-test: allow running test_emacs from
 [RFC PATCH v2 06/12] perf-test: emacs tagging

The first six patches are not strictly needed for this feature, but
are reasonable changes I think.

 [RFC PATCH v2 07/12] emacs: remove non-batch code path from function

This is again not strictly needed, but makes further changes to this
code easier

 [RFC PATCH v2 08/12] emacs/tag: keep tag history
 [RFC PATCH v2 09/12] emacs: add notmuch-tag-undo

These add the actual undo.

             reply	other threads:[~2022-02-03 14:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 14:32 David Bremner [this message]
2022-02-03 14:32 ` [RFC PATCH v2 01/12] doc/emacs: add minimal documentation for notmuch-unthreaded mode David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 02/12] test: split variable settings to their own file David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 03/12] test/emacs: split out emacs related tests David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 04/12] test/emacs: write *Notmuch errors* buffer from test macro David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 05/12] perf-test: allow running test_emacs from performance test suite David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 06/12] perf-test: emacs tagging David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 07/12] emacs: remove non-batch code path from function notmuch-tag David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 08/12] emacs/tag: keep tag history David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 09/12] emacs: add notmuch-tag-undo David Bremner
2022-02-03 19:09   ` Miguel Bernabeu
2022-02-03 21:57     ` David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 10/12] emacs: redirect undo to notmuch-tag-undo David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 11/12] emacs: Document undo binding David Bremner
2022-02-03 14:32 ` [RFC PATCH v2 12/12] emacs: whitespace cleanup for keybindings David Bremner
2022-02-04 12:35   ` David Bremner

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=20220203143254.3344753-1-david@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.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).