From: Ruijie Yu via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: emacs-orgmode@gnu.org
Subject: [FR] Do not resolve relative "file" paths
Date: Mon, 27 Mar 2023 22:36:48 +0800 [thread overview]
Message-ID: <sdvy1nifegv.fsf@fw.net.yu> (raw)
Both Emacs and Org are on recent master commits.
Repro:
--8<---------------cut here---------------start------------->8---
$ cd $(mktemp -d)
$ mkdir 1
$ touch 2
$ emacs -L /org/lisp/ -Q 1/3.org
M-: emacs-repository-version RET
"db7e95531ac36ae842787b6c5f2859d0642c78cc"
M-x org-version RET
Org mode version 9.7-pre (release_9.6.1-321-g44e1cb @ /opt/src/emacs/packages/orgmode/main/lisp/)
C-c C-l file:../4 RET RET
[[file:/tmp/tmp.ztrbRDDtKy/4]]
C-c C-l file:../2 RET RET
[[file:/tmp/tmp.ztrbRDDtKy/2]]
--8<---------------cut here---------------end--------------->8---
Note that I showcased both ../4 and ../2 because it seems that the
referenced file does not need to exist.
I expect the links to be literally [[file:../4]] and [[file:../2]]
respectively. This is helpful for me to reference other files
relatively (e.g., in a repository).
For example, since I am working on translating orgweb to zh_CN, I have
/zh_CN/index.org referencing /resources/img/xyz.svg, where after I do
`C-c C-l file:../resources/img/xyz.svg RET' inside /zh_CN/index.org, Org
resolves this link to an absolute path which is counterproductive and
does not work beyond my own computer.
--
Best,
RY
next reply other threads:[~2023-03-27 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:36 Ruijie Yu via General discussions about Org-mode. [this message]
2023-03-27 14:43 ` [FR] Do not resolve relative "file" paths Ihor Radchenko
2023-03-27 14:59 ` Ruijie Yu via General discussions about Org-mode.
2023-03-28 0:42 ` Samuel Wales
2023-03-27 14:50 ` 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=sdvy1nifegv.fsf@fw.net.yu \
--to=emacs-orgmode@gnu.org \
--cc=ruijie@netyu.xyz \
/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).