From: joseph@ushin.org
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org, "Adam Porter" <adam@alphapapa.net>
Subject: Re: Should org-link-parser add type "file" when link has no "file:" prefix?
Date: Fri, 02 Feb 2024 04:35:13 +0000 [thread overview]
Message-ID: <c7a1b9e705b4c961d1906cb1ec9f7d1f3b6d8775@ushin.org> (raw)
In-Reply-To: <87v878gypt.fsf@localhost>
February 1, 2024 at 4:23 AM, "Ihor Radchenko" <yantar92@posteo.net> wrote:
>
> joseph@ushin.org writes:
>
> >
> > >
> > > > > What we can do then is pass an extra argument to :follow function - the
> > >
> > > > > link object. That way, :follow function can get all the information it
> > >
> > > > > needs.
> > >
> > > > >
> > >
> > > >
> > >
> > > > I like this idea! Would this change break existing :follow functions
> > >
> > > > which only expect max two args?
> > >
> > > >
> > >
> > >
> > >
> > > No. We can preserve backwards-compatibility by checking :follow function
> > >
> > > arity and only passing the extra argument with the :follow function
> > >
> > > supports that many arguments.
> > >
> >
> > Good to know. If the goals of hyperdrive.el can be accomplished without adding complexity to Org mode, it may be best to avoid avoid adding another argument to :follow functions. WDYT?
> >
>
> I did not make any changes to Org mode. And I will not, unless we need
>
> to pass this extra information to :follow functions.
Thank you! I think we can close this issue. Can I close the issue myself?
> --
>
> Ihor Radchenko // yantar92,
>
> Org mode contributor,
>
> Learn more about Org mode at <https://orgmode.org/> https://orgmode.org/%3E .
>
> Support Org development at <https://liberapay.com/org-mode>, https://liberapay.com/org-mode%3E,
>
> or support my work at <https://liberapay.com/yantar92> https://liberapay.com/yantar92%3E
>
next prev parent reply other threads:[~2024-02-02 4:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 4:12 Should org-link-parser add type "file" when link has no "file:" prefix? Joseph Turner
2023-12-29 14:49 ` Ihor Radchenko
2023-12-29 22:05 ` Joseph Turner
2023-12-30 21:12 ` Joseph Turner
2023-12-31 15:07 ` Ihor Radchenko
2024-01-01 6:52 ` Joseph Turner
2024-01-02 13:20 ` Ihor Radchenko
2024-01-14 7:10 ` Joseph Turner
2024-01-16 13:40 ` Ihor Radchenko
2024-01-16 20:16 ` Joseph Turner
2024-01-17 13:15 ` Ihor Radchenko
2024-01-31 22:10 ` joseph
2024-02-01 12:23 ` Ihor Radchenko
2024-02-02 4:35 ` joseph [this message]
2024-02-02 16:01 ` 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=c7a1b9e705b4c961d1906cb1ec9f7d1f3b6d8775@ushin.org \
--to=joseph@ushin.org \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).