From: Manuel Carro <mcarro@fi.upm.es>
To: Philipp Haselwarter <philipp.haselwarter@gmx.de>
Cc: asjo@koldfront.dk (Adam Sjøgren), ding@gnus.org
Subject: Re: Show mark in unread emails
Date: Tue, 20 Dec 2011 19:33:23 +0100 [thread overview]
Message-ID: <7s4nwvm6to.fsf@fi.upm.es> (raw)
In-Reply-To: <87wr9rzduj.fsf@nzebook.haselwarter.org> (Philipp Haselwarter's message of "Tue, 20 Dec 2011 12:23:16 +0100")
> Then `tick' the articles, as Steinar suggested in his first mail:
> `gnus-summary-tick-article-forward' is bound to `u' in summary and
> article buffer. That'll mark the article with a `!' and it'll show up when
> you enter the group. It's useful to "bookmark" read articles that still
> require some action on your part.
This I do (manually) for messages that I have read and I know I will
have to work on or refer to later on before sending them to their final
group. Sorry I did not mention this before. In short, I'd be glad if I
could distinguish between the following three categories:
- Not-yet-read messages.
- Read messages.
- Read messages which I manually tick as a reminder that they are special.
Cheers,
next prev parent reply other threads:[~2011-12-20 18:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 12:44 Show read emails? Petro
2011-12-16 16:59 ` Steinar Bang
2011-12-16 19:58 ` Wes Hardaker
2011-12-17 10:46 ` Vitalie Spinu
2011-12-17 11:03 ` Adam Sjøgren
2011-12-17 21:25 ` Steinar Bang
2011-12-18 23:08 ` Show mark in unread emails Manuel Carro
2011-12-19 0:15 ` Russ Allbery
2011-12-19 1:25 ` Manuel Carro
2011-12-19 14:20 ` Adam Sjøgren
2011-12-20 8:09 ` Manuel Carro
2011-12-20 11:23 ` Philipp Haselwarter
2011-12-20 18:33 ` Manuel Carro [this message]
2011-12-20 18:56 ` Adam Sjøgren
2011-12-20 19:16 ` Manuel Carro
2011-12-20 20:14 ` Adam Sjøgren
2011-12-20 20:24 ` Manuel Carro
2011-12-20 20:33 ` Adam Sjøgren
2011-12-21 15:35 ` Manuel Carro
2011-12-20 20:18 ` Philipp Haselwarter
2011-12-20 20:31 ` Philipp Haselwarter
2011-12-19 1:57 ` XeCycle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7s4nwvm6to.fsf@fi.upm.es \
--to=mcarro@fi.upm.es \
--cc=asjo@koldfront.dk \
--cc=ding@gnus.org \
--cc=philipp.haselwarter@gmx.de \
/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.
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).