From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Fixing link encoding once and for all
Date: Wed, 27 Feb 2019 12:25:55 +0100 [thread overview]
Message-ID: <87h8cpcw1o.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87wollvemz.fsf@wi.uni-muenster.de> (Jens Lechtenboerger's message of "Wed, 27 Feb 2019 09:07:00 +0100")
Hello,
Jens Lechtenboerger <lechten@wi.uni-muenster.de> writes:
> When exporting the following link to LaTeX, the decoding fails.
>
> --8<---------------cut here---------------start------------->8---
> [[https://en.wikipedia.org/wiki/Red%E2%80%93black_tree][Red-black trees]]
> --8<---------------cut here---------------end--------------->8---
According to my suggestion in this thread, this link should be written
[[https://en.wikipedia.org/wiki/Red%25E2%2580%2593black_tree][Red-black trees]]
i.e., either you wrote it by hand, or `org-insert-link' failed.
With the \-escape solution suggested by Neil, it would be correctly
processed without additional change. Of course, that would entail other
difficulties.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-02-27 11:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 1:16 [RFC] Fixing link encoding once and for all Nicolas Goaziou
2019-02-24 23:04 ` Neil Jerram
2019-02-27 10:48 ` Nicolas Goaziou
2019-02-28 10:24 ` Neil Jerram
2019-03-01 8:14 ` Nicolas Goaziou
2019-03-01 8:30 ` Nicolas Goaziou
2019-03-01 8:40 ` Michael Brand
2019-03-01 8:41 ` Jens Lechtenboerger
2019-03-01 8:56 ` Nicolas Goaziou
2019-03-01 9:40 ` Jens Lechtenboerger
2019-03-03 6:58 ` stardiviner
2019-03-03 8:08 ` Nicolas Goaziou
2019-03-04 23:16 ` Neil Jerram
2019-03-05 0:23 ` Nicolas Goaziou
2019-03-05 16:27 ` Neil Jerram
2019-03-05 16:36 ` Robert Pluim
2019-02-25 8:54 ` stardiviner
2019-02-27 8:07 ` Jens Lechtenboerger
2019-02-27 11:25 ` Nicolas Goaziou [this message]
2019-02-27 12:57 ` Jens Lechtenboerger
2019-02-28 10:51 ` Nicolas Goaziou
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=87h8cpcw1o.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.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 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.