From: Spencer Baugh <sbaugh@janestreet.com>
To: help-gnu-emacs@gnu.org
Subject: Re: vterm and Meta?
Date: Tue, 01 Aug 2023 11:05:14 -0400 [thread overview]
Message-ID: <iersf92ajmd.fsf@janestreet.com> (raw)
In-Reply-To: c9db2daa19dfd8a6b4be84bf7bd1a30325e1754b.camel@adminart.net
hw <hw@adminart.net> writes:
> On Tue, 2023-08-01 at 14:12 +0200, Thibaut Verron wrote:
>> Hi,
>>
>> Are you using emacs in a terminal?
>
> sometimes
>
>> If not, Meta is usually bound to a modifier key (afaik by default the
>> one immediately left of the space bar, e.g. alt on PC keyboards), and
>> that works in vterm.
>
> Uhm, I've been using emacs for over 30 years and in all these years,
> the ESC key was always used for a meta key across all instances by
> default. It's the same when running emacs in a terminal, as an X11
> client or with wayland.
>
> The key left of the space bar has always been the Alt key on all PC
> keyboards I've used so far. Pressing, for example, Alt-x, inserts x
> into the buffer (like into this buffer I'm writing this reply in, and
> into the vterm buffer).
>
> How is it that it's different for you?
>
>> If you don't usually run programs using the Esc key in vterm, you can
>> unbind it and send it with vterm-send-next-key when necessary.
>
> Hm, true, I can try that. It's not like I need the ESC key too often
> in a terminal. Somehow I didn't think of that, thank you :)
>
> But then, maybe it makes sense to reconfigure things to use the Alt
> key instead of ESC? Apparently Alt doesn't do anything now and may be
> less awkward to type. Hmm ...
It's possible to separate these in graphical frames. I think you could
(define-key local-function-key-map (kbd "<escape>") nil)
to make <escape> no longer map to ESC. Then you can remove the ESC
binding in vterm and add an <escape> binding. Then Meta bindings and
<escape> will be separate.
(I know this because I figured it out for some evil-mode users and wrote
it up here: https://github.com/emacs-evil/evil/issues/1780 )
next prev parent reply other threads:[~2023-08-01 15:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 11:55 vterm and Meta? hw
2023-08-01 12:12 ` Thibaut Verron
2023-08-01 14:21 ` hw
2023-08-01 14:40 ` how to configure Meta key with wayland (was: vterm and Meta?) hw
2023-08-01 15:05 ` Spencer Baugh [this message]
2023-08-01 16:36 ` vterm and Meta? hw
2023-08-03 19:56 ` Spencer Baugh
2023-08-01 15:09 ` Thibaut Verron
2023-08-01 16:25 ` hw
2023-08-01 19:54 ` Thibaut Verron
2023-08-02 0:39 ` hw
2023-08-02 7:54 ` Thibaut Verron
2023-08-02 14:21 ` hw
2023-08-02 14:29 ` hw
2023-08-02 15:10 ` Yuri Khan
2023-08-03 14:02 ` hw
2023-08-03 19:46 ` tpeplt
2023-08-03 21:32 ` hw
2023-08-03 22:29 ` tpeplt
2023-08-04 20:08 ` hw
2023-08-04 21:20 ` PierGianLuca
2023-08-06 16:32 ` hw
2023-08-06 17:09 ` PierGianLuca
2023-08-06 17:39 ` Yuri Khan
2023-08-04 21:42 ` tpeplt
2023-08-06 19:41 ` hw
2023-08-06 19:54 ` Emanuel Berg
2023-08-02 15:05 ` Thibaut Verron
2023-08-03 13:50 ` hw
2023-08-01 19:01 ` Akib Azmain Turja
2023-08-02 0:45 ` hw
2023-08-02 9:02 ` Akib Azmain Turja
2023-08-02 18:01 ` Emanuel Berg
2023-08-03 14:15 ` hw
2023-08-03 18:49 ` Akib Azmain Turja
2023-08-04 20:30 ` hw
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=iersf92ajmd.fsf@janestreet.com \
--to=sbaugh@janestreet.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).