From: Jose Antonio Ortega Ruiz <jao@gnu.org>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: add global tag history
Date: Wed, 26 Jan 2022 17:43:11 +0000 [thread overview]
Message-ID: <87ee4u9yvk.fsf@gnus.jao.io> (raw)
In-Reply-To: <878rv2foky.fsf@wondoo.home.cworth.org>
On Wed, Jan 26 2022, Carl Worth wrote:
> On Wed, Jan 26 2022, inwit wrote:
>>> Even that will not be perfect (since the messages matching the query
>>> could change behind emacs back), but close enough for most interactive
>>> use, maybe?
>>
>> I was thinking about saving the IDs of the messages affected by the
>> change, but I still don't know how would I go about that or if it's
>> sensible.
>
> One could imagine a history that would enable a conventional undo stack
> for a notmuch interface. The trick with making that usable would be the
> need to refresh views to make what was undone evident, (and the fact
> that some of the operations could be large/slow).
>
> All of those issues kept me from pursuing the idea in early days of
> coding up the emacs notmuch UI. But someone could certainly explore the
> implementation further if desired.
maybe this could be a buffer-local history variable, for notmuch search
and tree search buffers, and the undo feature apply only to the current
search buffer. the view update is then well-defined, i think, if it's
just changing tags, at least, and per-buffer operation is the normal
behaviour of undo/redo in emacs. hooking that up with the regular emacs
undo/redo mechanism would be great (in my book at least), but i've never
looked at that, so not sure if it's possible.
cheers,
jao
--
Keep away from people who try to belittle your ambitions. Small people
always do that, but the really great make you feel that you, too, can
become great. - Mark Twain
next prev parent reply other threads:[~2022-01-26 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 15:32 [PATCH] emacs: add global tag history inwit
2022-01-26 15:40 ` David Bremner
2022-01-26 16:08 ` inwit
2022-01-26 16:29 ` Carl Worth
2022-01-26 17:43 ` Jose Antonio Ortega Ruiz [this message]
2022-01-27 12:23 ` inwit
2022-01-26 17:48 ` David Bremner
2022-01-26 18:00 ` David Bremner
2022-01-27 12:28 ` David Bremner
2023-01-06 11:36 ` David Bremner
2023-01-10 15:29 ` inwit
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=87ee4u9yvk.fsf@gnus.jao.io \
--to=jao@gnu.org \
--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).