emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Aaron Ecay <aaronecay@gmail.com>
To: Tobias Getzner <tobias.getzner@gmx.de>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Mark-up handling chokes on unicode whitespace
Date: Tue, 23 Sep 2014 14:15:53 -0400	[thread overview]
Message-ID: <87ppemnqxy.fsf@gmail.com> (raw)
In-Reply-To: <lvsbhj$6al$1@ger.gmane.org>

Hi Tobias,

2014ko irailak 23an, Tobias Getzner-ek idatzi zuen:
> 
> Hello Aaron!
> 
> On Tue, 23 Sep 2014 13:03:06 -0400, Aaron Ecay wrote:
> 
>> 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.

org-emphasis-regexp-components is known to be a wart.  You can search
for posts on the mailing list.  Some people are trying to figure out how
to get rid of it.  (You can search in particular for Nicolas Goaziou’s
posts...)  Here’s one thread where you can see the lay of the land:
<http://mid.gmane.org/87zjl6ktu2.fsf@gmail.com>.

All that to say, the longer-term solution is to figure out some radically
different approach.  In the meantime though, if you can provide a list of
characters (by unicode name and/or code point) that you think should be
added to that variable, someone might be able to add them.  (I probably
would not make such a change on my own, but would wait for feedback from
Nicolas, Bastien, or one of the other maintainer-esque figures on the
list).  On the other hand, they might say “making such a change in org’s
core is just restacking the deck chairs on the Titanic,” which would
also be a reasonable position for them to take IMO.

> 
> 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? :'|

I don’t really know anything about this...it’s unfortunate if true
though.

-- 
Aaron Ecay

next prev parent reply	other threads:[~2014-09-23 18:16 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
2014-09-23 18:15     ` Aaron Ecay [this message]
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=87ppemnqxy.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tobias.getzner@gmx.de \
    /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

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).