<commit_before>;;; .emacs --- summary -*- lexical-binding: t -*-

;;; Commentary:
;;  This is the standard Emacs configuration file.  It uses the Emacs Lisp
;;  dialect of the Lisp programming language for its specification.  Note that
;;  the majority of the configuration is in ~/.emacs.d/my-init.org, since ORG
;;  markup is far better for layout and organization than standard Elisp.  This
;;  file loads that ORG file at the very end, once it completes all setup
;;  operations.

;;; Code:

;; Tip from Doom Emacs:
;; Set these variables here to speed up our initial load.
;; They will be reset later on to further optimize our experience.
(defvar last-file-name-handler-alist file-name-handler-alist
  "Name of the `file-name-handler-alist' that was set to nil during startup.")
(setq gc-cons-threshold most-positive-fixnum
  gc-cons-percentage 0.6
  file-name-handler-alist nil)

;; JIT settings to speed up startup.
;; https://tychoish.com/post/towards-faster-emacs-start-times/
(setq jit-lock-stealth-time nil)
(setq jit-lock-defer-time nil)
(setq jit-lock-defer-time 0.05)
(setq jit-lock-stealth-load 200)

;;; NOTE REGARDING BYTE COMPILING CONFIG FILES:
;; In general, I have observed that attempting to load compiled Elisp files is
;; much, much slower than simply interpreting their corresponding .el files at
;; run time. I don't know why this is, but I have a guess. I am making prolific
;; use of the 'use-package' and 'straight' macros, and historically macros have
;; not played well with compiled Lisp code. Whatever the case may be, just bear
;; in mind that seeking a performance improvement from compiled files is likely
;; a fool's errand.
;;
;; In addition, the process of compiling all of these macro-heavy Elisp files is
;; extremely difficult to get right. Many things are left up to chance, and
;; things we often take for granted in the Elisp world cease to function<commit_msg>Deactivated JIT font lock stuff in emacs<commit_after>;;; .emacs --- summary -*- lexical-binding: t -*-

;;; Commentary:
;;  This is the standard Emacs configuration file.  It uses the Emacs Lisp
;;  dialect of the Lisp programming language for its specification.  Note that
;;  the majority of the configuration is in ~/.emacs.d/my-init.org, since ORG
;;  markup is far better for layout and organization than standard Elisp.  This
;;  file loads that ORG file at the very end, once it completes all setup
;;  operations.

;;; Code:

;; Tip from Doom Emacs:
;; Set these variables here to speed up our initial load.
;; They will be reset later on to further optimize our experience.
(defvar last-file-name-handler-alist file-name-handler-alist
  "Name of the `file-name-handler-alist' that was set to nil during startup.")
(setq gc-cons-threshold most-positive-fixnum
  gc-cons-percentage 0.6
  file-name-handler-alist nil)

;; JIT settings to speed up startup.
;; https://tychoish.com/post/towards-faster-emacs-start-times/
;; (setq jit-lock-stealth-time nil)
;; (setq jit-lock-defer-time nil)
;; (setq jit-lock-defer-time 0.05)
;; (setq jit-lock-stealth-load 200)

;;; NOTE REGARDING BYTE COMPILING CONFIG FILES:
;; In general, I have observed that attempting to load compiled Elisp files is
;; much, much slower than simply interpreting their corresponding .el files at
;; run time. I don't know why this is, but I have a guess. I am making prolific
;; use of the 'use-package' and 'straight' macros, and historically macros have
;; not played well with compiled Lisp code. Whatever the case may be, just bear
;; in mind that seeking a performance improvement from compiled files is likely
;; a fool's errand.
;;
;; In addition, the process of compiling all of these macro-heavy Elisp files is
;; extremely difficult to get right. Many things are left up to chance, and
;; things we often take for granted in the Elisp world cease to function
{'fraction_non_alphanumeric': 0.09187645990137555, 'fraction_numerical': 0.004152608357124318, 'mean_word_length': 4.011703511053316, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1599005', 'n_tokens_mistral': 1159, 'n_tokens_neox': 1109, 'n_words': 521}