unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Chris Moore" <christopher.ian.moore@gmail.com>
To: "Andreas Schwab" <schwab@suse.de>
Cc: David Reitter <david.reitter@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-pretest-bug@gnu.org
Subject: Re: capslock changes control characters?
Date: Tue, 4 Mar 2008 14:15:05 +0100	[thread overview]
Message-ID: <a9691ee20803040515l31b65e00vd49909e356b808f4@mail.gmail.com> (raw)
In-Reply-To: <jeve43vp5t.fsf@sykes.suse.de>

On Mon, Mar 3, 2008 at 3:49 PM, Andreas Schwab <schwab@suse.de> wrote:

>  Or add ctrl:nocaps to your XKB options.

I don't want to disable the capslock key, I just want it to work properly.

When capslock is on, the letters a-z should become A-Z, but that's
all.  I don't expect 1 to become ! (shifted 1), and I don't expect C-q
to become C-S-q.  Capslock should only act on regular letters, not on
control keys.

Another example:  in a *shell* buffer, I expect M-p to take me to a
previous command in the shell history.  If capslock is on, it just
inserts a p into the buffer.  I don't know why it inserts a lowercase
'p' (capslock is on, after all), but this is what C-h k tells me:

  p (translated from M-P) runs the command self-insert-command, which is
  an interactive built-in function in `C source code'.

Chris.




  reply	other threads:[~2008-03-04 13:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 18:45 capslock changes control characters? Chris Moore
2008-02-24 22:30 ` Richard Stallman
2008-03-03 10:38   ` David Reitter
2008-03-03 14:02     ` Stefan Monnier
2008-03-03 14:49       ` Andreas Schwab
2008-03-04 13:15         ` Chris Moore [this message]
2008-03-05  5:13   ` Kenichi Handa
2008-03-05 16:18     ` Stefan Monnier
2008-03-05 16:50       ` Andreas Schwab
2008-03-06 11:20         ` Kenichi Handa
2008-03-07 23:04           ` Stefan Monnier
2008-03-10  0:54             ` Kenichi Handa
2008-03-10  3:26               ` Stefan Monnier
2008-03-16  9:15     ` Andreas Schwab
2008-03-17  0:48       ` Kenichi Handa

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=a9691ee20803040515l31b65e00vd49909e356b808f4@mail.gmail.com \
    --to=christopher.ian.moore@gmail.com \
    --cc=david.reitter@gmail.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@suse.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).