From: Max Mikhanosha <max.mikhanosha@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t)
Date: Tue, 01 Jun 2021 17:45:22 +0000 [thread overview]
Message-ID: <pn0jIScs8eOdPcKvtZ1NznYW5zCxx1RbcPRIeKTlVK7PD1TZsLrBJXb2FWqXG-ReOT-4eEy0Y45sZ5EO5DeQlhh5ZEA9VkmbQs5U-0Od43M=@protonmail.com> (raw)
In-Reply-To: <83h7ihze5y.fsf@gnu.org>
On Tuesday, June 1st, 2021 at 1:29 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> And btw, why do you use MetaSendEscape:false with these emulators? It
> sounds like if you set MetaSendEscape:true, your problems will be
> solved, no? FWIW, this is how I use terminal emulators here, for many
> years, including with non-ASCII input (and of course Meta-characters),
> and I have yet to see a single problem.
Its because of vi. Not to start an argument, but evil package for emacs is best of both worlds,
its vim with Elisp scripting, and my brain is already hardwired for vi keys for decades).
When typing fast in vi mode, its really frustrating to be typing, then press Esc o to
exit insert mode and start new line, only for it to be interpreted as M-o. Its even worse
when typing over a slow-laggy ssh connections.
Thus most vi-junkies have their terminals configured with metaSendEscape:false
next prev parent reply other threads:[~2021-06-01 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:19 Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t) Max Mikhanosha
2021-06-01 16:51 ` Eli Zaretskii
2021-06-01 17:28 ` Max Mikhanosha
2021-06-01 17:38 ` Eli Zaretskii
2021-06-01 18:01 ` Max Mikhanosha
2021-06-01 18:18 ` Eli Zaretskii
2021-06-01 18:35 ` Max Mikhanosha
2021-06-01 18:46 ` Eli Zaretskii
2021-06-02 9:22 ` Max Mikhanosha
2021-06-02 12:16 ` Andreas Schwab
2021-06-03 5:42 ` Max Mikhanosha
2021-06-05 14:20 ` Eli Zaretskii
2021-06-01 17:29 ` Eli Zaretskii
2021-06-01 17:45 ` Max Mikhanosha [this message]
2021-06-01 17:52 ` Eli Zaretskii
2021-06-01 18:10 ` Max Mikhanosha
2021-06-01 17:04 ` Andreas Schwab
2021-06-01 17:36 ` Max Mikhanosha
2021-06-01 20:06 ` Stefan Monnier
2021-06-02 10:21 ` Max Mikhanosha
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='pn0jIScs8eOdPcKvtZ1NznYW5zCxx1RbcPRIeKTlVK7PD1TZsLrBJXb2FWqXG-ReOT-4eEy0Y45sZ5EO5DeQlhh5ZEA9VkmbQs5U-0Od43M=@protonmail.com' \
--to=max.mikhanosha@protonmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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).