From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Caps Lock affects Ctrl+keys
Date: Mon, 20 Jan 2014 19:53:48 +0100 [thread overview]
Message-ID: <877g9uwkkq.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.12445.1390242632.10748.help-gnu-emacs@gnu.org
Yuri Khan <yuri.v.khan@gmail.com> writes:
>> Some information on this, see if you can figure it
>> out: In keymaps(5), there is some information what
>> to do with caps:
>
> I'm in X, I thought I was clear enough. Why or how
> are keymaps(5)/showkey(1)/loadkeys(1) relevant?
If you read the keymaps man page, it sure looks like it
is impossible (the "CapsShift") - this of course does
not imply that the kernel cannot do it in principle, it
just doesn't (what I can read) in that case. How X does
its I/O, and how this relates to the kernel, I don't
know.
--
underground experts united:
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2014-01-20 18:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 11:57 Caps Lock affects Ctrl+keys Yuri Khan
2014-01-20 14:47 ` Jude DaShiell
2014-01-20 15:24 ` Yuri Khan
2014-01-20 17:47 ` Jude DaShiell
[not found] ` <mailman.12433.1390240051.10748.help-gnu-emacs@gnu.org>
2014-01-20 18:24 ` Emanuel Berg
[not found] ` <mailman.12400.1390231499.10748.help-gnu-emacs@gnu.org>
2014-01-20 17:23 ` Emanuel Berg
2014-01-20 18:30 ` Yuri Khan
[not found] ` <mailman.12445.1390242632.10748.help-gnu-emacs@gnu.org>
2014-01-20 18:53 ` Emanuel Berg [this message]
2014-01-20 20:38 ` Yuri Khan
[not found] ` <mailman.12458.1390250342.10748.help-gnu-emacs@gnu.org>
2014-01-20 22:55 ` Emanuel Berg
2014-01-21 2:10 ` Emanuel Berg
2014-01-21 5:07 ` Yuri Khan
[not found] ` <mailman.12490.1390280831.10748.help-gnu-emacs@gnu.org>
2014-01-21 17:38 ` Emanuel Berg
2014-01-24 14:38 ` Yuri Khan
2014-01-24 15:56 ` Stefan Monnier
[not found] ` <mailman.12684.1390574300.10748.help-gnu-emacs@gnu.org>
2014-01-24 15:22 ` Dan Espen
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=877g9uwkkq.fsf@nl106-137-194.student.uu.se \
--to=embe8573@student.uu.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.