From: Harry Putnam <reader@newsguy.com>
Subject: Re: Article read not being marked as such
Date: 31 Jul 1998 11:50:43 -0700 [thread overview]
Message-ID: <m3k94tg8ho.fsf@newsguy.com> (raw)
In-Reply-To: Nelson Jose dos Santos Ferreira's message of "31 Jul 1998 18:21:29 +0100"
Nelson Jose dos Santos Ferreira <Nelson.Ferreira@inesc.pt> writes:
>> [...]
>
> Sure.
>
> When I enter a group with space ou mouse (i.e. gnus-topic-read-group
> or gnus-mouse-pick-topic, because I use topics) and the first article
> to be read is in a thread with a parent article which is ticked, it
> does not get marked as read.
> Moving the cursor up or selecting another article and then selecting
> the first article again makes it being marked as read.
I have noticed a very similar behavior. I have a setting to keep from
going to first unread when entering a group. I like to do it manually
after looking things over. So when I press 'n' the first time, if the
first unread is in a hidden thread it will be displayed in an article
buffer but remains marked unread. Moving on with another 'n' will
leave the first one showing unread, unless I go back to it. Pressing
<RET> after the first 'n' still leaves the article unread.
Only happens when the first unread is in a hidden thread.
Related settings:
(set-variable (quote gnus-group-goto-unread) nil)
(setq gnus-thread-hide-subtree t)
--
Harry Putnam reader@newsguy.com
next prev parent reply other threads:[~1998-07-31 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-01 14:35 Nelson Jose dos Santos Ferreira
1998-07-01 15:34 ` Lars Magne Ingebrigtsen
1998-07-25 14:15 ` Nelson Jose dos Santos Ferreira
1998-07-26 15:39 ` Lars Magne Ingebrigtsen
1998-07-26 17:37 ` Nelson Jose dos Santos Ferreira
1998-07-30 20:41 ` Lars Magne Ingebrigtsen
1998-07-31 17:21 ` Nelson Jose dos Santos Ferreira
1998-07-31 18:50 ` Harry Putnam [this message]
1998-08-01 14:26 ` Lars Magne Ingebrigtsen
1998-08-04 13:12 ` Nelson Jose dos Santos Ferreira
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=m3k94tg8ho.fsf@newsguy.com \
--to=reader@newsguy.com \
/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).