From: Noam Postavsky <npostavs@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: 36983@debbugs.gnu.org
Subject: bug#36983: 27.0.50; ansi-term gets disturbed with unicode characters
Date: Fri, 09 Aug 2019 09:10:00 -0400 [thread overview]
Message-ID: <87blwyqyc7.fsf@gmail.com> (raw)
In-Reply-To: <20190809125421.GA19074@protected.rcdrun.com> (Jean Louis's message of "Fri, 9 Aug 2019 14:54:21 +0200")
Jean Louis <bugs@gnu.support> writes:
> * Noam Postavsky <npostavs@gmail.com> [2019-08-09 14:09]:
>> Jean Louis <bugs@gnu.support> writes:
>>
>> > This screen recording may show what is happening:
>> > https://gnu.support/files/tmp/2019-08-09-11:23:11.ogv
>> >
>> > When there is unicode character, there can be error, it seems as it
>> > will not refresh nicely.
>>
>> Do you get the same problem if you call 'cat file' in ansi-term, where
>> 'file' contains those characters?
>
> If I use elinks, lynx, mutt, and view any page with Unicode characters
> I get the problem
Since you mentioned Turkish, I looked at
https://tr.wikipedia.org/wiki/Anasayfa in lynx under ansi-term; it seems
okay. Could you please provide a specific example that doesn't require
access to your email account?
next prev parent reply other threads:[~2019-08-09 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 11:48 bug#36983: 27.0.50; ansi-term gets disturbed with unicode characters Jean Louis
2019-08-09 12:08 ` Noam Postavsky
2019-08-09 12:54 ` Jean Louis
2019-08-09 13:10 ` Noam Postavsky [this message]
2019-08-09 13:41 ` bug#36983: 27.0.50; ansi-term gets disturbed with unicode characters 🐑 Jean Louis
2019-08-09 13:45 ` Jean Louis
2019-08-19 2:19 ` Noam Postavsky
2019-08-19 6:05 ` Jean Louis
[not found] ` <handler.36983.B.156535133416470.ack@debbugs.gnu.org>
2019-08-13 18:46 ` bug#36983: Acknowledgement (27.0.50; ansi-term gets disturbed with unicode characters) Jean Louis
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=87blwyqyc7.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=36983@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).