From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>, Austin Clements <amdragon@MIT.EDU>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: RFC: tag macros
Date: Wed, 18 Jan 2012 11:28:09 -0800 [thread overview]
Message-ID: <87obu0q08m.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87wr8o7rzb.fsf@rocinante.cs.unb.ca>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Wed, 18 Jan 2012 15:03:52 -0400, David Bremner <david@tethera.net> wrote:
> My main motivation here is (as you can probably see from the example)
> dealing with patches, and in that setting, tagging the whole thread is
> is almost never what you want.
The example I sent was about tagging individual message, not threads.
> That aside, thread tagging is already there in search view, and I guess
> could be done by selecting the whole thread and tagging that region.
Thread tagging would be supported in show mode with the recent
notmuch-show-{add,remove}-tag-thread patches I sent:
id:"1326823531-14549-1-git-send-email-jrollins@finestructure.net"
> I haven't really looked at how to apply tags to regions in
> notmuch-show-mode. Is there code around that does that? Or more
> generally iterate over messages in a region?
I don't think the show mode tagging functions support regions at the
moment, but I think extending them to do that would be a good idea.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-01-18 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 14:45 RFC: tag macros David Bremner
2012-01-18 15:04 ` David Edmondson
2012-01-18 18:33 ` Austin Clements
2012-01-18 19:03 ` David Bremner
2012-01-18 19:11 ` Austin Clements
2012-01-18 19:28 ` Jameson Graef Rollins [this message]
2012-01-18 18:50 ` Jameson Graef Rollins
2012-01-19 0:04 ` David Bremner
2012-01-19 2:15 ` Jameson Graef Rollins
2012-01-19 2:37 ` David Bremner
2012-01-19 13:10 ` 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=87obu0q08m.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=amdragon@MIT.EDU \
--cc=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).