From: Steve Youngs <youngs@xemacs.org>
Subject: Re: [Enter] mapping in a gnuserv text frame for MULE XEmacs 21.5b12
Date: Wed, 07 May 2003 12:26:15 +1000 [thread overview]
Message-ID: <microsoft-free.87issnwkzc.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <m3bryfsuv2.fsf_-nf--_xmat_-m:gnus_---@tuxie.homelinux.net> (Nelson Ferreira's message of "Tue, 06 May 2003 16:06:25 -0400")
|--==> "njsf" == Nelson Ferreira <nelson.ferreira@verizon.net> writes:
njsf> When using Gnus v5.10.2 in a MULE XEmacs 21.5B12 , the Enter
njsf> key is sent as LFD which is not in the Gnus keymap definitions,
njsf> thus causing the Buffer is read-only error.
This isn't a Gnus problem, it is a bug in XEmacs 21.5 [1]. As a work
around, simply eval something in the scratch buffer _before_ you do
anything else. It doesn't matter what you eval, you could even:
() C-j
njsf> Which keymaps should I change ?
None. You can't anyway.
,----[ C-h f define-key RET ]
| `define-key' is a built-in function
| (define-key KEYMAP KEYS DEF)
|
| Documentation:
|
| [...]
|
| Of course, all of this applies only when running under a window system. If
| you're talking to XEmacs through a TTY connection, you don't get any of
| these features.
|
| [...]
|
`----
njsf> Should this be a default for Gnus , i.e. to map LFD to the
njsf> same bindings as RET, or should I as a general rule have some
njsf> XEmacs wide mapping of LFD to RET ?
As it is an XEmacs bug, no.
Footnotes:
[1] We are aware of it and are working towards a fix.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<youngs@xemacs.org>---|
next prev parent reply other threads:[~2003-05-07 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3bryfsuv2.fsf_-nf--_xmat_-m:gnus_---@tuxie.homelinux.net>
2003-05-06 23:35 ` Nelson Ferreira
2003-05-07 2:26 ` Steve Youngs [this message]
[not found] ` <m3r87bfy33.fsf_-nf--_xmat_-m:gnus_---@tuxie.homelinux.net>
2003-05-07 2:27 ` Steve Youngs
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=microsoft-free.87issnwkzc.fsf@eicq.dnsalias.org \
--to=youngs@xemacs.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).