1. solved: sent that other answer to the list too 2. now it does not trigger that error either 3. org 9.7.37
On Wed, 19 Nov 2025, at 12:55, Christian Moe wrote: > "Racoon Chimp" <[email protected]> writes: > >> oh, thank you. that's it. >> >> first there was headline and NOT heading. >> >> second, as in your case, it had zero effect. so i thought, maybe it >> gets evaluated the other way around. changed it to: >> >> =(setq org-M-RET-may-split-line '((headline . nil)(default . t)))= >> >> and the magic does happen. >> >> problem solved! >> >> i still don't get it, but it does work as intended. > > Good! But very different from what I'm seeing. For me > - your original expression triggered no error > - the corrected expression works, regardless of order > Not really planning to look into it, but I wonder what Org version > you're using. I'm on 9.8-pre (release_9.7.30-367-ge8413b). > > Also, would you mind replying on-list (with reply-all) just so the > thread will reflect that the matter is closed? > > Yours, > Christian
