On Sat, Oct 12, 2019 at 12:59 PM João Távora <
address@hidden> wrote:
> Do you really prever jit-lock--antiblink-in-string-or-comment and
> jit-lock--antiblink-line-beginning-position?
In a clean emacs -Q we already have things like
minibuffer-history-case-insensitive-variables
jit-lock-after-change-extend-region-functions
lisp-el-font-lock-keywords-for-backtraces-1
lisp-el-font-lock-keywords-for-backtraces-2
display-buffer--action-function-custom-type
jka-compr-added-to-file-coding-system-alist
revert-buffer-insert-file-contents-function
w32-direct-print-region-use-command-dot-com
backup-by-copying-when-privileged-mismatch
window-adjust-process-window-size-function
electric-indent-functions-without-reindent
list-matching-lines-default-context-lines
lisp-el-font-lock-keywords-for-backtraces
syntax-propertize-extend-region-functions
jka-compr-compression-info-list--internal
which are longer.
I don't understand how this can be an argument.
Is not exceeding the length of the longest symbol
ever, i.e. playing to the 99% percentile, acceptable
criteria for readability? I don't think so, personally.
That said, I'm neither in love with the solution I came
up with nor will I kill myself over long symbol names :-)
Perhaps a plist `jit-lock--antiblink-info` can be a
compromise.