Re: Internal links to lines in different org files

2023-02-03 Thread kevin lucas
Thanks for responding. I meant specifically the :: syntax with org IDs, and
not filenames. I did confirm that this feature is currently only in Doom
Emacs, see:
https://github.com/doomemacs/doomemacs/blob/master/modules/lang/org/config.el#L639-L659
Regarding org-export-with-broken-links, is there a way to export the text
of the link, and not kill all the text?

On Wed 1. Feb 2023 at 15:55, Ihor Radchenko  wrote:

> kevin lucas  writes:
>
> > 1. Is this feature indeed specific to Doom Emacs?
> > 2. If this behavior isn’t in org mode, could it be added?
>
> No. It is built-in.
>
> > 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?
>
> See org-export-with-broken-links
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>


Re: Internal links to lines in different org files

2023-02-01 Thread Ihor Radchenko
kevin lucas  writes:

> Thanks for responding. I meant specifically the :: syntax with org IDs, and
> not filenames. I did confirm that this feature is currently only in Doom
> Emacs, see:
> https://github.com/doomemacs/doomemacs/blob/master/modules/lang/org/config.el#L639-L659

I am really curious why Doom author never considered contributing to Org
core. This style with numerous advices is a recipe for eventual
disaster.

> Regarding org-export-with-broken-links, is there a way to export the text
> of the link, and not kill all the text?

Currently, no.

I guess one may add a new possible value to
`org-export-with-broken-links', making it a custom function.

Alternatively, you may override the link transcoder in a custom derived
export backend (see `org-export-define-derived-backend').

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Internal links to lines in different org files

2023-02-01 Thread Ihor Radchenko
kevin lucas  writes:

> 1. Is this feature indeed specific to Doom Emacs?
> 2. If this behavior isn’t in org mode, could it be added?

No. It is built-in.

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

See org-export-with-broken-links

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 



Re: Internal links to lines in different org files

2023-01-28 Thread Max Nikulin

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.






Internal links to lines in different org files

2023-01-28 Thread kevin lucas
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