emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: a4ofubmq@anonaddy.com
Cc: emacs-orgmode@gnu.org
Subject: [FR] Allow searching by outline path in file: links to Org files [file:<filename::*parent heading::*child] (was: org-store-link relative to parent headings)
Date: Sun, 13 Oct 2024 11:19:39 +0000	[thread overview]
Message-ID: <87v7xwz1v8.fsf@localhost> (raw)
In-Reply-To: <cee83d4d2edacdc40bd4c705aa6cd709@anonaddy.com>

a4ofubmq@anonaddy.com writes:

> there is ambiguity right now if you want to org-store-link to heading 2
>> subheading 1. By default org stores
> [[file:<FILENAME>::*subheading1]], which would incorrectly point to
> heading 1.
>
> Instead it could be [[file:<FILENAME>::*heading 2**subheading1]]
>
> Please let me know what you think, if this has been already suggested.
> I know that you could create unique UUID in PROPERTIES, but wouldn't it
> be more informative if org-store-link used parent headings instead? I
> think it would be more elegant and not dissimilar from other popular
> addressing schemes (e.g. file paths or urls).

I think that such feature does make sense.
In a way, we already use something similar in org-refile - search by
outline path.

I am not sure if I like the format you proposed though.
Maybe we can instead try to implement nested search options. Something
like [file:<filename>::*heading 2::*subheading1]

You may refer to the existing code in `org-id-open' that allows to
narrow down link search to an existing subtree.

-- 
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-10-13 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 23:24 org-store-link relative to parent headings a4ofubmq
2024-10-13 11:19 ` Ihor Radchenko [this message]

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=87v7xwz1v8.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=a4ofubmq@anonaddy.com \
    --cc=emacs-orgmode@gnu.org \
    /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).