From: Christoph LANGE <langec@web.de>
To: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: Bug: can't use square brackets in link descriptions;
Date: Tue, 31 Jan 2012 17:19:40 +0100 [thread overview]
Message-ID: <4F28149C.6000700@web.de> (raw)
Dear org-mode developers,
I am desperately trying to get a square bracket into the description of
a link.
That is, in an org file that I want to export to HTML, I would like to
have the source
<a href="http://example.org">foo [bar]</a>
and of course I would like to avoid using XML character entities such as
b; for [, for two reasons:
1. It is painful.
2. I might eventually want to export my org file to some other format
than HTML.
I noticed this post on escaping in org links
(http://article.gmane.org/gmane.emacs.orgmode/37888), but apparently I
didn't understand it.
I thought that escaping as %5B might work – not only in the "link"
component of a link, where it works due to the specification of URIs,
but also in the "description" component, but in the description it
doesn't work.
Quite generally, I wonder whether there is (or, why there is not) a
generic escape character (e.g. the backslash), which would also allow
for escaping other characters of the org markup syntax, such as * or /.
So far this was something like a feature request, but there is also one
actual bug:
When I insert or edit a link with org-insert-link (C-c C-l) and insert
square brackets into the link description, they are rewritten to {...},
which I do not consider acceptable. If there is any escape syntax, they
should rather be rewritten using that escape syntax.
Thanks in advance for any pointers,
Christoph
--
Christoph Lange, http://www.facebook.com/ch.lange, Skype duke4701
next reply other threads:[~2012-01-31 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:19 Christoph LANGE [this message]
2012-01-31 21:43 ` Bug: can't use square brackets in link descriptions; Christian Moe
-- strict thread matches above, loose matches on Subject: below --
2012-01-31 16:20 Christoph LANGE
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=4F28149C.6000700@web.de \
--to=langec@web.de \
--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 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).