Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: marianne.promberger+sup-talk@gmail.com (Marianne)
Subject: [sup-talk] Availability of key presses in different modes
Date: Thu, 08 Jan 2009 20:51:37 +0100	[thread overview]
Message-ID: <1231444262-sup-3650@audrey> (raw)

Hi,

Is there a specific reason why certain key presses are not available in some
modes?

I'm thinking specifically about using "&" to kill a thread from thread-view
mode, and of "A" or "a" to archive a thread from search-results-mode.

The first would save me killing the buffer before killing the thread, since I
sometimes have to at least glance at a thread before deciding I want to kill it.

The second is much more important, really. I go through mail by mailing list, so
I use "L" to search for mail with a specific label. It seems I cannot then
archive threads from that view. Am I missing something? 

Thanks,

Marianne

-- 
Marianne Promberger
PGP/GnuPG public key ID 80AD9916


             reply	other threads:[~2009-01-08 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 19:51 Marianne [this message]
2009-01-13 23:36 ` Daniel Wagner
2009-01-14 18:13   ` Marianne

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=1231444262-sup-3650@audrey \
    --to=marianne.promberger+sup-talk@gmail.com \
    /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