Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <>
Subject: Re: feature request: differentiate between read and automatically marked read
Date: Thu, 03 Feb 2022 13:34:36 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <87r18k85kj.fsf@dick>

On Thursday,  3 Feb 2022 at 08:04, dick wrote:
> In either case, it's semantic-free tallying.

It is.  Yes, semantic based logic could arguably be "better" but sorting
without semantics can be useful.  Would I make any claims about it
always working?  No, but what matters (to me) is that it works in
practice for my use case.  YMMV, of course.

> I know of no companies, Google-scale or otherwise, who have stood behind
> an algo that opines about the read-worthiness of one's mail unless the
> mail is 99.98% probable spam.

So what?  Absence of evidence is not evidence of absence... ;-)

Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2

  reply	other threads:[~2022-02-03 13:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  8:50 Eric S Fraga
2022-02-03  9:10 ` Eric S Fraga
2022-02-03 12:26 ` dick
2022-02-03 12:38   ` Tassilo Horn
2022-02-03 13:04     ` dick
2022-02-03 13:34       ` Eric S Fraga [this message]
2022-02-03 12:50   ` Eric S Fraga
2022-02-05  8:51     ` Uwe Brauer
2022-02-05  9:29       ` Eric S Fraga
2022-02-05 10:36         ` Uwe Brauer
2022-02-07 12:28           ` Eric S Fraga

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.
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 NNTP newsgroup(s).