On Tue, 10 Jan 2012 16:01:32 -0400, David Bremner <david@tethera.net> wrote:
> Just thinking out loud here, but it does seem a bit unfortunate to me
> that it represents a pretty fundamental divergence between the CLI and
> the emacs interface. Mind you, I guess one could make the same argument
> about the libs versus the CLI. Lack of configuration information in the
> library (possibly among other reasons) makes this not too nice to
> support in the current library either.
I think a consensus has formed that this functionality (automatically
suppressing messages with certain tags from searches) is better left to
the CLI, rather than implementing it just in the emacs UI.
Unfortunately I'm not going to get to that any time soon.
However, without that functionality, I really see no reason why we
should be adding any built-in support for adding "deleted" tags in the
emacs UI. Without the CLI change, "deleted" tags aren't handled any
differently than any other tag, so why should the default emacs UI care.
If users want to bind keys to special tagging operations, they can do so
for themselves [0].
In fact, I'm now starting to think we don't need to add any support for
special tagging operations (such as "deleted") even if we *do* have
support for suppressing them in the CLI. Special tagging operations
should only be supported if the tagged messages are somehow handled
specially. If not, then again, we should just leave them up to the user
[0].
All that said, I think I'll just resubmit the couple small changes to
the emacs UI that I think we should consider adopting anyway.
jamie.
[0]
(define-key notmuch-show-mode-map "d"
(lambda ()
"Delete message"
(interactive)
(notmuch-show-add-tag "deleted")
(notmuch-show-next-open-message)))