> We can probably close this bug.
> I haven't been able to reproduce it with the org-mode bundled with the
> pretest version.
Thanks, done.
> Sorry for the noise.
Better luck next time,
Stefan
We can probably close this bug.
I haven't been able to reproduce it with the org-mode bundled with the
pretest version.
Sorry for the noise.
Regards,
--
Daimrod/Greg
Bastien writes:
> Daimrod writes:
>
>> Bastien writes:
>>
>>> Daimrod writes:
>>>
I wonder if it is because `org-adaptive-fill-function' doesn't mix well
with `adaptive-wrap-prefix-mode'...
>>>
>>> (Nicolas has been doing some rewrite for filling functions in the
>>> master branch, m
Daimrod writes:
> Bastien writes:
>
>> Daimrod writes:
>>
>>> I wonder if it is because `org-adaptive-fill-function' doesn't mix well
>>> with `adaptive-wrap-prefix-mode'...
>>
>> (Nicolas has been doing some rewrite for filling functions in the
>> master branch, maybe it's worth checking wheth
Bastien writes:
> Daimrod writes:
>
>> I wonder if it is because `org-adaptive-fill-function' doesn't mix well
>> with `adaptive-wrap-prefix-mode'...
>
> (Nicolas has been doing some rewrite for filling functions in the
> master branch, maybe it's worth checking whether this bug affects
> the ma
Daimrod writes:
> I wonder if it is because `org-adaptive-fill-function' doesn't mix well
> with `adaptive-wrap-prefix-mode'...
(Nicolas has been doing some rewrite for filling functions in the
master branch, maybe it's worth checking whether this bug affects
the master branch too, not just the
> Is there a way to disable the effect of `inhibit-quit' in `jit-lock' so
> C-g interrupt again in order to get an elisp-backtrace with
> `debug-on-quit'.
> Otherwise, what's the best way to debug this? Looking closer at
> `org-adaptive-fill-function'?
You can try `debug-on-event'.
There's jit-lo
Stefan Monnier writes:
>> gdb) xbacktrace
>> "avl-tree-delete" (0x54b0)
>> "byte-code" (0x55a0)
>> "byte-code" (0x5760)
>> "org-element--cache-process-request" (0x5990)
>> "byte-code" (0x5aa0)
>> "org-element--cache-sync" (0x5ce0)
>> "org-element-at-point" (0x5e00)
>>
> gdb) xbacktrace
> "avl-tree-delete" (0x54b0)
> "byte-code" (0x55a0)
> "byte-code" (0x5760)
> "org-element--cache-process-request" (0x5990)
> "byte-code" (0x5aa0)
> "org-element--cache-sync" (0x5ce0)
> "org-element-at-point" (0x5e00)
> "byte-code" (0x60d0)
> "org-ad
Daimrod writes:
> Stefan Monnier writes:
>
>>> So, that's an org-mode bug, I'll try to see if I can reproduce it
>>
>> Right: org-adaptive-fill-function should finish fairly promptly.
>>
>>> (though I wonder why it uses `inhibit-quit' in the first place).
>>
>> It's not org-mode which binds inhi
Stefan Monnier writes:
>> So, that's an org-mode bug, I'll try to see if I can reproduce it
>
> Right: org-adaptive-fill-function should finish fairly promptly.
>
>> (though I wonder why it uses `inhibit-quit' in the first place).
>
> It's not org-mode which binds inhibit-quit but the C code that
> So, that's an org-mode bug, I'll try to see if I can reproduce it
Right: org-adaptive-fill-function should finish fairly promptly.
> (though I wonder why it uses `inhibit-quit' in the first place).
It's not org-mode which binds inhibit-quit but the C code that runs
jit-lock. The C code binds
12 matches
Mail list logo
