all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: kevin lucas <lucaskevin296@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Internal links to lines in different org files
Date: Wed, 01 Feb 2023 15:14:06 +0000	[thread overview]
Message-ID: <875yclju4h.fsf@localhost> (raw)
In-Reply-To: <CACESMjK2ACCwdDSrgopiaQ2kJqvffC7BQtsZj8eSufRJ4VpeRg@mail.gmail.com>

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


      reply	other threads:[~2023-02-01 15:14 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
2023-02-01 15:14     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yclju4h.fsf@localhost \
    --to=yantar92@posteo.net \
    --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
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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.