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/ _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
