Carsten Dominik <[EMAIL PROTECTED]> writes:
Hi Carsten,
> There is a lot of code happening between the moment of the match, and
> the replacement. So far none of this code seems to have had the
> effect of changing the match data, I have been careful to avoid this.
> However, in your case it see
There is a lot of code happening between the moment of the match, and
the
replacement. So far none of this code seems to have had the effect of
changing the match data, I have been careful to avoid this. However,
in your case it seems that some internal code does change it.
I believe the foll
Bastien <[EMAIL PROTECTED]> writes:
Hi Bastien,
> Mhh... strange, I still cannot reproduce here with a minimal config.
> Can you debug step by step in this case?
It fails in line 13497 of org.el (the call to replace-match). Here's
the edebug output so far.
--8<---cut here-
Tassilo Horn <[EMAIL PROTECTED]> writes:
> Yes. I even get it with emacs -Q and only the two settings
>
> (setq org-use-fast-todo-selection t
> org-todo-keywords '((sequence "TODO(t)" "STARTED(s)" "WAITING(w)"
> "|" "DONE(d)" "DEFERRED(f)"
> "CANCELLED(c
Bastien <[EMAIL PROTECTED]> writes:
Hi Bastien,
>> I didn't follow the org development for the last few weeks, so maybe
>> this is no bug but a misconfiguration by me.
>
> What version of Org are you using?
>
> I cannot reproduce your problem here with latest Org 5.13e.
Same here.
>> When I wan
Carsten Dominik <[EMAIL PROTECTED]> writes:
Hi Carsten,
> I cannot reproduce this.
Hm, I use a Emacs checkout from this morning which comes with org 5.13e,
but I noticed that behavior earlier.
I can reproduce the problem like this:
1. emacs -Q
2. Switch to *scratch* and eval
(setq org-use
