From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Chris Torek <chris.torek@gmail.com>
Cc: Lars Kiesow <lkiesow@uos.de>, Git List <git@vger.kernel.org>
Subject: Re: Bug report: gitk unable to handle Unicode properly
Date: Sat, 17 Apr 2021 00:35:36 +0000 [thread overview]
Message-ID: <YHotWPe8noZqd9zt@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAPx1GvetNRBovJMF8tkk9obuSHjC=w9JqryrSTeA0rVF35Q5+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On 2021-04-17 at 00:01:45, Chris Torek wrote:
> On Fri, Apr 16, 2021 at 4:21 PM brian m. carlson
> <sandals@crustytoothpaste.net> wrote:
> > On 2021-04-16 at 16:21:21, Lars Kiesow wrote:
> > > - Launch gitk
> > > - Crash (see below)
>
> > I don't see a crash.
>
> I think this is a Tk/X11 interaction bug.
>
> See, e.g., https://bugs.python.org/issue42225 (which has the same symptoms).
>
> I'm no tcl/tk expert, but I vaguely remember other similar bug
> reports. They all turned out to need a tk-side fix.
It seems from the linked bug report that this is fixed in Tk 8.6.11,
which I'm using, but not in Tk 8.6.10, which is available in Fedora 33.
So it sounds like this should probably be filed as a bug with Fedora. I
don't know what their policy on backports is like, but they might be
willing to backport a fix to Fedora 33.
--
brian m. carlson (he/him or they/them)
Houston, Texas, US
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2021-04-17 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 16:21 Bug report: gitk unable to handle Unicode properly Lars Kiesow
2021-04-16 23:20 ` brian m. carlson
2021-04-17 0:01 ` Chris Torek
2021-04-17 0:35 ` brian m. carlson [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YHotWPe8noZqd9zt@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=lkiesow@uos.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox