From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] use-mail branch and other work
Date: Mon, 31 Mar 2014 22:57:06 +0200 [thread overview]
Message-ID: <1396299131-sup-5113@qwerzila> (raw)
In-Reply-To: <1396294116-sup-6519@kpad>
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
Excerpts from Matthieu Rakotojaona's message of 2014-03-31 21:42:57 +0200:
> Excerpts from Martin Bähr's message of 2014-03-30 11:51:43 +0200:
> > some ideas:
> > i'd like the ability to apply a label change to all messages that match a
> > given search, not just the ones loaded into the buffer.
> >
> > i have imported a lot of uncategorized messages from my mutt inbox, and i
> > want to make use of sup's tagging to group them. instead of loading all
> > messages in a search with !! it would be nice to just let sup tagg those
> > messages in the background.
>
> Semi-answer: bin/sup-tweak-labels is this, except it's supposed to be
> used from the command line. Moreover you must exit sup because the index
> can't be shared safely.
> Since Sup is mostly targeted towards the ui and that use case happen
> once in the lifetime of a user (hopefully !), I guess I'm ok with how
> things are. I don't know how we could manage to reproduce the
> bin/sup-tweak-labels _inside_ sup efficiently, but I'm open to the
> discussion.
We could do something similar to what tagging and + does now, but
iterate over all the threads in the search without rendering them.
Unless the chunks are loaded it is a matter of loading it from the
index. It would be an extension to thread-index mode. Basically a
command: Apply an action to all threads matching the current search. It
will be the equivalent of: Search + show all (!!) + tag all +
do action.
- gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-31 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 9:51 Martin Bähr
2014-03-30 20:47 ` Steven Schmeiser
2014-03-31 12:02 ` Gaute Hope
2014-03-31 12:09 ` Gaute Hope
2014-04-01 4:13 ` Martin Bähr
2014-03-31 19:42 ` Matthieu Rakotojaona
2014-03-31 20:57 ` Gaute Hope [this message]
2014-04-01 3:55 ` Martin Bähr
2014-04-01 3:46 ` Martin Bähr
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1396299131-sup-5113@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox