From: Ronald Fischer <rovf@feriasonline.pt.invalid>
Subject: Re: Meta-Down doesn't work
Date: 01 Aug 2002 08:43:41 +0200 [thread overview]
Message-ID: <m2znw7gjtu.fsf@karfiol.glp.de> (raw)
In-Reply-To: <87it2vigyc.fsf@io.com>
Adam Fabian <afabian@io.com> writes:
> When I press alt-down, emacs (from what C-h alt-down tells me) reads
> only the down key; no meta.
When you do from the Linux commandline a
xmodmap -pm
what do you get? Maybe "Alt" is not properly defined as a meta key.
> When I use ESC <down>, emacs says ESC ESC
> [ b is undefined. And meta-up seems to get my some message from the
> kernel about inittab.
This is weird. Could you give more information about this kernel
message thing?
Also, when you do a M-x view-lossage, what keys do you find recorded
there after you have used alt-down and alt-up?
Ronald
--
To reduce spam in my inbox, the address given in the Reply-To: header is
not guaranteed to live longer than 1 month after the article was
posted. My permanent address is (after deleting the XXX):
Ronald Otto Valentin Fischer <rovfXXX@operamail.com>
parent reply other threads:[~2002-08-01 6:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87it2vigyc.fsf@io.com>]
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=m2znw7gjtu.fsf@karfiol.glp.de \
--to=rovf@feriasonline.pt.invalid \
--cc=rovf@feriasonline.pt \
/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).