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

From: Max Nikulin <manikulin@gmail.com>
To: kevin lucas <lucaskevin296@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Internal links to lines in different org files
Date: Sat, 28 Jan 2023 22:25:11 +0700	[thread overview]
Message-ID: <e7059f70-2cda-203a-e461-6aca00466fdc@gmail.com> (raw)
In-Reply-To: <CACESMj+2ovHj9w4Tz7Eu8GjLOCD7npB7VW7qfnvxVvYybQaArw@mail.gmail.com>

On 28/01/2023 19:35, kevin lucas wrote:
> 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.

Usually links in org start with "type:" prefix. I can not say it for 
sure, but your link looks like a fuzzy link (search in the same file).

I recommend you to run

     M-x org-link RET

for a report on possible issues with your file.

> 2. If this behavior isn’t in org mode, could it be added?

First of all, have a look into (info "(org) Search Options") 
https://orgmode.org/manual/Search-Options.html
Notice "file:" type of the links.

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

Export may be affected by some bugs. Try to open PDF file in a browser 
to inspect what is the target of the exported link.

next prev parent reply	other threads:[~2023-01-28 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 12:35 Internal links to lines in different org files kevin lucas
2023-01-28 15:25 ` Max Nikulin [this message]
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=e7059f70-2cda-203a-e461-6aca00466fdc@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lucaskevin296@gmail.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

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