From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Subject: Re: [feature] Macros can't contain accents
Date: Sun, 24 Jun 2012 09:56:54 +0200 [thread overview]
Message-ID: <4FE6C846.80308@christianmoe.com> (raw)
In-Reply-To: <87bokao14m.fsf@gmail.com>
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
prev parent reply other threads:[~2012-06-24 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 19:51 [feature] Macros can't contain accents Sebastien Vauban
2012-06-22 19:57 ` Nicolas Goaziou
[not found] ` <4FE55CCB.2000102@christianmoe.com>
2012-06-23 8:58 ` Nicolas Goaziou
2012-06-24 7:56 ` Christian Moe [this message]
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=4FE6C846.80308@christianmoe.com \
--to=mail@christianmoe.com \
--cc=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).