From: Dmitry Bogatov <KAction@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Loadkeys trickery
Date: Fri, 28 Nov 2014 00:58:25 +0300 [thread overview]
Message-ID: <20141127215825.GA7558@self> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
Hello!
I work in linux terminal. I use fbterm and tmux.
I use loadkeys to get more keychords. Here is example of my config:
keymaps 0-255
alt keycode 1 = 0xFFFF
control keycode 105 = 0xFFFE
control keycode 106 = 0xFFFD
control keycode 103 = 0xFFFC
control keycode 108 = 0xFFFB
ctrll keycode 103 = 0xFFFA
shift keycode 57 = 0xFFF9
keycode 56 = Alt
keycode 100 = AltGr
keycode 125 = ShiftL
keycode 127 = ShiftR
keycode 29 = CtrlL
keycode 97 = CtrlR
keycode 58 = Control
These 0xFFFF are some tibetian symbols, their exact values does not
matter. Under linux console, I can happily press (Shift + Space(=keycode
57)) and get strange symbol, and bind it to some command in emacs. If I
start tmux, and press (Shift + Space), I get same strange symbol into
bash prompt. It is great. But! If I start emacs under tmux and press
Shift+Space, emacs interprets it as F10 and open text menu. I checked,
Vim works as expected (prints tibetian symbol).
Usually I run fbterm and tmux in it. Fbterm breaks nothing, but adds 256
colors.
Interesting enough, if I set TERM=linux under tmux, things works well.
I could set it for emacs, but I am unwilling to give up 256 colors.
Also I tried screen over tmux. Same result.
Maybe someone have idea or encountered such problem? Thank in advance for your
attention.
--
Best regards, Dmitry Bogatov <KAction@gnu.org>,
Free Software supporter, esperantisto and netiquette guardian.
GPG: 54B7F00D
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-11-27 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 21:58 Dmitry Bogatov [this message]
2014-12-01 9:18 ` Loadkeys trickery Nancy
2014-12-01 12:39 ` Dmitry Bogatov
[not found] ` <mailman.15043.1417425517.1147.help-gnu-emacs@gnu.org>
2014-12-01 9:29 ` Álvar Ibeas
2014-12-01 9:45 ` Nancy
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=20141127215825.GA7558@self \
--to=kaction@gnu.org \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).