From: Kyle Meyer <firstname.lastname@example.org>
To: Jack Kamm <email@example.com>
Subject: Re: [PATCH] New "project" option for org-link-file-path-type
Date: Thu, 05 Nov 2020 22:33:10 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Jack Kamm writes:
> I like the idea of letting org-link-file-path-type be a function.
> However, it struck me that it might be too limiting to just have the
> function return the project root. There's a lot more potential for
> customization here -- for example, a user might want to combine the
> noabbrev option with the adaptive option. If we could instead pass a
> function that takes the filename as an argument and returns the path to
> insert, that would allow for greater flexibility.
> Other benefits are that the implementation is much simpler, and
> subjectively I think it's more intuitive to explain the meaning of this
> option (as opposed to an option where the user passes a function that
> returns the project root).
> The downside of this is that the user has to do a bit more work and
> write some elisp to take advantage of the option.
> I've attached an updated patch in this direction. What do you think? I
> think the simplicity and flexibility outweighs the downside, but I'm not
I think that's a good direction to go (for the reasons you laid out, not
just because it lets me use this with projectile :).
> +++ b/etc/ORG-NEWS
> @@ -35,6 +35,25 @@ omit a file description was to omit the header argument entirely,
> which made it difficult/impossible to provide a default value for
> +*** New option to set ~org-link-file-path-type~ to a function
> +If ~org-link-file-path-type~ can now be set to a function that takes
> +the full filename as an argument and returns the path to link to.
> +For example, if you use ~project.el~, you can set this function to use
> +relative links within a project as follows:
> +#+begin_src emacs-lisp
> +(setq (org-link-file-path-type
> + (lambda (path)
> + (let* ((proj (project-current))
> + (root (if proj (project-root proj) default-directory)))
> + (if (string-prefix-p (expand-file-name root) path)
> + (progn
> + (file-relative-name path))
> + (abbreviate-file-name path))))))
next prev parent reply other threads:[~2020-11-06 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 0:46 [PATCH] New "project" option for org-link-file-path-type Jack Kamm
2020-11-02 5:41 ` Kyle Meyer
2020-11-04 18:11 ` Jack Kamm
2020-11-06 3:33 ` Kyle Meyer [this message]
2020-11-12 1:05 ` Jack Kamm
2021-04-25 3:29 ` Timothy
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).