unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: on deleting messages
Date: Tue, 17 Jan 2012 22:21:18 +0200	[thread overview]
Message-ID: <877h0qkrlt.fsf@nikula.org> (raw)
In-Reply-To: <87vcoaywyu.fsf@servo.finestructure.net>

On Tue, 17 Jan 2012 11:01:45 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> Now that Austin's excellent tag exclusion patch set [0] has been pushed,
> the question remains if we want to support any delete-handling key
> bindings in emacs.
> 
> Based on the show-mode improvements I recently sent [1], the following
> patch set implements thread and message delete keys.
> 
> This is the last I'm going to comment on this issue.  If we don't want
> to support this, we should put together something on the wiki that
> states we don't want to support it and that users should just bind it
> themselves (with a nice explanation how), so that we can try to reduce
> the number of future patches on the issue.
> 
> Given the number of patches we've had on this issue, though, it's clear
> that a lot of people expect this functionality, so we may want to
> seriously consider supporting it.  Given Austin's tag exclusion stuff,
> and the fact that "deleted" tags are excluded by default, we now have
> the functionality that Carl originally wanted to see, so it's not so
> unreasonable to support this functionality anymore.

I think it's reasonable to consider having key bindings (or other
special handling) for pretty much *any* tags that are special to
notmuch: inbox, unread, draft, flagged, etc. (An exhaustive list should
be documented somewhere.)

Looking at the source and history, I have to admit there has been
intent, and code, to have support for "deleted" tag. See for example
TODO or [1].

And I agree there has been demand for this.

I say let's have this.

But make it clear that "deleted" is just a tag; that the messages aren't
going away, not by notmuch anyway.


BR,
Jani.

[1] commit 2c262042ac174d7bc96d6035ab9c88bd0abe7f35

  parent reply	other threads:[~2012-01-17 20:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 19:01 on deleting messages Jameson Graef Rollins
2012-01-17 19:02 ` [PATCH 1/3] emacs: modify help message for notmuch-search-line-faces to reflect preferred "deleted" tag name Jameson Graef Rollins
2012-01-17 19:02   ` [PATCH 2/3] emacs: message/thread deletion by adding "deleted" tag Jameson Graef Rollins
2012-01-17 19:02     ` [PATCH 3/3] emacs: add delete key bindings for search and show mode Jameson Graef Rollins
2012-04-15 17:25   ` [PATCH 1/3] emacs: modify help message for notmuch-search-line-faces to reflect preferred "deleted" tag name Mark Walters
2012-04-15 17:39     ` Tomi Ollila
2012-04-15 20:06     ` Jameson Graef Rollins
2012-04-16  5:13       ` Tomi Ollila
2012-04-16  5:46         ` Jameson Graef Rollins
2012-04-16  7:02           ` Tomi Ollila
2012-04-25  2:30   ` David Bremner
2012-01-17 20:21 ` Jani Nikula [this message]
2012-01-18  7:30   ` on deleting messages Tomi Ollila
2012-01-17 22:31 ` Xavier Maillard
2012-01-18  7:44 ` Antoine Beaupré
2012-01-18  8:18 ` David Edmondson

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=877h0qkrlt.fsf@nikula.org \
    --to=jani@nikula.org \
    --cc=jrollins@finestructure.net \
    --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).