From: "inwit" <inwit@sindominio.net>
To: "Tomi Ollila" <tomi.ollila@iki.fi>, <notmuch@notmuchmail.org>
Subject: Re: Repeat last tagging
Date: Wed, 14 Jul 2021 15:01:23 +0200 [thread overview]
Message-ID: <CCSVS3V8THJZ.2GCNM09WYAZGE@bisio> (raw)
In-Reply-To: <m2czrlfdrp.fsf@guru.guru-group.fi>
On Wed Jul 14, 2021 at 11:25 AM CEST, Tomi Ollila wrote:
> On Wed, Jul 14 2021, inwit@sindominio.net wrote:
> It does, what it would require is saving last-tag-change to a variable
> and then bind function to a key...
Put that way, it sounds pretty straightforward...
> I personally am not too interested for such a binding (It could be
> "dangerous" to do accidental undesired change (but I also could be
> wrong and like such a feature >;D)
My current alternative is of course hit 'CTRL+p' after '+', retrieving the
last tags in the minibuffer's memory. I guess I'll survive with that.
> for reference I have the following bindings added to my configuration
> file
>
> (define-key notmuch-show-user-map "u"
> (lambda () "mark message unread" (interactive)
> (notmuch-show-tag-message "+unread")))
>
> (define-key notmuch-show-user-map "i"
> (lambda () "remove inbox tag" (interactive)
> (notmuch-show-tag-message "-inbox")))
>
> which means uu restores "unread" and ui removes "inbox".
Sounds handy, I'll try it.
>
> storing last-tag-change may provide hard if there
> is no central place to execute "notmuch tag" command in notmuch emacs
> source code...
You mean we would need to modify every call to "notmuch tag" in the
code, in order to save last-tag-change in a variable which is accesible
in every other scope?
It's my first dive into the code, thanks for your patience.
Regards,
>
>
> Tomi
>
> > I know I could perform a search for all the emails that I need
> > to tag and tag them all at the same time, but the criteria to select
> > them is usually not obvious. Another option would be to be able to mark
> > emails, then tag them (I've seen the emacs-region thing, but it's not
> > the same).
> >
> > Thanks in advance. And cheers again for the good work!
> >
> > Regards,
> > _______________________________________________
> > notmuch mailing list -- notmuch@notmuchmail.org
> > To unsubscribe send an email to notmuch-leave@notmuchmail.org
next prev parent reply other threads:[~2021-07-14 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 8:41 Repeat last tagging inwit
2021-07-14 9:25 ` Tomi Ollila
2021-07-14 13:01 ` inwit [this message]
[not found] ` <87sg0gvo1r.fsf@wobbit.home.cworth.org>
2021-07-15 8:08 ` inwit
2022-01-20 16:36 ` 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=CCSVS3V8THJZ.2GCNM09WYAZGE@bisio \
--to=inwit@sindominio.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).