emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: kevin lucas <lucaskevin296@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Internal links to lines in different org files
Date: Sat, 28 Jan 2023 13:35:07 +0100	[thread overview]
Message-ID: <CACESMj+2ovHj9w4Tz7Eu8GjLOCD7npB7VW7qfnvxVvYybQaArw@mail.gmail.com> (raw)

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

A neat little feature that as far as I can tell is only available in Doom
Emacs is the ability to link to specific labeled lines from different org
files. So for instance when I use org-roam I can in an org file with ID foo
label a block of code with #+name: my_code and then from a different org
file write a link like [[foo::my_code][Some code]] and have it refer back
to the exact line in the first file.

I have several questions:

1. Is this feature indeed specific to Doom Emacs? Looking at the code that
gets called it seems there were modifications in Doom to org-id that allow
appending a name to an org ID using double colons in this way. I’ve asked
in a number of other forums and no one has been able to replicate this
outside Doom.
2. If this behavior isn’t in org mode, could it be added?
3. Connected to this: if I export an org file containing an ordinary link
to another node to PDF, the PDF compiles and I get a dead link in the file.
If one tries to export org files with these double colon links there's an
error message `Unable to resolve ID "foo::myname"`. Is there a way to
generate the PDF just like in the first case?

Thanks,
Kevin

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

next             reply	other threads:[~2023-01-28 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 12:35 kevin lucas [this message]
2023-01-28 15:25 ` Internal links to lines in different org files Max Nikulin
2023-02-01 14:56 ` Ihor Radchenko
2023-02-01 15:04   ` kevin lucas
2023-02-01 15:14     ` 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=CACESMj+2ovHj9w4Tz7Eu8GjLOCD7npB7VW7qfnvxVvYybQaArw@mail.gmail.com \
    --to=lucaskevin296@gmail.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

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