unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Max Mikhanosha <max.mikhanosha@protonmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t)
Date: Tue, 01 Jun 2021 21:18:52 +0300	[thread overview]
Message-ID: <83bl8pzbw3.fsf@gnu.org> (raw)
In-Reply-To: <HRBXJ_TvMkbH_f-xYguQercYQngtf0-jd4BPF6ssrEPKKkWEhhyCEF3TGA5Ygt45Zh4139oWHXjTIAVV7AuLIJgbOvLGPw8yV3i8tJObBGo=@protonmail.com> (message from Max Mikhanosha on Tue, 01 Jun 2021 18:01:27 +0000)

> Date: Tue, 01 Jun 2021 18:01:27 +0000
> From: Max Mikhanosha <max.mikhanosha@protonmail.com>
> Cc: emacs-devel@gnu.org
> 
> My patch functionality is specifically enabled only when someone customizes their Emacs to set META parameter of (set-input-mode) to T or NIL, but its behavior is exactly the same as in non-UTF-8 mode.  Only thing it does, is make UTF-8 terminals work exactly same as non-UTF-8 terminals, instead of beaing broken

But UTF-8 is not the only encoding that uses the 8th bit.  So this
must be a separate setting, unrelated to the encoding being UTF-8 or
not.  What you want is for Emacs to interpret the 8th bit after
decoding characters and not before it as it does now.  So I think a
new non-nil value of input-meta-mode should be introduced to trigger
this behavior, and you should drop the tests of the encoding being
UTF-8, as it's not the only encoding that can be affected.



  reply	other threads:[~2021-06-01 18:18 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 [this message]
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
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=83bl8pzbw3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=max.mikhanosha@protonmail.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. 
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).