Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: gnus-summary-refer-parent-article weirdness
Date: 20 Feb 2001 15:28:48 -0500	[thread overview]
Message-ID: <m3zofhp089.fsf@multivac.student.cwru.edu> (raw)

I'm running current CVS oGnus, and getting some hard-to-pin-down
errors with gnus-summary-refer-parent-article.  When I try to get the
parent of an article, I sometimes get one of a variety of errors if
the parent is not already visible in the Summary buffer, but the
parent's parent is.  Sometimes the grandparent's Summary line gets
duplicated; sometimes the parent is inaccessible.  I can reproduce the
same error consistently in any case where it happens, but I can't
figure out what makes those cases different from cases where no error
occurs.

Example: <URL:http://multivac.cwru.edu/prj/log.tar.gz> is a maildir
with 3 messages, each a reply to the last.  If the first and third are
'ticked (thus visible) and the second is 'read (thus not initially
visible), I get an error if I '^' on the third article.  'C-u RET' to
enter the group shows the correct thread structure.

Some of my Gnus-related configuration stuff can be found at
<URL:http://multivac.cwru.edu/prj/gnus>.  This is all from my .emacs;
I have no .gnus.

" *nntpd*" seems to contain correct data the whole time, so I don't
think this is a backend problem, but in case it is, you can get
nnmaildir from <URL:http://multivac.cwru.edu/nnmaildir/>.

This problem, or one like it, existed at least as far back as 5.8.7,
although for the particular instance where I found and could reproduce
the error in 5.8.7, oGnus did not exhibit the error.  I think 5.8.8
also fixed that particular case.


paul



             reply	other threads:[~2001-02-20 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 20:28 Paul Jarc [this message]
2002-03-25 19:17 ` Paul Jarc

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=m3zofhp089.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).