unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: 50983@debbugs.gnu.org
Subject: bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters
Date: Sun, 03 Oct 2021 12:01:36 +0300	[thread overview]
Message-ID: <83ee92a3db.fsf@gnu.org> (raw)
In-Reply-To: <CAE9z9A3iOEzXXBsCQWu0-fRV9DRCYXFTgXcgqpyfZqEYACrh-Q@mail.gmail.com> (message from Rudi C on Sun, 3 Oct 2021 10:17:21 +0330)

> From: Rudi C <rudiwillalwaysloveyou@gmail.com>
> Date: Sun, 3 Oct 2021 10:17:21 +0330
> Cc: 50983@debbugs.gnu.org
> 
> > The site which you use to post the files is problematic: its
> certificate is expired or invalid.
> 
> I use caddy to automatically manage its certificates, and I don't get any cert errors myself. Can you be more
> specific? Perhaps you need newer versions of wget? 

No, I don't think so.  Anyway, this is a tangent; if you think
everything is okay with the site, I can fetch files regardless.

> https://www.ssllabs.com/ssltest/analyze.html?d=files.lilf.ir also says everything is okay.
> 
> > This could be specific to macOS
> 
> I tested `bug.txt` via SSH on an Ubuntu server with emacs 27.2, and it was no different:
> https://files.lilf.ir/tmp/tmp.mZxt5Pilap.png

How exactly did you do that? where was Emacs running and where was the
display running?  Was that with or without X forwarding?

Also, this is the second file; what about the first one?  Do you see
on Ubuntu problems with deleting characters in it, and if so, which
characters and what problems this causes?

> Testing it with other terminal apps, none of the bugs occur with `terminal.app`. 
> 
> The RTL is all wrong on `terminal.app` though (https://files.lilf.ir/tmp/tmp.1UjK8TYGoG.png)
> , but I guess it's unrelated. Alacritty doesn't show the bug, and it also doesn't mess up the RTL shaping.
> 

To display RTL text on a terminal, you need to turn off bidirectional
features of the terminal, if it has them, because Emacs performs the
bidirectional processing by itself.

> If you think the issue is to be upstreamed to Kitty, can you open an issue on their Github?
> (https://github.com/kovidgoyal/kitty/issues) 

Sorry, I wouldn't know what to write there, and cannot present any
data as I don't have Kitty installed.  I think it's better that you do
it.





  reply	other threads:[~2021-10-03  9:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 22:50 bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters Rudi C
2021-10-03  5:51 ` Eli Zaretskii
2021-10-03  6:47   ` Rudi C
2021-10-03  9:01     ` Eli Zaretskii [this message]
2021-10-03  9:11   ` Lars Ingebrigtsen
2021-10-03  9:54   ` Alan Third
2021-10-03 10:04     ` Eli Zaretskii
2021-10-03 10:24       ` Alan Third
2021-10-03 10:49         ` Eli Zaretskii
2021-10-03 11:26           ` Alan Third
2021-10-03 12:02             ` Eli Zaretskii
2021-10-03 12:54               ` Alan Third
2021-10-03 14:48                 ` Eli Zaretskii
2021-10-03 11:00         ` Rudi C
2021-10-03 11:11           ` Eli Zaretskii
2021-10-04  8:05             ` Rudi C
2021-10-04 12:40               ` Eli Zaretskii
2021-10-04 13:50                 ` Eli Zaretskii
2022-09-04 21:37                   ` Lars Ingebrigtsen
2021-10-03  9:08 ` Lars Ingebrigtsen
2021-10-03 10:48   ` Rudi C

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=83ee92a3db.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50983@debbugs.gnu.org \
    --cc=rudiwillalwaysloveyou@gmail.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).