From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou <n.goaziou@gmail.com> Subject: Re: <<<radio target>>>: stopped working Date: Tue, 04 Dec 2012 20:40:07 +0100 Message-ID: <8738zlvc6g.fsf@gmail.com> References: <87zk1t3a6s.wl%n142857@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org> Received: from eggs.gnu.org ([208.118.235.92]:37498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <n.goaziou@gmail.com>) id 1TfyPu-00087o-S6 for emacs-orgmode@gnu.org; Tue, 04 Dec 2012 14:44:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <n.goaziou@gmail.com>) id 1TfyPq-0000py-RO for emacs-orgmode@gnu.org; Tue, 04 Dec 2012 14:44:30 -0500 Received: from mail-wg0-f41.google.com ([74.125.82.41]:46122) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <n.goaziou@gmail.com>) id 1TfyPq-0000pm-KT for emacs-orgmode@gnu.org; Tue, 04 Dec 2012 14:44:26 -0500 Received: by mail-wg0-f41.google.com with SMTP id ds1so545753wgb.0 for <emacs-orgmode@gnu.org>; Tue, 04 Dec 2012 11:44:25 -0800 (PST) In-Reply-To: <87zk1t3a6s.wl%n142857@gmail.com> (Daniel Clemente's message of "Tue, 04 Dec 2012 20:10:35 +0100") List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>, <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode> List-Post: <mailto:emacs-orgmode@gnu.org> List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>, <mailto:emacs-orgmode-request@gnu.org?subject=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 <n142857@gmail.com> Cc: emacs-orgmode@gnu.org Hello, Daniel Clemente <n142857@gmail.com> writes: > in the latest org-mode and emacs (both compiled today), global radio targets <<<like this one>>> are colored as such and work, but <<<this one is not detected>>>, 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 <<radio>>; maybe it needs tests for <<<radio>>> 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. Regards, -- Nicolas Goaziou