From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Mark Walters <markwalters1009@gmail.com>,
Austin Clements <amdragon@MIT.EDU>
Cc: notmuch@notmuchmail.org
Subject: Re: [Patch v2 0/3] emacs: allow show to colour based on tags and flags
Date: Fri, 04 May 2012 07:22:21 -0700 [thread overview]
Message-ID: <877gwsrppe.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87txzw1otb.fsf@qmul.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]
On Thu, May 03 2012, Mark Walters <markwalters1009@gmail.com> wrote:
> There are a couple of extra reasons why I like the show ones
> separate. One is that I like to colour headerlines of matching messages to
> highlight them, but in search mode that would highlight every
> line. Secondly, I colour some things "negatively" in show mode: for
> example I show excluded messages in grey. This negative colouring does
> not make sense for search mode because I would only want to grey out
> results where all messages were excluded not results where at least one
> message is excluded. Of course we don't show entirely excluded threads
> in search, but similar comments apply to say the "replied" tag: I could
> show those in green (on the basis they are "dealt with") but I would not
> want a thread coloured green just because I have replied to one message
> in it.
Ok, that makes sense. Maybe there could be switch to inherit colors,
and then a way to set them independently as well.
>>> BTW, I like how this clearly distinguishes tags and flags. I wonder
>>> if we could transition to flags for some information that's current
>>> shoe-horned into tags but actually represents immutable information
>>> about a message (attachment, signed, and encrypted or so).
>>
>> Yes! As Austin probably remembers, we've discussed this before. I
>> definitely agree that it makes sense to somehow distinguish "immutable"
>> information that is a fundamental, unchanging/able property of the
>> message, and it might be nice to look ahead to that here.
>
> In essence I agree: my only concern is can the user search for these
> immutable things, and what syntax is used there.
Well, nothing exists yet so we can define it as we wish, but I would say
absolutely they should be searchable. That's an important part. They
just wouldn't be changable, like tags are, since they represent
immutable characteristics of the original message. I would suggest we
use something like "prop:" (for "property"), e.g. "prop:signed", or
"prop:attachment", etc.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-05-04 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 22:48 [Patch v2 0/3] emacs: allow show to colour based on tags and flags Mark Walters
2012-04-29 22:48 ` [Patch v2 1/3] emacs: Move colour line from search to lib Mark Walters
2012-04-29 22:48 ` [Patch v2 2/3] emacs: Add `notmuch-show-line-faces' and apply it Mark Walters
2012-05-05 11:45 ` Jani Nikula
2012-04-29 22:48 ` [Patch v2 3/3] emacs: allow notmuch-show-line-faces to use flags for colouring Mark Walters
2012-04-30 4:49 ` Tomi Ollila
2012-04-29 23:02 ` [Patch v2 0/3] emacs: allow show to colour based on tags and flags Austin Clements
2012-04-29 23:37 ` Mark Walters
2012-05-02 0:30 ` Jameson Graef Rollins
2012-05-04 5:46 ` Mark Walters
2012-05-04 14:22 ` Jameson Graef Rollins [this message]
2012-05-05 11:57 ` Jani Nikula
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=877gwsrppe.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=amdragon@MIT.EDU \
--cc=markwalters1009@gmail.com \
--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).