From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Max Mikhanosha Newsgroups: gmane.emacs.devel Subject: Re: Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t) Date: Tue, 01 Jun 2021 18:35:43 +0000 Message-ID: References: <83k0ndzfxr.fsf@gnu.org> <83fsy1zds7.fsf@gnu.org> <83bl8pzbw3.fsf@gnu.org> Reply-To: Max Mikhanosha Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14872"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 01 20:47:07 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lo9Pu-0003d7-Kq for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Jun 2021 20:47:06 +0200 Original-Received: from localhost ([::1]:32804 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lo9Pt-0007bT-I4 for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Jun 2021 14:47:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49436) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lo9F2-0000iQ-SM for emacs-devel@gnu.org; Tue, 01 Jun 2021 14:35:53 -0400 Original-Received: from mail2.protonmail.ch ([185.70.40.22]:16559) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lo9Ex-0005Jp-Uh for emacs-devel@gnu.org; Tue, 01 Jun 2021 14:35:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1622572544; bh=HdVavCaVByuYGsI4kPBYojE39nJoJ618r+405iFfgJs=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=s4+IHQS9JKt/9oUQWvWe956r5nG6qFqh/PbFdqsvNPuu3PfCHoxgNczKn+1EwJGGp YuGhGDKb8DmTkmJ3jWXEBi0tR+/xFf00xvaMTs0wE9XXAuf4O7ChISpw1zK7x9i3px NUoiEpj05Mk4Y0jKBsxHeVupHEZ8f92HcrFVl638= In-Reply-To: <83bl8pzbw3.fsf@gnu.org> Received-SPF: pass client-ip=185.70.40.22; envelope-from=max.mikhanosha@protonmail.com; helo=mail2.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 01 Jun 2021 14:44:18 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:270241 Archived-At: Ok I'll rework the patch along these lines, and submit again later. Do you = have a suggestion or input-meta-mode new enum value? My only idea is 'ENCOD= ED, to mean same as T but that 8th bit will be checked after decoding the i= nput with whatever keyboard coding system is. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Tuesday, June 1st, 2021 at 2:18 PM, Eli Zaretskii wrote: > > 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 custom= izes 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.