Gnus development mailing list
 help / color / mirror / Atom feed
From: Sudish Joseph <sudish@mindspring.com>
Subject: Re: Danger!  Danger!
Date: 26 Nov 1996 15:02:59 -0500	[thread overview]
Message-ID: <yvia4ticbp58.fsf@atreides.mindspring.com> (raw)
In-Reply-To: David Moore's message of 26 Nov 1996 11:18:43 -0800

In article <rvpw108y24.fsf@sdnp5.ucsd.edu>,
David Moore <dmoore@UCSD.EDU> writes:
> Steven L Baur <steve@miranova.com> writes:
>> Ouch.  I'm noticing a different effect.  I'm having some messages that
>> are counted as unread in the *Group* buffer disappear into the ether.

> 	I used to notice this occasionally, and thought it was related
> to crossposts or duplication or NoCeM.  But in 0.70 it's happening _a
> lot_.  Also now sometimes when I enter a group, read all of the articles
> and exit, the group buffer will say '1' instead of '0', but when I go
> into it, nothing's there of course.

I've been seeing this since 0.60.  It didn't happen prior to 0.56.  In
private mail with Lars, I convinced myself that Gnus was getting
confused when the head article was cancelled.  I'm no longer sure of
this.  I just had a 7 article group present 5 articles on entering.

Also, it'd be real neat if M-RET behaved like C-u SPC.  I.e., it
should not look at ticked/dormant article numbers.  Just fetching the
last n articles and presenting them w/o *any* further processing would
be _extremely_ useful.  As things stand, port 119 is the only way we
have of checking stuff; too time-consuming to be a real option for me.


BTW, the gnus-emphasise stuff simply rewlz.  Makes a huge difference
when reading and is easy to create when writing.  No hope of ever
making this standard, but it'd have been a really nifty, lightweight
mechanism that works on all UA's.

-Sudish


  reply	other threads:[~1996-11-26 20:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-26 17:12 Lars Magne Ingebrigtsen
1996-11-26 17:23 ` Samuel Tardieu
1996-11-26 18:07   ` Steven L Baur
1996-11-26 19:18     ` David Moore
1996-11-26 20:02       ` Sudish Joseph [this message]
1996-11-26 21:18         ` Per Abrahamsen
1996-11-26 22:42           ` Steven L Baur
1996-11-26 22:52           ` Sudish Joseph
1996-11-26 22:48         ` Steven L Baur
1996-11-26 23:18           ` Sudish Joseph
1996-11-26 23:57             ` Steven L Baur
1996-11-27  2:15               ` Lars Magne Ingebrigtsen
1996-11-27 16:36                 ` Steven L Baur
1996-11-27  1:54         ` Lars Magne Ingebrigtsen
1996-11-27 10:31           ` Hrvoje Niksic
1996-11-27 11:47             ` Lars Magne Ingebrigtsen
1996-11-27 14:26               ` Karl Kleinpaste
1996-11-27 12:22           ` Karl Kleinpaste
1996-11-27  1:49       ` Lars Magne Ingebrigtsen
1996-11-27  3:07         ` David Moore
1996-11-27  5:54           ` Mark Boyns
1996-11-29  8:26           ` Lars Magne Ingebrigtsen
1996-11-27 10:12       ` Steinar Bang
1996-11-26 19:39     ` Samuel Tardieu
1996-11-26 19:53       ` Per Abrahamsen
1996-11-26 20:20       ` David Moore
1996-11-27  2:18         ` Lars Magne Ingebrigtsen
1996-11-27 10:11     ` Steinar Bang
1996-11-27 10:23       ` Lars Magne Ingebrigtsen

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=yvia4ticbp58.fsf@atreides.mindspring.com \
    --to=sudish@mindspring.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).