From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44664: 28.0.50; troubles with some chars in term Date: Thu, 19 Nov 2020 18:15:51 +0200 Message-ID: <83r1opnwzs.fsf@gnu.org> References: <83blfvr8xs.fsf@gnu.org> <873617zlor.fsf@igel.home> <838sazqr2r.fsf@gnu.org> <877dqjhy0x.fsf@igel.home> <873617m4tv.fsf@gnus.org> <834klmr989.fsf@gnu.org> <83d00apm6q.fsf@gnu.org> <833615pglp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5877"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, schwab@linux-m68k.org, 44664@debbugs.gnu.org To: Jean Louis Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 19 17:17:11 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1kfmcQ-0001OZ-AC for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 Nov 2020 17:17:10 +0100 Original-Received: from localhost ([::1]:41416 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfmcP-0007C3-85 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 19 Nov 2020 11:17:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51680) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfmcI-0007B0-BY for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 11:17:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57434) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kfmcI-0006KJ-0w for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 11:17:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kfmcH-0001St-RM for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 11:17:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 19 Nov 2020 16:17:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44664 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 44664-submit@debbugs.gnu.org id=B44664.16058025775575 (code B ref 44664); Thu, 19 Nov 2020 16:17:01 +0000 Original-Received: (at 44664) by debbugs.gnu.org; 19 Nov 2020 16:16:17 +0000 Original-Received: from localhost ([127.0.0.1]:40747 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfmbZ-0001Rq-5e for submit@debbugs.gnu.org; Thu, 19 Nov 2020 11:16:17 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51458) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfmbX-0001Rb-2r for 44664@debbugs.gnu.org; Thu, 19 Nov 2020 11:16:16 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55508) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kfmbQ-0005zJ-CV; Thu, 19 Nov 2020 11:16:09 -0500 Original-Received: from [176.228.60.248] (port=1174 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kfmbP-0005vu-Jc; Thu, 19 Nov 2020 11:16:08 -0500 In-Reply-To: (message from Jean Louis on Thu, 19 Nov 2020 18:11:19 +0300) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:193729 Archived-At: > Date: Thu, 19 Nov 2020 18:11:19 +0300 > From: Jean Louis > Cc: larsi@gnus.org, schwab@linux-m68k.org, 44664@debbugs.gnu.org > > > M-: (font-at POS) RET > > > > where POS is the buffer position of the offending character. > > Alternatively, go to the character and type "C-u C-x =", it will pop > > up a buffer with a lot of information including the font. > > The default font probably chosen by Emacs at the same point where > there was that one char I think it is making problems is this one: > > # Otherwise you may see 2 attached screenshots. First screenshot will > show condition "before" as that is when I yet did not come to > allegedly offending characters. There is one line for message of > Thien-Thi > > What one DOES NOT SEE is that there is actually another invisible > line, now shown there. I can see it in mutt in xterm, you can find it > under "Web spy" and before "Thien-Thi". That line is not shown in mutt > under M-x term, until I come with the mutt highlighted line to it. > > The line is from 2002-03-09 - as I said it cannot be seen. That mbox file has several email messages where the encoding is either wrongly declared or is not recognized by mutt. That's a different problem, unrelated to term.el and its handling of fonts. > Then that line shows itself and I can see some replaced characters and > I can see this character not replaced with that circled ?. It is just > perception that this character and maybe others are not properly > interpreted by the terminal or fonts. > > position: 2833 of 7081 (40%), column: 52 > character:  (displayed as ) (codepoint 60531, #o166163, #xec73) > charset: unicode (Unicode (ISO10646)) > code point in charset: 0xEC73 > syntax: w which means: word > category: L:Left-to-right (strong) > to input: type "C-x 8 RET ec73" > buffer code: #xEE #xB1 #xB3 > file code: #xEE #xB1 #xB3 (encoded by coding system utf-8-unix) > display: no font available > > Character code properties: customize what to show > general-category: Co (Other, Private Use) > decomposition: (60531) ('') This is a PUA character, another separate issue (Emacs doesn't expect to see such characters in human-readable text, and cannot display them without special tinkering with font setup). Finally, I don't know what byte sequences did mutt send to the terminal, it is possible that some problems you see are because term.el is unable to interpret some sequences that mutt assumes to be supported. (What termcap/terminfo entry did you use in that shell, which tells mutt what commands to send?) Bottom line, I'm no longer sure which problems we are discussing here, since we have several unrelated issues involved. Please consider separating the issues.