On 6/23/12 10:58 AM, Nicolas Goaziou wrote:
Accented and a variety of other non-ascii characters do work in
targets, IDs and CUSTOM_IDs, in my experience.
Right.
Org-target-regexp is simply "<<\\([^<>]+\\)>>", so it's not
picky. Perhaps the same could be done for macros (replacing angle
brackets with curly braces), without screwing anything up...?
I'd rather do the opposite and restrict them all: this kind of regexp is
slow to parse and there is little gain to allow any character in targets
since they are all invisible now.
My user perspective differs: I'm happy to be able to use my
language(s) freely in Org, even in the invisible bits, and would not
trade it in for a speedup.
That said, I don't particularly mind the status quo on macros. They're
code-like, and we're used to ascii restrictions on computer code.
Yours,
Christian
