From: Mueen Nawaz <mueen@nawaz.org>
To: notmuch@notmuchmail.org
Subject: Re: Header and other questions
Date: Mon, 16 May 2011 21:36:28 -0700 [thread overview]
Message-ID: <87aaemt037.fsf@fester.com> (raw)
In-Reply-To: 8762pabodc.fsf@servo.factory.finestructure.net
Jameson Graef Rollins
<jrollins@finestructure.net> writes:
> 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.
I guess so. I still haven't really switched to notmuch for real mail so
I have little experience. I don't quite remember why I would have found
it handy when I wrote it, but it was while I was busy experimenting with
tagging my existing archive.
next prev parent reply other threads:[~2011-05-17 4:45 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 [this message]
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=87aaemt037.fsf@fester.com \
--to=mueen@nawaz.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).