From: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] use-mail branch and other work
Date: Tue, 01 Apr 2014 05:55:12 +0200 [thread overview]
Message-ID: <1396324091-sup-9960@email.archlab.tuwien.ac.at> (raw)
In-Reply-To: <1396299131-sup-5113@qwerzila>
Excerpts from Gaute Hope's message of 2014-03-31 22:57:06 +0200:
> 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.
yes, that's how i imagined to use it.
btw: do action for all tagged blocks. with a few threads tagged or on a fast
machine it's not noticable, but on a slower machine it is.
if the above is solved to run in the background, then the current do action for
all tagged, could use the same mechanism. it is just a matter of which list of
threads/messages the function receives to operate on:
search + tag some messages + do action on tagged -> call action with list of tagged messages.
search + do action on search -> call action with list of matching messages.
same function for both, return to view immideately, maybe update view when function completes
greetings, martin.
--
eKita - the online platform for your entire academic life
hackerspace beijing - http://qike.info
--
chief engineer eKita.co
pike programmer pike.lysator.liu.se caudium.net societyserver.org
BLUG secretary beijinglug.org
foresight developer foresightlinux.org realss.com
unix sysadmin
Martin Bähr working in china http://societyserver.org/mbaehr/
next prev parent reply other threads:[~2014-04-01 3:55 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
2014-04-01 3:55 ` Martin Bähr [this message]
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=1396324091-sup-9960@email.archlab.tuwien.ac.at \
--to=mbaehr@email.archlab.tuwien.ac.at \
--cc=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