From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 6DB356DE0C51 for ; Mon, 11 Nov 2019 00:14:50 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.285 X-Spam-Level: X-Spam-Status: No, score=0.285 tagged_above=-999 required=5 tests=[AWL=-0.367, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8oyoSyrliS4t for ; Mon, 11 Nov 2019 00:14:49 -0800 (PST) Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) by arlo.cworth.org (Postfix) with ESMTPS id 4D2916DE0240 for ; Mon, 11 Nov 2019 00:14:49 -0800 (PST) Received: by mail-wr1-f53.google.com with SMTP id f2so13477862wrs.11 for ; Mon, 11 Nov 2019 00:14:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dme-org.20150623.gappssmtp.com; s=20150623; h=to:subject:in-reply-to:references:from:date:message-id:mime-version :content-transfer-encoding; bh=1kHLG7fImBOhsVBwZFm0GC6cJTzhCLTqvXhlxeawLug=; b=sLC6x98V/RiZcPLBY0RGAtltxxmZoe0NN3k5TB7AbIia5LyMsjxH2FsUb6tb02fl5G qFEkTb6SmeHiOSqrB12bFax3IOHArwLHcvnZlgF4ZE+C7UKP1V7ZS6t04DKdkUHcJ+SG 03Ycp9svtxClQMncjNS8gEO9CFIypGIjZs7caX/937oZretXFpg9Yjb6dg5KGXOAySym 3+8TlXywL+4Z8wtC/MIpZ0UqbU/gI1jmp1vHjvL9WIHY426WoxwpaDhZvABC5Y7v6DSI byhRiupo35RCxjHkEBw4pKM8EuE8PDpmzop0vdKjS988UCtUKEp2k4FqN3qt+TVPueQn RaYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:subject:in-reply-to:references:from:date :message-id:mime-version:content-transfer-encoding; bh=1kHLG7fImBOhsVBwZFm0GC6cJTzhCLTqvXhlxeawLug=; b=gVrHUZgCjvAajrlVesg+3N3YaGoepc/JpuID/40ygxnKMFH/J1sTo95k+wzpSQjzt4 NOBcVrmJNdwYhdPQkLZLh7fapeG57N6RhLkFbsK8Yg54GZjnAjBKLDiC+jXp5S0FkFLu 57LX9esvukbUQyoAuZZuY2uDuPPir649AY8kzwuqgtpO95uFKAPQYfovvP2azqnOnWWJ KPkKLV6BBj9Ls9QrNtcG/5Sl4nf6CedxBKnZNEL8wQuJXKcntKI8y3WyFCdl+mT+2fpd yTUV4duyWHCx+Y9VxP5FvHgXZSYPKuUGgN8LeqeQEGZ4deynndazWz9U6a3xzfGV1nUP P7Jw== X-Gm-Message-State: APjAAAXU4/8E+/hxpkC6bZhlsoi36JXIDuIWp0r4XNLj8eyTtg8sxKR8 JV5Mr6o3TEspvLW3RE+ttXlvjg== X-Google-Smtp-Source: APXvYqzhx4b/NtrONVw3GT5HMf1+6iwiyKnZL3R39Rzvw1jscrKORbwmSfSY1kf1JISRm/kE3ptv/A== X-Received: by 2002:a5d:522e:: with SMTP id i14mr7108133wra.27.1573460086355; Mon, 11 Nov 2019 00:14:46 -0800 (PST) Received: from disaster-area.hh.sledj.net (disaster-area.hh.sledj.net. [81.149.164.25]) by smtp.gmail.com with ESMTPSA id j7sm3904260wro.54.2019.11.11.00.14.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Nov 2019 00:14:45 -0800 (PST) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id 1b2f1362; Mon, 11 Nov 2019 08:14:44 +0000 (UTC) To: Johan Parin , notmuch@notmuchmail.org Subject: Re: Unread handling In-Reply-To: References: X-HGTTG: gag-halfrunt From: David Edmondson Date: Mon, 11 Nov 2019 08:14:44 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2019 08:14:50 -0000 On Monday, 2019-11-11 at 00:16:17 +01, Johan Parin wrote:=20 > I'm probably doing something wrong but I find myself frustrated=20 > with the handling of unread in the emacs-mua.=20 >=20 > In notmuch-search I found the default bold face for unread of=20 > notmuch-search-unread-face not enough to make them stand out so=20 > I tried something like=20 >=20 > (setq notmuch-search-line-faces=20 > '(("unread" . '(:foreground "SkyeBlue"))=20 (setq notmuch-search-line-faces=20 '(("unread" :foreground "SkyeBlue"))) (And I don't have a =E2=80=9CSkyeBlue=E2=80=9D, just =E2=80=9CSkyBlue=E2=80= =9D.)=20 > which ought to work according to the doc, but did not=20 > work. Fortunately however it works to define a new face with=20 > defface and use that.=20 >=20 > (setq notmuch-search-line-faces=20 > '(("unread" . my/notmuch-unread-face)))=20 >=20 > So that problem solved.=20 >=20 > My real frustration lies in the thread view. Typically threads=20 > will be partially read and I want to read only unread messages.=20 >=20 > I find the show view confusing because I don't clearly see the=20 > message boundaries. Also I always need to start with C-u M-RET=20 > to get an overview of the thread. In this view the unread stand=20 > out a bit due to the colorization of the unread tag, which is=20 > typically visible. I still would like to be able to colorize the=20 > entire line or the author here, for unread. Is it possible?=20 The single-line summary of the message is drawn using=20 notmuch-message-summary-face, which you can customise. This would=20 be the same for all messages in the thread, though (no distinction=20 for =E2=80=9Cunread=E2=80=9D). You could perhaps abuse notmuch-tag-formats to force unread=20 message header lines to stand out more. =20 > I'm trying instead to use the tree view, this seems to me the=20 > more natural way to view threads. So I immediately do `Z'=20 > whenever I enter a thread. I would like to have the option to=20 > enter tree view automatically for a thread from the search=20 > buffer. Is it possible?=20 =E2=80=9CZ=E2=80=9D in search mode should take you directly to tree mode. =20 > In tree view however, again I would like to colorize the unread=20 > messages. Haven't found a way to do this and reading=20 > notmuch-tree.el it seems it's not possible. Is there a way?=20 > Since I like to keep my window to 80 chars the tag display is=20 > outside the visible area and I find myself doing C-e to find the=20 > unread tags. This is very inconvenient.=20 >=20 > Also I would like to navigate to the next unread message, and=20 > would prefer the `n' binding to do that instead of go to next=20 > message. Haven't found a binding for that.=20 >=20 > Finally when entering the tree view I would like the first=20 > unread message to automatically be shown.=20 I'm not a tree mode user, so I'm not familiar with it. =20 > I guess the above can be summarized as, I would like to have the=20 > option to have a gnus-ish way of viewing threads.=20 Tree mode is the closest, I think. =20 > Again, I'm probably doing something wrong and / or am missing=20 > some possibilities here, it would be very interesting to hear=20 > others work flow for thread reading.=20 notmuch doesn't generally obsess about the =E2=80=9Cunread=E2=80=9D tag qui= te as=20 much as the =E2=80=9Cinbox=E2=80=9D tag. Maybe you are used to orienting yo= urself=20 around =E2=80=9Cunread=E2=80=9D (which is important in Gnus, I'd agree) and= =20 thinking about how to look at =E2=80=9Cinbox=E2=80=9D instead would help? dme. --=20 I was better off when I was on your side, and I was holding on.