all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Schierl <schierlm-usenet@gmx.de>
To: bug-gnu-emacs@gnu.org
Subject: Re: two different internal representations of the key
Date: Sun, 25 Nov 2007 02:22:30 +0100	[thread overview]
Message-ID: <fiaioo$pdc$1@ger.gmane.org> (raw)
In-Reply-To: 20071121153533.2a45e4d7@gaura-nitai.dyndns.org

Hello,

On Wed, 21 Nov 2007 15:35:33 +0100, in gmane.emacs.bugs you wrote:

> Please, if someone can take a look on this issue, it's one of big
> advantages of emacs over vim for non-US users!

unfortunately this is an old and known issue (since Emacs 20 at least), and
I for myself have several "hacks" in my .emacs to work around it.

First:

(defun mihi-insert-keycode () 
  (interactive)
  (insert (format "%S" (read-key-sequence ""))))

This enables me to run M-x mihi-insert-keycode, press a key and have the
keycode in the current buffer. Then I have a cond block that defines keys
depending on system-configuration and/or window-system, like this:

(cond
 ((eq system-configuration 'windows-nt)
  (global-set-key [342387] "»")  ; C-ö
  (global-set-key [342398] "«")) ; C-ä
 ;; other configurations I use are here
)

Most likely this issue will vanish with Emacs 23, because that one will use
Unicode internally, so there won't be more than one codepoint for the same
character any longer.

Michael

-- 
#!/usr/bin/perl -I' # tekscribble.pl - start in an xterm and scribble with mouse
$|=1;$g="\35";sub g{getc}sub p{print@_}system"stty -icanon";p"\233?38h";for(;;){
p"$g\33\32";$_=g;$x=g;$X=g;$y=g;$Y=g;last if/q/;$k=$y.chr((ord$Y)+64).$x.chr((
ord$X)+32);p"\33\14"if/c/;p$g.(/ì/?$l:$k).$k;$l=$k;}p"\33\3";system"stty icanon"





  reply	other threads:[~2007-11-25  1:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 14:35 two different internal representations of the key Gour
2007-11-25  1:22 ` Michael Schierl [this message]
2007-11-29 10:14   ` Gour

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='fiaioo$pdc$1@ger.gmane.org' \
    --to=schierlm-usenet@gmx.de \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=schierlm@gmx.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 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.