summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/eieio-datadebug.el
diff options
context:
space:
mode:
authorPhil Sainty <psainty@orcon.net.nz>2021-01-10 14:29:32 +1300
committerPhil Sainty <psainty@orcon.net.nz>2021-08-03 23:20:06 +1200
commit9df60d52d50b86639a82f22d7c0a07a81c3ba817 (patch)
tree167cbcd82f84de23625efd299169af6cdc5a41d9 /lisp/emacs-lisp/eieio-datadebug.el
parent359a8e4eda047b7dcb7e64faff7f8eaacf5d937c (diff)
downloademacs-9df60d52d50b86639a82f22d7c0a07a81c3ba817.tar.gz
emacs-9df60d52d50b86639a82f22d7c0a07a81c3ba817.tar.bz2
emacs-9df60d52d50b86639a82f22d7c0a07a81c3ba817.zip
Increase `so-long-threshold' and `so-long-max-lines' defaults
* lisp/so-long.el (so-long-threshold, so-long-max-lines): Increase default values to reduce false-positives. * etc/NEWS: Describe changes. Lines shorter than 10,000 characters shouldn't generally be causing problems, so testing this explicitly will largely eliminate false-positives. We must also increase the maximum number of lines to check, because 'minified' code may still include newlines, and so there may be many lines shorter than the new threshold before we find a line which exceeds it. Previously we used a minimum-effort heuristic, testing a very small number of lines against a maximum length which, while not remotely long enough to cause problems, would nevertheless be uncommon in any normal file of programming code (and hence indicative that the file was likely to be minified code). Testing indicates that the performance penalty for the larger values should be negligible.
Diffstat (limited to 'lisp/emacs-lisp/eieio-datadebug.el')
0 files changed, 0 insertions, 0 deletions