From: serg.partizan@gmail.com
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix default font scaling
Date: Sun, 23 Jun 2024 17:00:39 +0300 [thread overview]
Message-ID: <3LDJFS.N7X2NCO8QRE9@gmail.com> (raw)
In-Reply-To: <YY2JFS.UYR26AJBROJJ3@gmail.com>
On нд, чер 23 2024 at 13:11:22 +03:00:00, serg.partizan@gmail.com
wrote:
>
>
> On нд, чер 23 2024 at 11:13:53 +02:00:00, Johannes Sixt
> <j6t@kdbg.org> wrote:
>> Am 21.06.24 um 09:18 schrieb Serhii Tereshchenko:
>>> Thanks! I tried booting into Fedora/37 with the same Tk version,
>>> \x7f\x7fand it
>>> indeed does not have this scaling problem.
>>>
>>> Then, I downgraded packages on Arch to 8.6.12 and 8.6.13 - also no
>>> \x7f\x7fproblem.
>>>
>>> The only version affected is 8.6.14.
>>>
>>> That's probably a bug in Tk (and there's quite a few reported,
>>> \x7f\x7fmostly
>>> about "tk scaling" https://core.tcl-lang.org/tk/info/1de3a48312, we
>>> don't use it explicitly in git-gui but on my system it is set to
>>> \x7f\x7f1.3)
>>
>> What is the best course of action now? Since this change does not
>> make
>> things any different for me on Linux+KDE, I am inclined to pick up
>> \x7fthis
>> patch with a modified commit message and code comment that clearly
>> \x7fstate
>> that this is a work-around for a bug in Tk introduced in 8.6.14. This
>> would help users who upgrade from an earlier version of Tk, because
>> it
>> does not look like a fix of Tk is in the works (or that the issue is
>> regarded as a regression by Tk people at all).
>>
>> Suggestions?
>>
>> -- Hannes
>
> I tried running default git-gui and this patch on macOS 12 Monterey,
> and that version does not have font scaling, so there's no problem. I
> will ask around and maybe find someone with latest macOS, which has
> font scaling, and see if there's a problem.
>
> Patch does not breaks anything, but produces a warning due to system
> fonts being present in 'font names'.
>
> Then, if turns out this linux-specific problem - i'd limit this fix
> only to linux. If this affects other platforms - i'd filter fonts to
> only include those starting with 'Tk' prefix.
After more reasearch, I found this:
https://core.tcl-lang.org/tk/info/dccd82bdc7
This is x11-only bug, which existed for a long time and i'm suprized
we're seeing it only in 8.6.14, because .13 and .12 are using the same
negative sizes.
It is also fixed for a long time in the 8.7 branch and not backported
into 8.6.
https://github.com/tcltk/tk/blob/7c3e2ff815e23cc6ac1ce9891ca659e709776ea4/library/ttk/fonts.tcl
Also, you may be not seeing this, because your distro may have applied
this patch:
https://sources.debian.org/patches/tk8.6/8.6.9-2/font-sizes.diff/
With this information, i'm more inclined to making a patch for
ArchLinux package. So, it will fix every tk app, and not only git-gui.
What do you think?
next prev parent reply other threads:[~2024-06-23 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 8:53 [PATCH] Fix default font scaling Serhii Tereshchenko
2024-06-15 16:32 ` Eric Sunshine
2024-06-16 10:30 ` Johannes Sixt
2024-06-16 12:37 ` Serhii Tereshchenko
2024-06-20 17:24 ` Johannes Sixt
2024-06-20 18:11 ` Serhii Tereshchenko
2024-06-20 22:04 ` Johannes Sixt
2024-06-21 7:18 ` Serhii Tereshchenko
2024-06-23 9:13 ` Johannes Sixt
2024-06-23 10:11 ` serg.partizan
2024-06-23 14:00 ` serg.partizan [this message]
2024-06-23 15:50 ` Johannes Sixt
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=3LDJFS.N7X2NCO8QRE9@gmail.com \
--to=serg.partizan@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
/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