From: "William Léchelle" <firstname.lastname@example.org>
To: emacs-orgmode <email@example.com>
Subject: [bug] org-insert-link fails on special characters in headlines
Date: Fri, 28 Dec 2012 04:58:29 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> > it looks like captured links won't take into account header text after < or
> > >, hence capturing links to headlines featuring these will fail, is there a
> > known issue about accepted characters in headlines that I'm not aware of ?
> There should be none, please test master if you can and report any
Using org-store-link followed by org-insert-link RET RET fails on the following
****** TODO Special chars in titles > !
[[*Special%20chars%20in%20titles%20][Special chars in titles > !]]
The link ignores what follows the greater-than sign (>) and thus the inserted
link is still-broken.
Prior to this, I had some working tests with <, it seems both < and > are
On Mon, 24 Dec 2012 01:56:24 +0100, Bastien spake thus:
> > I suggest the priority is removed from the captured link.
> This is now the case in master, it will be part of 8.0.
next reply other threads:[~2012-12-28 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 3:58 William Léchelle [this message]
2012-12-28 10:04 ` [bug] org-insert-link fails on special characters in headlines Bastien
2013-01-05 23:09 ` William Léchelle
2013-01-06 6:45 ` Bastien
2013-01-14 8:09 ` William Léchelle
2013-01-22 14:40 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).