emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Kepa <gnu.cognition199@slmails.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Ideas to generate unique search context for id:links
Date: Sun, 01 Sep 2024 17:55:01 +0000	[thread overview]
Message-ID: <87h6azp8cq.fsf@localhost> (raw)
In-Reply-To: <172458403079.9.14394725843089748827.415077079@slmails.com>

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>


  reply	other threads:[~2024-09-01 17:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-25 11:07 Ideas to generate unique search context for id:links Kepa
2024-09-01 17:55 ` Ihor Radchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-25 17:42 Kepa

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=87h6azp8cq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=gnu.cognition199@slmails.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).