From: "inwit" <inwit@sindominio.net>
To: "Jose Antonio Ortega Ruiz" <jao@gnu.org>, <notmuch@notmuchmail.org>
Subject: Re: [PATCH] emacs: add global tag history
Date: Thu, 27 Jan 2022 13:23:36 +0100 [thread overview]
Message-ID: <CHGGCHZR6CKE.1GVUJEEXTHMSF@bisio> (raw)
In-Reply-To: <87ee4u9yvk.fsf@gnus.jao.io>
On Wed Jan 26, 2022 at 6:43 PM CET, Jose Antonio Ortega Ruiz wrote:
> 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.
This sounds very much like it, yes. Would this need automatic update of
the buffer? If a message is deleted, for instance, an undo operation
should bring it back to the buffer, right?
Of course, this sort of modification is still far in my slow learner
horizon...
>
> 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
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
next prev parent reply other threads:[~2022-01-27 12:23 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
2022-01-27 12:23 ` inwit [this message]
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=CHGGCHZR6CKE.1GVUJEEXTHMSF@bisio \
--to=inwit@sindominio.net \
--cc=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).