From: Ryo <furue@hawaii.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: keyboard-translate not working with emacs daemon
Date: Mon, 19 Oct 2009 03:11:08 -0700 (PDT) [thread overview]
Message-ID: <13d4341d-50d5-4588-ad03-0e42263f9a88@y28g2000prd.googlegroups.com> (raw)
In-Reply-To: 076d001b-160d-48a2-a426-d9f75a3e1ae9@k13g2000prh.googlegroups.com
On Oct 13, 7:33 am, Ryo <ryofu...@gmail.com> wrote:
[. . .]
> Yesterday, I submitted a report to emacsbugs.donarmstrong.com. The
> issue number is "bug#4709".
An emacs developer kindly found a solution for us:
(define-key key-translation-map [?\C-h] [?\C-?])
Unlike keyboard-translate, the key translation map is global: once you
have set it, it sticks.
Regards,
Ryo
next prev parent reply other threads:[~2009-10-19 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 2:18 keyboard-translate not working with emacs daemon Ryo
2009-10-12 6:24 ` Andreas Politz
[not found] ` <mailman.8578.1255328703.2239.help-gnu-emacs@gnu.org>
2009-10-12 19:48 ` Ryo
2009-10-13 2:40 ` Vassil Nikolov
2009-10-13 17:33 ` Ryo
2009-10-19 10:11 ` Ryo [this message]
2009-10-19 16:34 ` Andreas Politz
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=13d4341d-50d5-4588-ad03-0e42263f9a88@y28g2000prd.googlegroups.com \
--to=furue@hawaii.edu \
--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).