unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Florian Friesdorf <flo@chaoflow.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	Jesse Rosenthal <jrosenthal@jhu.edu>,
	Daniel Schoepe <daniel.schoepe@googlemail.com>,
	Xavier Maillard <xma@gnu.org>,
	mueen@nawaz.org, notmuch@notmuchmail.org
Subject: Re: Header and other questions
Date: Tue, 17 May 2011 12:59:48 +0200	[thread overview]
Message-ID: <87zkmlegnv.fsf@eve.chaoflow.net> (raw)
In-Reply-To: <8762pabodc.fsf@servo.factory.finestructure.net>

[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]

On Mon, 16 May 2011 09:29:19 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Mon, 16 May 2011 11:27:52 -0400, Jesse Rosenthal <jrosenthal@jhu.edu> wrote:
> > 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.
> 
> I should mention that in my experience it's usually not that hard to
> construct searches (or filters on searches) that pair down to just the
> messages you want to tag, in which case you can just tag the entire
> buffer.

Maybe its more a question of key bindings:
1. add some special tag to messages
2. filter on this tag
3. do something with the whole buffer
4. remove special tag from all messages
5. close filter

I'd welcome a standard set of key bindings for it.

-- 
Florian Friesdorf <flo@chaoflow.net>
  GPG FPR: 7A13 5EEE 1421 9FC2 108D  BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: flo@chaoflow.net
IRC: chaoflow on freenode,ircnet,blafasel,OFTC

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  parent reply	other threads:[~2011-05-17 10:59 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
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 [this message]
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=87zkmlegnv.fsf@eve.chaoflow.net \
    --to=flo@chaoflow.net \
    --cc=daniel.schoepe@googlemail.com \
    --cc=jrollins@finestructure.net \
    --cc=jrosenthal@jhu.edu \
    --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).