unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thibaut Verron <thibaut.verron@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>, hw <hw@adminart.net>
Subject: Re: vterm and Meta?
Date: Wed, 2 Aug 2023 07:54:08 +0000	[thread overview]
Message-ID: <c5b60f41-317b-448f-b1e1-a177d9620652@mail.shortwave.com> (raw)
In-Reply-To: <b9d357c1e8350311e747f671d759222167a960ce.camel@adminart.net>

> With -Q ... with -q, it says "x is undefined" in the message buffer.
That is... extremely strange.

What about C-h k x ?

What is your operating system, emacs version, etc?

Does the alt key on your keyboard work in other programs?
If you are on X, can you use xev to confirm that it sends the correct keycode?

On Wed Aug 2, 2023, 12:39 AM GMT, hw <mailto:hw@adminart.net> wrote:
> On Tue, 2023-08-01 at 19:54 +0000, Thibaut Verron wrote:
>> > It looks up x: "runs the command self-insert-command (found in
>> > global-map), which is an interactive built-in function in ‘C source
>> > code’ ..."
>>
>> Even with emacs -q?
>
> With -Q ... with -q, it says "x is undefined" in the message buffer.
>> Are you perhaps trying to use Meta like you use Esc, releasing Alt before you press x ?
>
> No, I'm pressing Alt-x without letting off of Alt. Not having to let
> off like with ESC makes it seem so interesting to be able to use Alt
> instead of ESC for Meta.
>> > Alt or ESC, or both?
>>
>> Both, but I'm only surprised about Alt, Esc should always work.
>
> emacs -q -nw in gnome terminal also says "x is undefined".
>
>


  reply	other threads:[~2023-08-02  7:54 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     ` vterm and Meta? Spencer Baugh
2023-08-01 16:36       ` 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 [this message]
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=c5b60f41-317b-448f-b1e1-a177d9620652@mail.shortwave.com \
    --to=thibaut.verron@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hw@adminart.net \
    /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).