From: Mark Anderson <MarkR.Anderson@amd.com>
To: Xavier Maillard <xma@gnu.org>,
Jesse Rosenthal <jrosenthal@jhu.edu>,
"notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Bulk message tagging
Date: Mon, 12 Apr 2010 11:41:00 -0600 [thread overview]
Message-ID: <3wd7hoc36xf.fsf@testarossa.amd.com> (raw)
In-Reply-To: <m2wrwf76n3.fsf@deb.maillard.im>
On Sat, 10 Apr 2010 08:56:48 -0500, Xavier Maillard <xma@gnu.org> wrote:
> Hi,
>
> On Tue, 6 Apr 2010 13:51:01 -0600, Mark Anderson <MarkR.Anderson@amd.com> wrote:
> >
> > I think that '*' is definitely an awesome command, but I wonder if we
> > shouldn't have another command for the notmuch-search buffer which means
> > 'tag all the threads that I can see in this buffer'.
>
> This is exactly what my initial post asked for. '*' is not
> totally satisfying for me due to the "limitations" you
> exposed. Though It is a good and acceptable workaround for me.
> As said, I just have to pay attention to redo my search query
> before pressing the '*' key.
Another problem I have is that I often _don't_ want to refresh my
search. Some of my mail processing, while not visible in the search
window, since we don't have a way to refresh tags yet, will remove some of
the current search results from matching the search query.
For example, I like to have notmuch folder definitions with "tag:unread"
in them. For those search views, once I've looked at any of the mails,
they no longer match the query. Sometimes I want to refresh the search
so that those mails are no longer visible, sometimed I want to apply an
action on all the visible messages which I've just processed.
When I visit a folder view, what intent do I have? Am I returning to a
'moment-ago' processing view that was interrupted? Or am I wanting to
do the search again on the current contents of the database? I could
easily see mental models that match either way.
I think I read that Carl plans to update the tags in a search view at
some point, without removing threads automatically.
Perhaps there ought to be a way to colorize threads which are displayed
but no longer match the search criterion?
-Mark
next prev parent reply other threads:[~2010-04-12 18:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 4:37 Bulk message tagging Xavier Maillard
2010-04-04 4:56 ` Jason White
2010-04-04 5:27 ` Xavier Maillard
2010-04-04 5:46 ` Jason White
2010-04-05 6:19 ` Xavier Maillard
2010-04-04 11:38 ` Jesse Rosenthal
2010-04-05 6:15 ` Xavier Maillard
2010-04-05 6:44 ` Jason White
2010-04-06 19:51 ` Mark Anderson
2010-04-10 13:56 ` Xavier Maillard
2010-04-12 17:41 ` Mark Anderson [this message]
2010-04-15 0:59 ` Carl Worth
2010-04-15 20:04 ` Jesse Rosenthal
2010-04-15 20:17 ` Jesse Rosenthal
2010-04-16 1:46 ` Carl Worth
2010-04-16 11:47 ` Jesse Rosenthal
2010-04-17 15:43 ` Carl Worth
2010-04-19 8:58 ` David Edmondson
2010-04-16 13:57 ` Servilio Afre Puentes
-- strict thread matches above, loose matches on Subject: below --
2010-04-17 18:32 Arian Kuschki
2010-04-21 23:02 ` Carl Worth
2010-04-23 20:05 ` Mark Anderson
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=3wd7hoc36xf.fsf@testarossa.amd.com \
--to=markr.anderson@amd.com \
--cc=jrosenthal@jhu.edu \
--cc=notmuch@notmuchmail.org \
--cc=xma@gnu.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).