Instead of mapping major modes to file size thresholds, it maps file
regexps (like auto-mode-alist) since the major mode cannot be known
before set-auto-mode is called (in after-find-file).
We don't need to be so judicious about what files are included in the
MRU list. If you open a file, any file, it'll be considered a recently
opened file.
Guessing the indentation can be awfully slow because it scans the whole
buffer. This PR overrides the guessing mechanism to scan at most 10000
points.
Signed-off-by: Rudi Grinberg <me@rgrinberg.com>
Some ivy/helm commands allow you to preview buffers, which is not an
appropriate time to (invisibly) revert them. The message could be missed
and expensive machinary could be triggered (e.g. updating git-gutter),
which could appear slow. Best to defer reverting until the user has
deliberately landed on the target, and is more likely to notice a revert
notification in the minibuffer.
Suggested by @flatwhatson
It would trigger set-auto-mode whenever files are written to (e.g. when
persp-mode writes its workspace/session files, which have unsafe local
variables, so the user is inundated with prompts to accept them).
Now, doom-guess-mode-h will only work on files with shebang lines.
Fixes an issue where pdfs (in pdf-view-mode) weren't been converted
correctly because the file was declared large while it was being read in
fundamental-mode.
Fixes an issue where dtrt-indent and/or nav-flash would hang Emacs when
opening large files, and disables all mode hooks for large
files (without using fundamental-mode so you can at least get syntax
highlighting).
Describes why we try to compress undo-tree history data. I'm aware that
undo-tree-auto-save-history is disabled, but that may change in the near
future.
Increase `undo-limit`, `undo-strong-limit` and `undo-outer-limit` by a
factor of ten, which should prevent emacs from prematurely truncating
the undo history and corrupting the tree.
Restore `undo-tree-auto-save-history` which was disabled to avoid
exacerbating the undo history truncation.
Change the `undo-tree` recipe to grab the latest version from the
maintainer's repostiory instead of the outdated ELPA version.
Restore `undo-tree-enable-undo-in-region` which should be fixed in the
latest version of `undo-tree`.
