From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Search all threads with option to cancel
Date: Wed, 16 Jan 2008 13:09:36 -0800 [thread overview]
Message-ID: <1200517677-sup-7041@south> (raw)
In-Reply-To: <1200480144-sup-10@tomsk>
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 <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-01-16 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 17:20 [sup-talk] [PATCH] (Double/guarded) keypress to show all threads Marcus Williams
2008-01-13 5:30 ` William Morgan
2008-01-13 15:57 ` Nicolas Pouillard
2008-01-13 18:16 ` Marcus Williams
2008-01-14 1:06 ` William Morgan
2008-01-14 10:54 ` Marcus Williams
2008-01-15 4:49 ` William Morgan
2008-01-15 12:29 ` [sup-talk] [PATCH] Search all threads with option to cancel Marcus Williams
2008-01-16 4:30 ` William Morgan
2008-01-16 10:47 ` Marcus Williams
2008-01-16 21:09 ` William Morgan [this message]
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=1200517677-sup-7041@south \
--to=wmorgan-sup@masanjin.net \
/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