From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Small complaint about M-g
Date: 22 Feb 2000 22:54:45 +0100 [thread overview]
Message-ID: <vafsnyklx7e.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Jussi Yli-Urpo's message of "22 Feb 2000 22:54:45 +0200"
Jussi Yli-Urpo <jmy@h32.erkki.ton.tut.fi> writes:
> This was one of the reasons I eventually turned off
> marking selected articles automatically as read. Now in all
> my mail groups I either manually mark them read one by one
> or catchup whole group when I'm sure that I haven't missed
> anything important.
Some of the users at our site use something which ticks a message when
it is read, rather than marking at as read.
(defun kai-gnus-mark-article-hook ()
(if (and (not (or (memq gnus-current-article gnus-newsgroup-marked)
(memq gnus-current-article gnus-newsgroup-dormant)
(memq gnus-current-article gnus-newsgroup-expirable)
(memq gnus-current-article gnus-newsgroup-ancient)
(memq gnus-current-article gnus-newsgroup-reads))))
(gnus-summary-tick-article)))
(setq gnus-mark-article-hook '(kai-gnus-mark-article-hook))
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-02-22 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-22 0:02 Harry Putnam
2000-02-22 20:54 ` Jussi Yli-Urpo
2000-02-22 21:06 ` Chris Richards
2000-02-22 21:38 ` Alan Shutko
2000-02-23 3:56 ` Harry Putnam
2000-02-23 16:53 ` David S. Goldberg
2000-02-23 17:04 ` David S. Goldberg
2000-02-23 17:36 ` Kai Großjohann
2000-02-23 21:18 ` David S. Goldberg
2000-02-23 22:04 ` Kai Großjohann
2000-02-25 0:14 ` Amos Gouaux
2000-02-22 21:54 ` Kai Großjohann [this message]
2000-02-22 23:25 ` Marking read articles (was Small complaint about M-g) Chris Brierley
2000-02-23 19:13 ` Jussi Yli-Urpo
2000-02-23 20:30 ` Kai Großjohann
2000-02-23 21:05 ` Jussi Yli-Urpo
2000-02-25 0:34 ` Amos Gouaux
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=vafsnyklx7e.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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.
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).