From: Simon Thum <simon.thum@gmx.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>,
emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: non-standard link errors
Date: Wed, 2 Mar 2016 11:46:35 +0100 [thread overview]
Message-ID: <56D6C48B.9070509@gmx.de> (raw)
In-Reply-To: <87twkpp6tl.fsf@nicolasgoaziou.fr>
Hi,
after some testing I see my assumption that without export function no
links are generated was wrong. All fine, and thanks for your
tirelessness in explaining it so even I get it ;)
Cheers,
Simon
On 03/02/2016 10:28 AM, Nicolas Goaziou wrote:
> Hello,
>
> Simon Thum <simon.thum@gmx.de> writes:
>
>> this reminds me of my issue with tel: links. I also would have
>> preferred to have them exported "pass-through", but AFAICT this
>> requires me to come up with a trival function for every possible
>> backend: those I know, those I don't, and those that may not exist
>> yet.
>>
>> I cannot switch to the raw: solution (due to vcard export). I'm not
>> currently experiencing problems, but I would like to suggest that
>> maybe such a trival default handler could be added to the backends as
>> some well-known property to be available to those who set the broken
>> link handler to e.g. 'fallback. The onus would be on the user to do
>> this, since correctness of output may suffer. Of course, basic
>> sanitation should still be done in such a handler, but preferably no
>> spectacular failure*.
>
> As I explained, there is already a default handler in every major
> back-end.
>
> However, Org needs to tell links with a type from the others (internal
> links). This is what `org-add-link-type' is for. This has nothing to do
> with export.
>
> To put it differently, when Org encounters a foo:bar link, there are two
> options. Either "foo" is a registered link type, or not. If the former,
> Org tries to use whatever export function was provided, or fall-backs to
> the default handler. In the latter, Org considers it to be an internal
> link. Since there is probably no #+NAME: foo:bar, <<foo:bar>>
> or * foo:bar in the document, the export process returns an error, by
> default.
>
>
> Regards,
>
prev parent reply other threads:[~2016-03-02 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 18:25 non-standard link errors Skip Collins
2016-02-26 21:56 ` Nicolas Goaziou
2016-02-27 18:23 ` Skip Collins
2016-02-28 8:28 ` Nicolas Goaziou
2016-02-29 4:04 ` Skip Collins
2016-02-29 18:10 ` Nicolas Goaziou
2016-03-02 9:11 ` Simon Thum
2016-03-02 9:28 ` Nicolas Goaziou
2016-03-02 10:46 ` Simon Thum [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
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=56D6C48B.9070509@gmx.de \
--to=simon.thum@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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 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).