From: Nevin Kapur <kapur@brutus.mts.jhu.edu>
Subject: SPC doesn't work in tty gnus on XEmacs 21.2.42
Date: 31 Jan 2001 21:10:03 -0500 [thread overview]
Message-ID: <m3g0hzrw5g.fsf@fermat.mts.jhu.edu> (raw)
I just started playing with XEmacs 21.2.42. I usually run gnuserv on a
my machine in school and then read gnus with gnuclient -nw. This
problem only occurs when I use gnus on a tty. The SPC key in the
*Summary* buffer does not work, i.e., if there is more than a
screenful of *Article*, SPC does not move page down. Neither does it
to the next article when one goes past the end of an *Article*. I've
been using 'C-M-v' and 'n' to navigate. Has anyone else seen this?
--
Nevin
next reply other threads:[~2001-02-01 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 2:10 Nevin Kapur [this message]
2001-02-08 14:13 ` Kai Großjohann
2001-02-08 14:33 ` Nevin Kapur
2001-02-08 15:03 ` Kai Großjohann
2001-02-08 15:17 ` ShengHuo ZHU
2001-02-08 15:36 ` Nevin Kapur
2001-02-09 3:55 ` Nevin Kapur
2001-02-11 3:08 ` Nevin Kapur
2001-02-13 4:37 ` ShengHuo ZHU
2001-02-13 15:57 ` Chris Green
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=m3g0hzrw5g.fsf@fermat.mts.jhu.edu \
--to=kapur@brutus.mts.jhu.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).