unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ryo Furue <furue@hawaii.edu>
To: monnier@iro.umontreal.ca
Cc: bug-gnu-emacs@gnu.org, 4709@emacsbugs.donarmstrong.com
Subject: bug#4709: 23.1; keyboard-translate not working with emacs daemon
Date: Wed, 14 Oct 2009 11:07:19 -1000 (HST)	[thread overview]
Message-ID: <20091014.110719.209373463.furue@hawaii.edu> (raw)
In-Reply-To: <jwv1vl6861j.fsf-monnier+emacsbugreports@gnu.org>

Hi Stefan,

Thank you very much for your response.

| AFAIK, you cannot set it globally.
|
Then, could we make it a request for a new feature?
We could even say that the keyboard-translate functionality
is partially broken because it sometimes works and sometimes
doesn't (Please recall my example).

| You can arrange to set it in every
| terminal (by putting (keyboard-translate ?\C-h ?\C-?) on some
| hook whose name escapes me), tho.

That sounds promising.

| Still, I wonder: why would you want to set such a mapping
| everywhere?
| 
I'm not sure if I understand your question. . . .  If you want
a keyboard translation, you'd want it everywhere consistently,
wouldn't you?

In this particular case, I want C-h to delete the character
before the cursor anywhere and everywhere (when deleting
characters makes sense, that is.  You don't want to delete
characters on a webpage displayed by a webbrowser,
for example).  That's natural for a person like me
who instinctively types C-h to delete.

I used to use

 (global-set-key "\C-h" 'delete-backward-char)

instead of keyboard-translate.  But, as of emacs23, C-h invokes
a help-like feature in the incremental search even with the
setting above.

So, I think keyboard-translate is the cleanest,
once-and-for-all solution, if it works globally.

Best regards,
Ryo






  reply	other threads:[~2009-10-14 21:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 20:37 bug#4709: 23.1; keyboard-translate not working with emacs daemon Ryo Furue
2009-10-14 13:25 ` Stefan Monnier
2009-10-14 21:07   ` Ryo Furue [this message]
2009-10-15  3:34     ` Stefan Monnier
2009-10-15  7:34       ` Ryo Furue
2009-10-15 15:22         ` Stefan Monnier
2009-10-15 18:26           ` Ryo Furue
2009-10-15 20:28             ` Stefan Monnier
2009-10-17  0:55               ` Ryo Furue
2009-10-17  2:22                 ` Stefan Monnier
2009-10-17  3:19                   ` Glenn Morris

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=20091014.110719.209373463.furue@hawaii.edu \
    --to=furue@hawaii.edu \
    --cc=4709@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).