From: "Berry, Charles" <ccberry@ucsd.edu>
To: Ryan Thompson <rct@thompsonclan.org>
Cc: Org-Mode List <emacs-orgmode@gnu.org>
Subject: Re: Feature request: Allow export to convert broken links to plain text
Date: Sun, 13 Jan 2019 17:50:57 +0000 [thread overview]
Message-ID: <6DD23F17-400A-468E-B637-5E2A9C7995DD@ucsd.edu> (raw)
In-Reply-To: <CAHCt_aYZggarRi6yHbG6RvwhvcbWbKSKdHs0Kw3QkkF2zAEnQw@mail.gmail.com>
> On Jan 12, 2019, at 12:38 PM, Ryan Thompson <rct@thompsonclan.org> wrote:
>
> Hi all,
>
> I have a use case where I'd like for Org Mode to remove broken links while preserving their text when exporting. In particular, I'm exporting the same file multiple times with different sets of headlines excluded each time, and as a result I have to be careful of linking to headlines that might not be present in every export. It would be much easier if such links could simply be converted back to plain text for that export, while remaining as a link for any exports that *do* include the target headline. None of the existing settings do quite what I want. The "mark" option comes closest.
> I basically want "mark" but without adding any additional text around the link's text.
Sounds like a good use case for a filter. See
(info "(org) Advanced Export Configuration")
and scroll down to the `Filters' section.
Just use the `broken-links:mark' option and set up your link filter to strip the `BROKEN LINK:' part.
HTH,
Chuck
next prev parent reply other threads:[~2019-01-13 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 20:38 Feature request: Allow export to convert broken links to plain text Ryan Thompson
2019-01-12 20:42 ` Ryan Thompson
2019-01-13 17:50 ` Berry, Charles [this message]
2019-01-13 21:33 ` Ryan Thompson
2019-01-13 22:34 ` Berry, Charles
2023-09-10 4:13 ` Ryan C. Thompson
2023-09-11 17:12 ` Berry, Charles
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 22:55 Janek Fischer
2023-04-15 6:50 ` Hanno Perrey
2023-04-17 13:56 ` Ihor Radchenko
2019-01-05 20:57 Ryan Thompson
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=6DD23F17-400A-468E-B637-5E2A9C7995DD@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=rct@thompsonclan.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
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 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).