From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: <<>>: stopped working Date: Tue, 04 Dec 2012 21:28:17 +0100 Message-ID: <87vcchtvdq.fsf@gmail.com> References: <87zk1t3a6s.wl%n142857@gmail.com> <8738zlvc6g.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:49660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TfzAR-000846-7O for emacs-orgmode@gnu.org; Tue, 04 Dec 2012 15:32:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TfzAL-000553-C4 for emacs-orgmode@gnu.org; Tue, 04 Dec 2012 15:32:35 -0500 Received: from mail-wg0-f51.google.com ([74.125.82.51]:58480) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TfzAL-00054z-6A for emacs-orgmode@gnu.org; Tue, 04 Dec 2012 15:32:29 -0500 Received: by mail-wg0-f51.google.com with SMTP id gg4so1914084wgb.30 for ; Tue, 04 Dec 2012 12:32:28 -0800 (PST) In-Reply-To: <8738zlvc6g.fsf@gmail.com> (Nicolas Goaziou's message of "Tue, 04 Dec 2012 20:40:07 +0100") 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: Daniel Clemente Cc: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Daniel Clemente writes: > >> in the latest org-mode and emacs (both compiled today), global radio targets <<>> are colored as such and work, but <<>>, because there's a comma after the > >> >> I used bisect to find where it stopped working and got to: >> >> ce8819f18d9d2be000fb70fc4d74b5d96fe07a83 is the first bad commit >> >> This was about org-element and included something for <>; maybe it needs tests for <<>> too. > > I confirm the problem. > > Though, it is totally unrelated to Org Elements. To convince yourself, > put point on the faulty radio and call M-: (org-element-context). This > will return a radio-target element. IOW, the parser properly detects the > right object. Never mind. I know where the problem lies. I will fix it as soon as I can have access to the repository (which looks down). Regards, -- Nicolas Goaziou