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, 06 Feb 2008 09:21:37 -0700 [thread overview]
Message-ID: <1202314746-sup-2532@tangerine.lanl.gov> (raw)
In-Reply-To: <1202232384-sup-1186@south>
Excerpts from William Morgan's message of Tue Feb 05 10:27:26 -0700 2008:
> Reformatted excerpts from John Bent's message of 2008-01-30:
> > 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.
>
> I do this too, often. Try ']' in next.
>
That's great! Thanks.
> I really need a better keybinding. Wonder if I just should bite the
> bullet and do < and > for previous and next instead of , and ].
>
That'd be nice too (and probably more intuitive). Or maybe it's really
hard but user-defined macros or shortcuts. So people could map
< to ,n and > to ]n. Or did I get the order wrong? Also, if we had
macros, I'd map something to |muttprint.
next prev parent reply other threads:[~2008-02-06 16:21 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 [this message]
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=1202314746-sup-2532@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