From: Ihor Radchenko <yantar92@posteo.net>
To: numbchild@gmail.com
Cc: "西 顾" <z.ref@outlook.com>, emacs-orgmode@gnu.org
Subject: Re: [POLL] Change calling convention for when `org-link-file-path-type' is set to custom function (was: Enhancement Proposal for 'org-link-file-path-type' Behavior)
Date: Wed, 17 Jan 2024 13:17:56 +0000 [thread overview]
Message-ID: <87r0ighzej.fsf@localhost> (raw)
In-Reply-To: <65a75fd5.170a0220.b5db2.7472@mx.google.com>
"Christopher M. Miles" <numbchild@gmail.com> writes:
> I have one situation need this feature.
>
> Assume a file structure like bellowing:
>
> #+begin_example
> `- folder-1
> `- file-1.org
> `- folder-1.2
> ` file-1.2.1.org
> #+end_example
>
> When I try to add link of "file-1.org" in "file-1.2.1.org", based on my
> custom option `org-link-file-path-type' value `adaptive'. The link will
> become a full-path link. But I want link to be relative to current Org
> file path. The file link path should be [[file:../file-1.org]] instead
> of [[file:folder-1/file-1.org]]. I hope I can use a custom function in
> conditions to decide the file path.
I think that you do not need to wait for this feature in order to get
what you need. Just examine default-directory in your custom function to
determine whether to return relative or absolute path.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-17 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 12:00 Enhancement Proposal for 'org-link-file-path-type' Behavior 西 顾
2024-01-16 16:06 ` [POLL] Change calling convention for when `org-link-file-path-type' is set to custom function (was: Enhancement Proposal for 'org-link-file-path-type' Behavior) Ihor Radchenko
2024-01-17 4:59 ` Christopher M. Miles
2024-01-17 13:17 ` Ihor Radchenko [this message]
2024-02-17 15:27 ` 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=87r0ighzej.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.com \
--cc=z.ref@outlook.com \
/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).