unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Daniel Schoepe <daniel.schoepe@googlemail.com>,
	Xavier Maillard <xma@gnu.org>,
	mueen@nawaz.org, notmuch@notmuchmail.org
Subject: Re: Header and other questions
Date: Mon, 16 May 2011 11:27:52 -0400	[thread overview]
Message-ID: <874o4uy8av.fsf@gogo.home> (raw)
In-Reply-To: <87vcxad6d6.fsf@gilead.home.box>


Hi,

On Mon, 16 May 2011 17:15:17 +0200, Daniel Schoepe <daniel.schoepe@googlemail.com> wrote:
> I think this is only a subset of the requested functionality, since one
> can only tag consecutive threads at once.

It seems like for non-consecutive messages to be tagged, there'd have to
be some sort of mutt-style message-marking facility. There was some
discussion when the feature was first introduced about whether to go
with region or marking. I think I wrote a quick version of both. (I just
checked -- that uncertainty is actually still there in the commit msg of
4c9585933 where the region feature comes in.)

The decision, if I remember correctly, was that regions are so intuitive
for emacs users, and many people reported trying to tag by region
without thinking about it, that this approach would make sense for the
emacs interface. In other words, keep the emacs interface emacsy. I
think I still agree with that, since I feel like having both would be
confusing (what do you do when you select a marked-line in a region?)
and I like the one I tend toward intuitively. But I certainly see the
benefit of the other functionality as well.

Best,
Jesse

  reply	other threads:[~2011-05-16 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15  5:23 Header and other questions mueen
2011-05-15 16:50 ` Daniel Kahn Gillmor
2011-05-15 17:15   ` mueen
2011-05-15 21:56 ` Xavier Maillard
2011-05-15 22:16   ` Jesse Rosenthal
2011-05-16 15:15     ` Daniel Schoepe
2011-05-16 15:27       ` Jesse Rosenthal [this message]
2011-05-16 16:29         ` Jameson Graef Rollins
2011-05-16 21:53           ` Xavier Maillard
2011-05-17  4:36           ` Mueen Nawaz
2011-05-17 10:59           ` Florian Friesdorf
2011-05-16  9:23 ` Sebastian Spaeth

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=874o4uy8av.fsf@gogo.home \
    --to=jrosenthal@jhu.edu \
    --cc=daniel.schoepe@googlemail.com \
    --cc=mueen@nawaz.org \
    --cc=notmuch@notmuchmail.org \
    --cc=xma@gnu.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).