From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] [PATCH] don't try to open the next thread if there isn't one available
Date: Wed, 30 Jan 2008 08:43:33 -0700 [thread overview]
Message-ID: <1201707688-sup-6637@tangerine.lanl.gov> (raw)
In-Reply-To: <1201681010-sup-3463@archie>
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
next prev parent reply other threads:[~2008-01-30 15:43 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 [this message]
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
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=1201707688-sup-6637@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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