From: pinmacs <pinmacs@cas.cat>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG (regression): clocktable with ~:link t~ looks visually inconsistent
Date: Mon, 9 Sep 2024 18:15:45 +0200 [thread overview]
Message-ID: <bdab5b42-a661-463c-b30d-9a6161b5c48e@cas.cat> (raw)
In-Reply-To: <87a5gje5vb.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On 2024-09-07 19:22, Ihor Radchenko wrote:
> pinmacs@cas.cat writes:
>
>> On a clocktable with hierarchy (see attached file
>> clocktable-link-bug.org), when ~:link t~ is used, it does not look
>> visually good; that was not an issue with the previous versions of orgmode
>>
>> Find attached screenshot 2024-09-01_23-05_clocktable-detail.png, that
>> shows the inconsistency in my ~emacs -Q~ with orgmode 9.7.10 and
>> emacs-30 branch with commit 44c2614
> I cannot reproduce.
> See the attached screenshot.
> Maybe something to do with your system fonts.
Hi Ihor,
Thanks for your reply!
By the way, my emacs command for testing the bug was wrong, now I did it
with =emacs -q=
After vanilla emacs, I did =describe-fontset= for that buffer and got
"google noto sans mono" font (see file 2024-09-09_18-10_google-noto.png )
I changed it to Fira Code Retina with this command =(set-frame-font
"Fira Code Retina" nil t)= ( see file 2024-09-09_18-11_fira-code.png )
As you see in the attached screen captures, I have the same problem with
both fonts, what font do you use?
Cheers,
pinmacs
[-- Attachment #2: 2024-09-09_18-10_google-noto.png --]
[-- Type: image/png, Size: 115767 bytes --]
[-- Attachment #3: 2024-09-09_18-11_fira-code.png --]
[-- Type: image/png, Size: 100614 bytes --]
next prev parent reply other threads:[~2024-09-09 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 21:30 BUG (regression): clocktable with ~:link t~ looks visually inconsistent pinmacs
2024-09-07 17:22 ` Ihor Radchenko
2024-09-09 16:15 ` pinmacs [this message]
2024-09-09 16:19 ` Ihor Radchenko
2024-09-09 16:34 ` pinmacs
2024-09-15 10:16 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2024-09-01 21:10 Pedro
2024-09-07 18:20 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bdab5b42-a661-463c-b30d-9a6161b5c48e@cas.cat \
--to=pinmacs@cas.cat \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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/org-mode.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).