From: Carl Worth <cworth@cworth.org>
To: Dirk Hohndel <hohndel@infradead.org>, notmuch@notmuchmail.org
Subject: Re: The archive operation should only archive open messages
Date: Thu, 15 Apr 2010 18:51:32 -0700 [thread overview]
Message-ID: <8739ywf9ln.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <m3tyrc8lwm.fsf@x200.gr8dns.org>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
On Thu, 15 Apr 2010 14:07:37 -0700, Dirk Hohndel <hohndel@infradead.org> wrote:
> I am always confused about the behavior of 'a' - does it archive the
> current message? Or the current thread? Or the current thread down to
> where I am? Or (as you propose) just the open messages?
>
> I think we really need to spend some time to crsiply define the
> semantics of these commands.
I think the semantics have always been specified well, and
documented. Have you hit the '?' key to get a brief description of all
of the key bindings? Then you can also run `describe-key' ("C-h k" by
default) and then press a key to get even more thorough documentation.
If anything is not crisp enough there, please let me know and we'll fix
it right away.
I do agree that it's important for us to discuss what the ideal set of
operations is, and I don't claim that we have anything close to that in
the current implementation.
So that's why we're here talking I think. :-)
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-04-16 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 20:41 The archive operation should only archive open messages Carl Worth
2010-04-15 20:59 ` Jameson Rollins
2010-04-17 15:28 ` Carl Worth
2010-04-17 18:14 ` Dirk Hohndel
2010-04-15 21:07 ` Dirk Hohndel
2010-04-16 1:51 ` Carl Worth [this message]
2010-04-15 21:18 ` Jesse Rosenthal
2010-04-17 15:36 ` Carl Worth
2010-04-20 7:37 ` racin
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739ywf9ln.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=hohndel@infradead.org \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).