From: Aaron Meurer <asmeurer@gmail.com>
To: 郭晓峰 <lamuguo@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: I can't use Alt+Shift
Date: Wed, 18 Jan 2012 17:34:19 -0700 [thread overview]
Message-ID: <CAKgW=6KR2pWVHtC57RxSEYfq-WX_HSeb3MOYLnp2EfnyCd696w@mail.gmail.com> (raw)
In-Reply-To: <CANupJ5TgxDLTUaRR22uZYrdN-8Qa_eT-yUSNeuyTfyyn33fhAw@mail.gmail.com>
If your terminal program lets you define custom key sequences, you can
work-around this by setting what you want to do as a some other unused
key sequence in your .emacs, and then setting your terminal to convert
the one key sequence to the other.
Aaron Meurer
On Tue, Jan 17, 2012 at 11:00 AM, 郭晓峰 <lamuguo@gmail.com> wrote:
> Maybe something below is useful:
> - Make sure your terminal or GUI transfer the key to the place you run
> emacs. To confirm this, you can use "showkey" in console-tools for
> terminal, or "xev" in X.
> - If it is transferred, make sure you can see the same "scan code" in
> emacs, with "Ctrl-h l", which will show you latest keyboard strokes.
> - If you can see the strokes in emacs, make sure it is combined with
> the emacs keymap. "Ctrl-h b" will show you all the mapping. "M-right"
> or "M->", I am not sure which one you like, should be combined with
> the key.
> - In the end, make sure <M-right> is combined with some emacs
> interactive function.
>
> Hope I didn't miss anything here, and hope the hints are helpful to you.
>
> Best Regards,
> Xiaofeng
>
> On Tue, Jan 17, 2012 at 6:43 AM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
>>
>> Am 17.1.2012 um 13:36 schrieb Daniel Sousa:
>>
>>> When I run C-h k and press that key combination, emacs simply ignores it
>>> and doesn't even say that it is undefined.
>>
>> Correct! In every software terminal emulation GNU Emacs is the guest of this software product. When its host is not able to receive or distinguish the signals about the keys being pressed (or released), then the host cannot send anything to its guest. (You might try to teach your terminal emulation a bit more key events.) So GNU Emacs does not receive anything. To check what it might receive you can press, for example in *scratch* buffer, C-q and then some desired key combination. By this means you record anything the host programme sends to its guest GNU Emacs. You can also type C-h l, which shows a recording of what you typed. Or actually of what GNU Emacs received from your keyboard work...
>>
>> --
>> Greetings
>>
>> Pete
>>
>> Without vi there is only GNU Emacs
>>
>>
>
next prev parent reply other threads:[~2012-01-19 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 22:29 I can't use Alt+Shift Daniel Sousa
2012-01-08 0:31 ` Peter Dyballa
[not found] ` <CAKhc=u53yZQQJWc4zLVpxOZv-UC2ZaSx_-0SM-sRgm_ExSazCg@mail.gmail.com>
2012-01-17 14:43 ` Peter Dyballa
2012-01-17 18:00 ` 郭晓峰
2012-01-19 0:34 ` Aaron Meurer [this message]
[not found] <mailman.1433.1325975890.15002.help-gnu-emacs@gnu.org>
2012-01-08 21:33 ` unfrostedpoptart
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='CAKgW=6KR2pWVHtC57RxSEYfq-WX_HSeb3MOYLnp2EfnyCd696w@mail.gmail.com' \
--to=asmeurer@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lamuguo@gmail.com \
/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).