From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: [feature] Macros can't contain accents Date: Sun, 24 Jun 2012 09:56:54 +0200 Message-ID: <4FE6C846.80308@christianmoe.com> References: <80ipejruq4.fsf@somewhere.org> <87k3yznmpk.fsf@gmail.com> <4FE55CCB.2000102@christianmoe.com> <87bokao14m.fsf@gmail.com> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34395) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sihbl-0007KG-1n for emacs-orgmode@gnu.org; Sun, 24 Jun 2012 03:51:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sihbj-0007ZV-HV for emacs-orgmode@gnu.org; Sun, 24 Jun 2012 03:51:44 -0400 Received: from plane.gmane.org ([80.91.229.3]:42979) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sihbj-0007ZP-AY for emacs-orgmode@gnu.org; Sun, 24 Jun 2012 03:51:43 -0400 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Sihbf-0006w7-8C for emacs-orgmode@gnu.org; Sun, 24 Jun 2012 09:51:39 +0200 In-Reply-To: <87bokao14m.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org, Sebastien Vauban 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