From: Nevin Kapur <nevin@jhu.edu>
Cc: ding@gnus.org
Subject: Is xemacs -unmapped broken? (was Re: Problem with Gnus using 21.2.4x)
Date: 26 Feb 2001 21:10:34 -0500 [thread overview]
Message-ID: <m3itlwho4l.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <m3lmquu29n.fsf@fermat.mts.jhu.edu>
I believe I've tracked this down. It seems to be a problem with xemacs
-unmapped. The following behavior is repeatable in 21.2.45 on 2 RedHat
7.0 systems without a .emacs or .gnus:
1. xemacs -unmapped -f gnuserv-start &
2. gnuclient
3. M-x gnus
4. quit gnus
5. gnuclient -nw
6. M-x gnus in the tty gnuclient.
7. Enter any group.
8. SPC in the *Summary* buffer (`gnus-summary-next-page') does not
scroll the *Article* buffer.
If one kills the X gnuclient (delete-frame), SPC starts to work again.
Start another X gnuclient and SPC will stop working.
This problem does not exist in XEmacs 21.1.12. Without the -unmapped
option, again there is no problem.
--
Nevin
prev parent reply other threads:[~2001-02-27 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 16:59 Problem with Gnus using 21.2.4x Nevin Kapur
2001-02-27 2:10 ` Nevin Kapur [this message]
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=m3itlwho4l.fsf@fermat.mts.jhu.edu \
--to=nevin@jhu.edu \
--cc=ding@gnus.org \
/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).