From: Pedro <pedro@cas.cat>
To: emacs-orgmode@gnu.org
Subject: BUG (regression): clocktable with ~:link t~ looks visually inconsistent
Date: Sun, 1 Sep 2024 23:10:41 +0200 [thread overview]
Message-ID: <7536c4a1-a379-4e78-8fee-70097a07dfda@cas.cat> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 402 bytes --]
Hi,
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
Cheers,
pinmacs
[-- Attachment #1.1.2: 2024-09-01_23-05_clocktable-detail.png --]
[-- Type: image/png, Size: 54862 bytes --]
[-- Attachment #1.1.3: clocktable-link-bug.org --]
[-- Type: text/org, Size: 1579 bytes --]
* [2024-08-31 Sat]
:PROPERTIES:
:CREATED: [2024-09-01 Sun 23:00]
:CUSTOM_ID: clocktable-link-bug_2
:END:
** DONE task1
:LOGBOOK:
CLOCK: [2024-08-31 Sat 22:45]--[2024-08-31 Sat 22:56] => 0:11
:END:
* [2024-09-01 Sun]
:PROPERTIES:
:CREATED: [2024-09-01 Sun 23:00]
:CUSTOM_ID: clocktable-link-bug_1
:END:
** DONE task2
:LOGBOOK:
CLOCK: [2024-09-01 Sun 22:30]--[2024-09-01 Sun 22:56] => 0:26
:END:
clocktable with ~:link nil~ shows it fine
#+NAME: my_clocktable_without_link
#+BEGIN: clocktable :maxlevel 4 :scope file :link nil
#+CAPTION: Clock summary at [2024-09-01 Sun 23:03]
| Headline | Time | |
|------------------+------+------|
| Total time | 0:37 | |
|------------------+------+------|
| [2024-08-31 Sat] | 0:11 | |
| \_ task1 | | 0:11 |
| [2024-09-01 Sun] | 0:26 | |
| \_ task2 | | 0:26 |
#+END
clocktable with ~:link nil~ shows it bad
#+NAME: my_clocktable
#+BEGIN: clocktable :maxlevel 4 :scope file :link t
#+CAPTION: Clock summary at [2024-09-01 Sun 23:03]
| Headline | Time | |
|-------------------+------+------|
| Total time | 0:37 | |
|-------------------+------+------|
| [[file:/home/music/clocktable-link-bug.org::*\[2024-08-31 Sat\]][[2024-08-31 Sat]]] | 0:11 | |
| \_ [[file:/home/music/clocktable-link-bug.org::*task1][task1]] | | 0:11 |
| [[file:/home/music/clocktable-link-bug.org::*\[2024-09-01 Sun\]][[2024-09-01 Sun]]] | 0:26 | |
| \_ [[file:/home/music/clocktable-link-bug.org::*task2][task2]] | | 0:26 |
#+END
[-- Attachment #1.1.4: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3323 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next reply other threads:[~2024-09-04 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 21:10 Pedro [this message]
2024-09-07 18:20 ` BUG (regression): clocktable with ~:link t~ looks visually inconsistent Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2024-09-01 21:30 pinmacs
2024-09-07 17:22 ` Ihor Radchenko
2024-09-09 16:15 ` pinmacs
2024-09-09 16:19 ` Ihor Radchenko
2024-09-09 16:34 ` pinmacs
2024-09-15 10:16 ` 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=7536c4a1-a379-4e78-8fee-70097a07dfda@cas.cat \
--to=pedro@cas.cat \
--cc=emacs-orgmode@gnu.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.
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).