From: Valentin Plechinger <v.plechinger@gmail.com>
To: Help-gnu-emacs <Help-gnu-emacs@gnu.org>
Subject: Keyboard Translate
Date: Tue, 21 Jun 2011 19:07:19 +0200 [thread overview]
Message-ID: <87r56nkta0.wl%v.plechinger@gmail.com> (raw)
Hello,
I have some trouble with keyboard-translate
This is in my .emacs
...
(keyboard-translate ?\C-p ?\C-t) ; translate
(keyboard-translate ?\C-e ?\C-p) ; translate
(keyboard-translate ?\C-f ?\C-e) ; translate
...
The Problem is that this doesn't get evaluated when the emacs daemon starts, so I have to eval it by hand.
Also if I close the frame where my .emacs is opened after evaluating, it stops working and I have to evaluate my .emacs again.
Which sucks... a lot...
Any clues how to solve this?
Cheers,
Valentin
next reply other threads:[~2011-06-21 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 17:07 Valentin Plechinger [this message]
[not found] <mailman.261.1136647273.26925.help-gnu-emacs@gnu.org>
2006-01-09 4:04 ` keyboard translate Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 15:17 Emabela
2006-01-07 15:44 ` thomas
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=87r56nkta0.wl%v.plechinger@gmail.com \
--to=v.plechinger@gmail.com \
--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).