unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: Johan Parin <johanparin@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Unread handling
Date: Mon, 11 Nov 2019 08:14:44 +0000	[thread overview]
Message-ID: <cuna792g77v.fsf@dme.org> (raw)
In-Reply-To: <m2zhh3jpa6.fsf@gmail.com>

On Monday, 2019-11-11 at 00:16:17 +01, Johan Parin wrote: 

> I'm probably doing something wrong but I find myself frustrated 
> with the handling of unread in the emacs-mua. 
> 
> In notmuch-search I found the default bold face for unread of 
> notmuch-search-unread-face not enough to make them stand out so 
> I tried something like 
> 
>   (setq notmuch-search-line-faces 
>       '(("unread" . '(:foreground "SkyeBlue")) 

   (setq notmuch-search-line-faces 
       '(("unread" :foreground "SkyeBlue")))

(And I don't have a “SkyeBlue”, just “SkyBlue”.) 

> which ought to work according to the doc, but did not 
> work. Fortunately however it works to define a new face with 
> defface and use that. 
> 
>   (setq notmuch-search-line-faces 
>         '(("unread" . my/notmuch-unread-face))) 
> 
> So that problem solved. 
> 
> My real frustration lies in the thread view. Typically threads 
> will be partially read and I want to read only unread messages. 
> 
> I find the show view confusing because I don't clearly see the 
> message boundaries. Also I always need to start with C-u M-RET 
> to get an overview of the thread. In this view the unread stand 
> out a bit due to the colorization of the unread tag, which is 
> typically visible. I still would like to be able to colorize the 
> entire line or the author here, for unread. Is it possible? 

The single-line summary of the message is drawn using 
notmuch-message-summary-face, which you can customise. This would 
be the same for all messages in the thread, though (no distinction 
for “unread”).

You could perhaps abuse notmuch-tag-formats to force unread 
message header lines to stand out more.
 
> I'm trying instead to use the tree view, this seems to me the 
> more natural way to view threads. So I immediately do `Z' 
> whenever I enter a thread. I would like to have the option to 
> enter tree view automatically for a thread from the search 
> buffer. Is it possible? 

“Z” in search mode should take you directly to tree mode.
 
> In tree view however, again I would like to colorize the unread 
> messages. Haven't found a way to do this and reading 
> notmuch-tree.el it seems it's not possible. Is there a way? 
> Since I like to keep my window to 80 chars the tag display is 
> outside the visible area and I find myself doing C-e to find the 
> unread tags. This is very inconvenient. 
> 
> Also I would like to navigate to the next unread message, and 
> would prefer the `n' binding to do that instead of go to next 
> message. Haven't found a binding for that. 
> 
> Finally when entering the tree view I would like the first 
> unread message to automatically be shown. 

I'm not a tree mode user, so I'm not familiar with it.
 
> I guess the above can be summarized as, I would like to have the 
> option to have a gnus-ish way of viewing threads. 

Tree mode is the closest, I think.
 
> Again, I'm probably doing something wrong and / or am missing 
> some possibilities here, it would be very interesting to hear 
> others work flow for thread reading. 

notmuch doesn't generally obsess about the “unread” tag quite as 
much as the “inbox” tag. Maybe you are used to orienting yourself 
around “unread” (which is important in Gnus, I'd agree) and 
thinking about how to look at “inbox” instead would help?

dme.
-- 
I was better off when I was on your side, and I was holding on.

  reply	other threads:[~2019-11-11  8:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 23:16 Unread handling Johan Parin
2019-11-11  8:14 ` David Edmondson [this message]
2019-11-12 13:17   ` William Casarin
2019-11-12 13:35     ` David Edmondson
2019-11-12 14:01       ` William Casarin
2019-11-12 13:53     ` Teemu Likonen
2019-11-12 13:59       ` William Casarin
2019-11-12 14:54         ` Teemu Likonen
2019-11-12 15:11           ` Teemu Likonen
2019-11-12 15:58             ` William Casarin
2019-11-11 15:57 ` Teemu Likonen
2019-11-12 18:45   ` Johan Parin

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=cuna792g77v.fsf@dme.org \
    --to=dme@dme.org \
    --cc=johanparin@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).