From: Betty <firstname.lastname@example.org>
Subject: How to stop Org mode from assuming non-Latin characters after "[[link]]" as part of the link?
Date: Fri, 17 Aug 2012 00:01:10 +0800 [thread overview]
Message-ID: <CAKmerWgRwUrhDaz4d2Vn9BUuaEia8NVhp02bFfS+ytt9FHT=Nw@mail.gmail.com> (raw)
If I don't put a space after a URL, Org always assumes that all
characters after the link are part of the link. For example, if I
Org will think the URL is "http://example.com]]asdf" while it should
In English there is usually a space after each word (including links)
anyway, so that might not be a big issue. But what about non-Latin
For instance, in Chinese, we don't use spaces to delimit words, and I
really don't want to deteriorate the Chinese language by adding extra
spaces just to make the links work properly. The result is, If I put a
URL in and don't add an extra space after it, Org will think all the
(Chinese) characters I enter after the URL is part of the link, until
the end of paragraph where I press RET.
Well, I know that "]" is a valid URL character, which makes things a
bit tricky. But it is very rare that a URL should contain both "]]"
and non-Latin characters immediately following the "]]". It is a safer
bet to assume the URL is just the part before "]]". On the rare
occasions when the URL does contain "]]" followed by non-Latin
characters, I'm willing to take the risk of breaking it.
In sum, I want Org to take only stuff inside the "[]" brackets as
the URL, nothing after. Is there a place where I can configure this?
Thank you for reading this and for any help you might provide.
(English is not my native tongue. I hope I have make myself clear.)
next reply other threads:[~2012-08-16 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 16:01 Betty [this message]
2012-08-19 14:58 ` How to stop Org mode from assuming non-Latin characters after "[[link]]" as part of the link? Bastien
2012-08-19 16:17 ` Takaaki ISHIKAWA
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).