From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Threading wrong if showing undownloaded articles
Date: Thu, 27 Feb 2003 15:51:07 +0100 [thread overview]
Message-ID: <84d6ldkc9w.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 26 bytes --]
See this summary buffer:
[-- Attachment #2: x.png --]
[-- Type: image/png, Size: 8706 bytes --]
[-- Attachment #3: Type: text/plain, Size: 345 bytes --]
As you can see, the \--\ markers have moved right for the messages
that were selected for display. Also, the threads aren't shown
correctly -- after doing J u on that group and reentering I see
proper thread trees.
(The \--\ characters come from %B in gnus-summary-line-format.)
--
A preposition is not a good thing to end a sentence with.
next reply other threads:[~2003-02-27 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 14:51 Kai Großjohann [this message]
2003-02-28 5:46 ` Kevin Greiner
2003-02-28 13:07 ` Kai Großjohann
2003-02-28 13:52 ` Kevin Greiner
2003-03-08 17:12 ` Kai Großjohann
2003-03-08 17:31 ` Kai Großjohann
2003-03-09 6:20 ` Kevin Greiner
2003-03-09 11:19 ` Kai Großjohann
2003-03-09 14:33 ` Kevin Greiner
2003-03-09 16:39 ` Kai Großjohann
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=84d6ldkc9w.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.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).