Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] don't try to open the next thread if there isn't one available
Date: Sat, 02 Feb 2008 20:31:00 -0800	[thread overview]
Message-ID: <1202012826-sup-1965@south> (raw)
In-Reply-To: <1201681010-sup-3463@archie>

Reformatted excerpts from its.jeff.balogh's message of 2008-01-30:
> When you're on the last thread of a ThreadSet and press ',<key>',
> nothing happens, but you can't '.<key>' since @dying == true.  This
> patch changes :next to :kill if there is no next thread.

I made a parallel change to do this:
e47f9dabca0349a1fff046232961b38d900d4445. It's all withing
ThreadIndexMode#launch_next_thread_after, which I think is a little
cleaner.

As I mentioned in the previous email, I also just changed these
operations so that they don't automatically save state to disk, so as to
be consistent with the rest of Sup.

-- 
William <wmorgan-sup at masanjin.net>


      parent reply	other threads:[~2008-02-03  4:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  8:21 Jeff Balogh
2008-01-30 15:43 ` John Bent
2008-02-05 17:27   ` William Morgan
2008-02-06 16:21     ` John Bent
2008-01-30 23:05 ` Jeff Balogh
2008-02-03  4:35   ` William Morgan
2008-02-03  4:31 ` 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=1202012826-sup-1965@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