Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: me@nicholasbs.net (Nicholas Bergson-Shilcock)
Subject: [sup-talk] [PATCH] Add 'a' and 'd' keybindings to thread-view-mode to archive/delete current thread
Date: Thu, 03 Sep 2009 14:58:45 -0400	[thread overview]
Message-ID: <1252004295-sup-6234@twoface> (raw)
In-Reply-To: <1252002852-sup-8688@r50p>

Excerpts from Mark Alexander's message of Thu Sep 03 14:37:34 -0400 2009:
> Excerpts from William Morgan's message of Thu Sep 03 14:06:55 -0400 2009:
> > I guess if most people primarily closes their thread-view-modes using
> > ",a" and ",d", then I'm fine with this.
> 
> Those are perhaps my most-commonly used commands in sup, so having
> them shortened is a very nice improvement.

+1. These would be quite helpful for me.


  reply	other threads:[~2009-09-03 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 22:40 Carl Worth
2009-09-03 18:06 ` William Morgan
2009-09-03 18:37   ` Mark Alexander
2009-09-03 18:58     ` Nicholas Bergson-Shilcock [this message]
2009-09-06 19:43   ` Nicolas Pouillard
2009-09-08 20:26     ` Carl Worth
2009-09-08 20:33       ` Nicolas Pouillard
2009-09-08 15:17   ` Wirt Wolff
2009-09-08 20:08     ` William Morgan
2009-09-09 14:37       ` 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=1252004295-sup-6234@twoface \
    --to=me@nicholasbs.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