emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
To: emacs-orgmode@gnu.org
Subject: Question about relative paths generated by Org
Date: Thu, 8 Aug 2024 14:18:04 +0200	[thread overview]
Message-ID: <e87b0e99-bed9-4a6f-9f50-64d08a0476f3@metacode.biz> (raw)

Hello,

I'm using Org-mode's clock feature and it's really great!

One thing bothers me: the links generated by the ":link t" option on the 
clocktable [0] are absolute [1] and it causes problems when using the 
same file on two different machines:

#+BEGIN: clocktable :scope file :maxlevel 3 :link t
#+CAPTION: Clock summary at [2024-08-08 Thu 11:02]
| Headline     | Time   |      |
|--------------+--------+------|
| *Total time* | *4:32* |      |
|--------------+--------+------|
| 
[[file:/home/runner/work/org-test/org-test/README.org::Project][Project]] 
      | 4:32   |      |
| \_  [[file:/home/runner/work/org-test/org-test/README.org::Task 
1][Task 1]]   |        | 3:30 |
| \_  [[file:/home/runner/work/org-test/org-test/README.org::Task 
3][Task 3]]   |        | 1:02 |
#+END:

I've tried adjusting that with `(setq org-link-file-path-type 
'relative)` but it doesn't seem to have any effect on the automatically 
generated clocktable (I ran emacs -nw README.org so the PWD should be 
correct).

Is there anything I could try to make the links relative so that they 
look like this: [[file:README.org::Task 3][Task 3]] ?

I've made a repository for reproducing this case: 
https://github.com/wiktor-k/org-test and I'm using emacs 29.4 and org 
9.6.15.

Thank you for your time and help!

Kind regards,
Wiktor

[0]: https://github.com/wiktor-k/org-test/blob/main/README.org?plain=1#L39

[1]: https://github.com/wiktor-k/org-test/blob/main/README.org?plain=1#L46


             reply	other threads:[~2024-08-09 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 12:18 Wiktor Kwapisiewicz [this message]
2024-08-10 17:03 ` Question about relative paths generated by Org 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=e87b0e99-bed9-4a6f-9f50-64d08a0476f3@metacode.biz \
    --to=wiktor@metacode.biz \
    --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).