emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* <<<radio target>>>: stopped working
@ 2012-12-04 19:10 Daniel Clemente
  2012-12-04 19:40 ` Nicolas Goaziou
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel Clemente @ 2012-12-04 19:10 UTC (permalink / raw)
  To: emacs-orgmode; +Cc: n.goaziou


Hi,
  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.


Regards

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: <<<radio target>>>: stopped working
  2012-12-04 19:10 <<<radio target>>>: stopped working Daniel Clemente
@ 2012-12-04 19:40 ` Nicolas Goaziou
  2012-12-04 20:28   ` Nicolas Goaziou
  0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Goaziou @ 2012-12-04 19:40 UTC (permalink / raw)
  To: Daniel Clemente; +Cc: emacs-orgmode

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: <<<radio target>>>: stopped working
  2012-12-04 19:40 ` Nicolas Goaziou
@ 2012-12-04 20:28   ` Nicolas Goaziou
  0 siblings, 0 replies; 3+ messages in thread
From: Nicolas Goaziou @ 2012-12-04 20:28 UTC (permalink / raw)
  To: Daniel Clemente; +Cc: emacs-orgmode

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> 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.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-12-04 20:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-04 19:10 <<<radio target>>>: stopped working Daniel Clemente
2012-12-04 19:40 ` Nicolas Goaziou
2012-12-04 20:28   ` Nicolas Goaziou

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).