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

From: kevin lucas <lucaskevin296@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Internal links to lines in different org files
Date: Wed, 1 Feb 2023 16:04:24 +0100	[thread overview]
Message-ID: <CACESMjK2ACCwdDSrgopiaQ2kJqvffC7BQtsZj8eSufRJ4VpeRg@mail.gmail.com> (raw)
In-Reply-To: <87fsbpjuy4.fsf@localhost>

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

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 <yantar92@posteo.net> wrote:

> kevin lucas <lucaskevin296@gmail.com> 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 <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
>

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

next prev parent reply	other threads:[~2023-02-03 13:13 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
2023-02-01 14:56 ` Ihor Radchenko
2023-02-01 15:04   ` kevin lucas [this message]
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=CACESMjK2ACCwdDSrgopiaQ2kJqvffC7BQtsZj8eSufRJ4VpeRg@mail.gmail.com \
    --to=lucaskevin296@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).