Ideas to generate unique search context for id:links

Ideas to generate unique search context for id:links

[Kepa]

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Hi

I'm exploring the new option implemented in org 9.7:

"id: links support search options like [[id:my-id::*child heading]]: Any 
valid fuzzy location will work as a search option."


Do you use any way to generate UNIQUE search contexts?


I was thinking about submitting this feature request, but probably it 
will have caveats:

If the search context is in the form "fn:number", update that "number" 
too when normalizing footnotes (org-footnote-normalize.

For example:

* headline 1

:PROPERTIES:
:ID:       2024-08-25T121008356645
:END:

blah blah [fn:20] blah

* headline 2

The goal is to automatically create unique search contexts using the 
features of the footnotes, like in this link to 
[[id:2024-08-25T121008356645::fn:20][blah]]


[-- Attachment #2: Type: text/html, Size: 1227 bytes --]

Re: Ideas to generate unique search context for id:links

[Kepa]

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

> Ideas to generate unique search context for id:links
> From:     Kepa
> Subject:     Ideas to generate unique search context for id:links
> Date:     Sun, 25 Aug 2024 13:07:01 +0200
> Hi
>
> I'm exploring the new option implemented in org 9.7:
>
> "id: links support search options like [[id:my-id::*child heading]]: 
> Any valid fuzzy location will work as a search option."
>
>
> Do you use any way to generate UNIQUE search contexts?
>
>
> I was thinking about submitting this feature request, but probably it 
> will have caveats:
>
> If the search context is in the form "fn:number", update that "number" 
> too when normalizing footnotes (org-footnote-normalize.
>
> For example:
>
> * headline 1
>
> :PROPERTIES:
> :ID:       2024-08-25T121008356645
> :END:
>
> blah blah [fn:20] blah
>
> * headline 2
>
> The goal is to automatically create unique search contexts using the 
> features of the footnotes, like in this link to 
> [[id:2024-08-25T121008356645::fn:20][blah]]

Caveat 1: If the footnote reference has not a footnote definition, 
after (org-footnote-normalize) a definition proposal appears (even if 
Org Footnote Define Inline is set to "t").

Caveat 2: If the proposed "id:link" is in a different file than the 
footnote reference, it could be impractical updating its fn:number with 
(org-footnote-normalize).

Interesting option: setting Org Footnote Auto Label to "Create a random 
label" could work as it is to generate unique search contexts. Just 
never, never, ever  (org-footnote-normalize) should be used.


[-- Attachment #2: Type: text/html, Size: 2362 bytes --]

Re: Ideas to generate unique search context for id:links

[Ihor Radchenko]

Kepa <gnu.cognition199@slmails.com> writes:

> I'm exploring the new option implemented in org 9.7:
>
> "id: links support search options like [[id:my-id::*child heading]]: Any 
> valid fuzzy location will work as a search option."
>
> ...
> I was thinking about submitting this feature request, but probably it 
> will have caveats:
>
> If the search context is in the form "fn:number", update that "number" 
> too when normalizing footnotes (org-footnote-normalize.
>
> For example:
>
> * headline 1
>
> :PROPERTIES:
> :ID:       2024-08-25T121008356645
> :END:
>
> blah blah [fn:20] blah
>
> * headline 2
>
> The goal is to automatically create unique search contexts using the 
> features of the footnotes, like in this link to 
> [[id:2024-08-25T121008356645::fn:20][blah]]

fn:20 is not a supported search term.
For example, [[fn:20]] link will not work.
[fn:20] is special - it is a footnote reference, not link.

-- 
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>