From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Wed, 16 Jan 2008 13:09:36 -0800 Subject: [sup-talk] [PATCH] Search all threads with option to cancel In-Reply-To: <1200480144-sup-10@tomsk> References: <1200071751-sup-5552@tomsk> <1200201168-sup-5812@south> <1200247733-sup-3710@tomsk> <1200272179-sup-6412@south> <1200307947-sup-1357@tomsk> <1200372469-sup-1813@south> <1200400125-sup-5900@tomsk> <1200457554-sup-9055@south> <1200480144-sup-10@tomsk> Message-ID: <1200517677-sup-7041@south> Reformatted excerpts from Marcus Williams's message of 2008-01-16: > At the moment isnt the only thread-loading operation the > load_n_threads method in thread-index-view? All the possibly long > running operations that run threads that I can think of end up going > through this as far as I can see. Yes. > So do you want a patch for interrupting the load threads method, and > then a patch to add the potentially long running load_all_threads? Precisely. > Ok, easily done - I didnt use ^G originally because I thought you > couldnt overload a key action in a mode and I though ^G was added > elsewhere. In general that is more or less true, but ^G is only caught by the top-level event handler (which we override every time we define a mode-specific keyboard command), and by the text entry stuff, which does its own keyboard handling routine. So I think you should be fine. -- William