From mboxrd@z Thu Jan  1 00:00:00 1970
From: johnbent@lanl.gov (John Bent)
Date: Wed, 30 Jan 2008 08:43:33 -0700
Subject: [sup-talk] [PATCH] don't try to open the next thread if
	there	isn't one available
In-Reply-To: <1201681010-sup-3463@archie>
References: <1201681010-sup-3463@archie>
Message-ID: <1201707688-sup-6637@tangerine.lanl.gov>

Excerpts from its.jeff.balogh's message of Wed Jan 30 01:21:18 -0700 2008:
> 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 usually traverse my inbox with ',a', so it annoys me when sup gets stuck on
> the last thread.  This patch implements what I expect to happen: the thread is
> killed and the previous buffer pops up.
> 
Perhaps I should just change my habits but I like to traverse my inbox in
chronological order (i.e. bottom up instead of top down).  If anyone could 
make a patch that does ,a or ,n but moves it up instead of down, I'd very
much appreciate it.

By the way, I finally figured out what n and p are for in thread-view mode.
They are really very nice.  The auto-topping and auto-margin positioning are
very slick.

John