"J.D. Smith" <[email protected]> writes: >> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil) >> <=(nil 165 nil) > > Thanks. Reproduced, and fixed in latest. This is an edge case: > `org-element' see that final `*bold*]]` as a nested entity, but org's > font-lock disagrees. It does not have its markers hidden, so > `org-inside` should not treat it as a nested entity. Add a space after > `*bold*` to see the normal behavior.
I see the fix. Another edge case: In * =[[test][foo *bar*| and]] (| is cursor) type = > I think this is an org font-lock bug, or at least an unfortunate > disagreement between `org-element` and org's font lock engine as to what > `*bold*]` actually is. Sure. Org font-lock is full of bugs, alas. > BTW, not related to `org-inside', but I've long thought when you are > typing, e.g. > > *this is a|* > > then back up to the point (`|') and edit it to read > > *this is a long bold phrase* > > org's font lock should /not/ flash face and marker hiding off and on > rapidly as you type. Perhaps a similar trick could be used as for > comments in many modes. Comment fontification "holds off" on > re-fontifying syntactically for a time (reset ever time you type > something), to give you a chance to close the comment before it messes > with the rest of the buffer. Stefan could probably help with that. Yeah. I am not aware about a way to achieve what you describe. P.S. I have second thoughts about the face. Underline is also good, and may be more subtle when editing frequently. Ugh! This is hard. We need a poll and multiple inputs from users. Probably, we can install the branch first and then ask people to test and tell what they prefer. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
