Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] Search all threads with option to cancel
Date: Wed, 16 Jan 2008 10:47:39 +0000	[thread overview]
Message-ID: <1200480144-sup-10@tomsk> (raw)
In-Reply-To: <1200457554-sup-9055@south>

On 16.1.2008, William Morgan wrote:
> I think you should split this into two patches, the first of which adds
> the ability to stop any current thread-loading operation, and the second
> of which gives you the "load everything now" button. I'd like to
> evaluate each one independently.

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.

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?

> I think I'd like the stop loading button to be ^G, which is the general
> cancel command everywhere in Sup. The load everything now button can be
> a scary multi-key sequence like "!!".
> 

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.

Marcus


  reply	other threads:[~2008-01-16 10:47 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 [this message]
2008-01-16 21:09                 ` William Morgan

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=1200480144-sup-10@tomsk \
    --to=marcus-sup@bar-coded.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