[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should org-link-parser add type "file" when link has no "file:" pref
From: |
Ihor Radchenko |
Subject: |
Re: Should org-link-parser add type "file" when link has no "file:" prefix? |
Date: |
Thu, 01 Feb 2024 12:23:26 +0000 |
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.
--
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>
- Re: Should org-link-parser add type "file" when link has no "file:" prefix?,
Ihor Radchenko <=