Slawomir Grochowski <[email protected]> writes: > This issue has bothered me for a long time. When I first started using > column view, I thought the strike-through text was caused by rendering > errors or display artifacts. > > COLUMNS property values may contain summary operators like '{+}'. > When multiple such operators are present, font lock can interpret the > text between plus signs as strike-through, for example: > > :PROPERTIES: > :COLUMNS: %A{+} %B{+} > :END:
Yet another example showcasing that our fontification is rather broken. > The attached patch prevents emphasis fontification in node property > values and adds a regression test. > + (let ((face (get-text-property (match-beginning 2) 'face))) > + (if (listp face) > + (memq 'org-property-value face) > + (eq 'org-property-value face))) > + (save-match-data (org-at-property-p)))) Any time your code depends on fontification, we are risking introducing bugs in the future. For example, if we change the fontification order, your code will no longer work. Or if we change face name. Sorry, but I do not think that it is the right approach to fix the problem. We may put a stopgap by querying org-element-at-point, but the ultimate solution for this and numerous other fontification-related bug reports is rewriting the whole fontification code to use parser. Superseded-by: https://orgmode.org/list/87ee7c9quk.fsf@localhost -- 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>
