You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rainbow-delimiters intentionally has no logic that determines what characters are delimiters, that's provided by the major mode in the form of a syntax table. If the major mode indicates that < and > are paired delimiters, even though that's not necessarily true, it's a bug in that major mode and affects all consumers of syntax table data, not just rainbow-delimiters.
An alternative solution to fix it within rainbow-delimiters would be #1, but getting that PR into a remotely usable form is… difficult.
More often than not, when I'm using rainbow mode in org-files, the symbols <, >, mess up my file font locking.
Is there a way to configure so that rainbow-mode does not try to match these, or ignore them?
The text was updated successfully, but these errors were encountered: