> gdb) xbacktrace > "avl-tree-delete" (0xffff54b0) > "byte-code" (0xffff55a0) > "byte-code" (0xffff5760) > "org-element--cache-process-request" (0xffff5990) > "byte-code" (0xffff5aa0) > "org-element--cache-sync" (0xffff5ce0) > "org-element-at-point" (0xffff5e00) > "byte-code" (0xffff60d0) > "org-adaptive-fill-function" (0xffff6300) > "fill-match-adaptive-prefix" (0xffff6480) > "fill-context-prefix" (0xffff6620) > "adaptive-wrap-fill-context-prefix" (0xffff67d0) > "adaptive-wrap-prefix-function" (0xffff6a18) > "run-hook-with-args" (0xffff6a10) > 0x4d89f80 PVEC_COMPILED > "funcall" (0xffff6b30) > "jit-lock-fontify-now" (0xffff6e38) > "jit-lock-function" (0xffff6fc8) > "vertical-motion" (0xffffdca8) > "end-of-visual-line" (0xffffde08) > "call-interactively" (0xffffdfc0) > "org-end-of-line" (0xffffe198) > "call-interactively" (0xffffe350) > "command-execute" (0xffffe478)
> I wonder if it is because `org-adaptive-fill-function' doesn't mix well > with `adaptive-wrap-prefix-mode'... As mentioned earlier, the immediate problem is that org-adaptive-fill-function does not terminate (or at least takes too long to terminate). Now, one reason why this might happen here is that adaptive-wrap-prefix-mode calls org-adaptive-fill-function everywhere, so it might be called in places where it usually (i.e. when adaptive-wrap-prefix-mode isn't in use) isn't triggered. Stefan