From: Uwe Brauer <firstname.lastname@example.org>
Subject: Re: feature request: differentiate between read and automatically marked read
Date: Sat, 05 Feb 2022 11:36:47 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
>>> "ESF" == Eric S Fraga <firstname.lastname@example.org> writes:
> On Saturday, 5 Feb 2022 at 09:51, Uwe Brauer wrote:
>> That is to say you score according to their email address? I am
>> extremely interested in such a configuration, since I right now need it.
>> Would you mind sharing (off list if necessary)
> This is actually the one easy bit about scoring. In the summary buffer,
> if there is an email from somebody that you want to have scored high,
> C-u NNN I a r p REGEXP-FOR-EMAIL-ADDRESS RET
> where NNN is the adjustment to the score you want to assign to the
> person's email, "I" means "increase score", "a" means "address", "r"
> means regular expression for matching (you can use exact matching if you
> wish), "p" for permanent storing the score, and lastly the regular
> expression for matching emails from that person which will be pre-filled
> with the address of the current email in the summary buffer.
> For my PhD students, I use 1000 for the adjustment to the score.
> If you use L instead of I, you lower the score for those you don't want
> to see (or you deem as less important).
Thanks very much!!
Fortunately the email is offered when running this, oops cumbersome
command. I tried it out with our email of course. 🙃
Your messages are then in bold face (did you fiddle the setting of the
display variable you mentioned earlier?)
BTW I wish that scoring would it a bit easier to set up, what you sent
me I shall copy in one of my important registers (I use copy-to-register
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-02-05 10:37 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
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 [this message]
2022-02-07 12:28 ` Eric S Fraga
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).