From: kevin.mark@verizon.net (Kevin Mark)
Subject: [sup-talk] Feature request
Date: Mon, 1 Oct 2007 03:14:03 -0400 [thread overview]
Message-ID: <20071001071403.GB21869@horacrux> (raw)
Hi,
I was finally thinking about what I think is a good workflow or at least
one that parallels mutt, which is the other MUA that I use. In SUP, I
think the best feature to add would be this:
having 'A' (which is used to archive the currently viewed message and
then send the user back to the main view) and instead of having it exit
to the main view, have it proceed to the next unread message.
This would allow folks to just press 'A' many times while cycling
through many unread messages.
-K
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keyserver: subkeys.pgp.net | my NPO: cfsg.org |
|join the new debian-community.org to help Debian! |
|_______ Unless I ask to be CCd, assume I am subscribed _______|
next reply other threads:[~2007-10-01 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 7:14 Kevin Mark [this message]
2007-10-04 16:20 ` 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=20071001071403.GB21869@horacrux \
--to=kevin.mark@verizon.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