From: Burkhard Knopf <burkhard.knopf@informatik.tu-clausthal.de>
Subject: bug (or feature?) in gnus-summary-next-page
Date: 09 Dec 1996 21:34:20 +0100 [thread overview]
Message-ID: <gfu3pvfodv.fsf@mixcoatl.in.tu-clausthal.de> (raw)
Hi!
Is it just me or did anyone else run into this:
Let's say you got a posting that fits in the *Article* window with
some hidden header lines. Then you show those (typing "t") which makes
the article longer that what you see now in the window. Trying to see
the rest of the posting by typing " " (gnus-summary-next-page) won't
show that but rather get the next unread article.
I can't remember having seen that in September Gnus, and I don't like
it either. But who am I to criticize such a nice package ...
--
burkhard.knopf@informatik.tu-clausthal.de
next reply other threads:[~1996-12-09 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-09 20:34 Burkhard Knopf [this message]
1996-12-09 20:59 ` David Moore
1996-12-09 21:33 ` Steven L Baur
1996-12-09 21:37 ` Steven L Baur
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=gfu3pvfodv.fsf@mixcoatl.in.tu-clausthal.de \
--to=burkhard.knopf@informatik.tu-clausthal.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).