From: Tobias Getzner <tobias.getzner@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] Mark-up handling chokes on unicode whitespace
Date: Tue, 23 Sep 2014 17:44:19 +0000 (UTC) [thread overview]
Message-ID: <lvsbhj$6al$1@ger.gmane.org> (raw)
In-Reply-To: 87a95qp8vp.fsf@gmail.com
Hello Aaron!
On Tue, 23 Sep 2014 13:03:06 -0400, Aaron Ecay wrote:
> 2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
>>
>> When mark-up such as =monospace=, /italic/, etc. is preceded by a
>> non-8bit whitespace, e. g., «narrow no-break space» (U+202F) or
>> «no-break space» (U+00A0), org-mode will not recognize the mark-up
>> content correctly
>
> You will need to change the variable org-emphasis-regexp-components; see
> the documentation thereof.
Thank you very much! This seems to do it.
Might I suggest amending unicode whitespace to the default? That variable
seems a bit opaque and I might probably never have discovered it on my
own; it also appears as if one has to ensure that this is set before org-
mode is «required», and one cannot easily just extend the default without
also setting the rest. For type-setting purposes, at least the class of
non-breaking whitespace is very useful.
At first I thought it might be easy to cleanly solve such problems by
using the whitespace character class throughout, but to my chagrin it
seems that at least «search-forward-regexp» will only match 8-bit
whitespace this way, so I suppose Emacs regex isn’t aware of non-ASCII
whitespace? :'|
Best,
Tobias
next prev parent reply other threads:[~2014-09-23 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 12:44 [BUG] Mark-up handling chokes on unicode whitespace Tobias Getzner
2014-09-23 17:03 ` Aaron Ecay
2014-09-23 17:44 ` Tobias Getzner [this message]
2014-09-23 18:15 ` Aaron Ecay
2014-09-24 7:34 ` [BUG] Mark-up handling chokes on Unicode white-space Tobias Getzner
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='lvsbhj$6al$1@ger.gmane.org' \
--to=tobias.getzner@gmx.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).