From: comphelp@toddh.net (Todd H.)
Subject: Function keys, keymap issue, over SSH terminal session
Date: 21 Mar 2005 22:45:06 -0600 [thread overview]
Message-ID: <84d5ts2srx.fsf@ripco.com> (raw)
Greetings,
I'm running emacs over an ssh session. No X, just a plain ole text
terminal (so any solutions involving xmodmap aren't applicable, I
don't think?? dunno). I'm connecting to a Debian box using TERM=VT220
and a matching VT220 emulation in SecureCRT (a very very nice windows
SSH client that's typically quite emacs friendly).
The trouble is, The F11 and F12 (and the rest of the F keys actually)
don't appear to be properly mapping, so my .emacs entries such as:
(global-set-key [f11] 'gnus)
(global-set-key [f12] 'vm)
Aren't working.
Now the same .emacs, same SecureCRT profile didn't have this problem
on a RedHat system running Emacs 20.6.1, but this Debian system
running 21.3.1 seems to be quite a bit different in the keymapping
dept.
Any utilities I can run to figure this out, and what if any mapping do
I need to do, and where (in .emacs ?
--
Todd H.
http://www.toddh.net/
next reply other threads:[~2005-03-22 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 4:45 Todd H. [this message]
2005-03-23 17:08 ` Function keys, keymap issue, over SSH terminal session Johan Bockgård
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84d5ts2srx.fsf@ripco.com \
--to=comphelp@toddh.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).