Use `ess-view-data` given the extensive support for multiple backends
like base, dplyr, DT, kable, etc. Also, it seems that `ess-R-data-view`
is in an unmaintained/stale state.
Fix: #6455
This way rebinding our keybinds for ess sub-packages will require a
simpler after! line. I.e.
(map! :after ess-help ...)
Instead of
(map! :after (ess ess-help) ...)
Ref: #6455
Yasnippet expanding snippets (on TAB) from another mode can cause
org-element warnings. Until this interop is resolved, best to not make
TAB too smart.
It still works in src blocks, however.
Fix: #8363
A regression introduced in bac90c0. The extra --eval isn't necessary in
bin/doomscript because it loads early-init.el (and thus, lisp/doom.el)
sooner than bin/doom does.
Fix: #8362
Amend: def4579a9f
BREAKING CHANGE: This removes eclim.el and meghanada.el support from the
Java module. Both of these projects are unmaintained and recommend the
user switch to lsp-java, which is already offered by the module's +lsp
flag.
Fix: #8360
As of recent commits of Emacs 31, elisp files missing a
"lexical-binding: t" cookie will emit this warning:
Warning (files): Missing ‘lexical-binding’ cookie in "path/to/elisp/file".
You can add one with ‘M-x elisp-enable-lexical-binding RET’.
See ‘(elisp)Selecting Lisp Dialect’ and ‘(elisp)Converting to Lexical Binding’
for more information.
You can look forward to many of these if you use any old and
unmaintained elisp packages, or if you have elisp shell scripts with
shebang lines (which make this warning unavoidable).
This commit silences these warnings because it's poorly implemented.
It's obnoxious to users and they aren't the ones that should be told
this. It ought to be emitted during byte-compilation or by linters (e.g.
`M-x checkdoc`) at the folks actually in a position to do something
about the warning (i.e. the developers).
Ref: https://lists.gnu.org/r/emacs-devel/2024-05/msg00283.html
Inhibit recentf-cleanup and projectile caching, and silence it's logging
on refresh-buffer. The former can potentially be slow and isn't
necessary on top of invalidating the cache, and the latter is noise.
This changes what buffer `+emacs-lisp-eval` evaluates elisp in (useful
for the :tool eval module's commands, like `+eval/buffer` and
`+eval/region`, or the Evil operators on gr/gR).
Creates a scratch buffer/org src block alternative to ielm.
When invoking `+emacs-lisp/open-repl`, if no working buffer is set in
the resulting ielm buffer, it will default to the selected buffer prior
to opening the repl.
Store a little less undo history, to improve general runtime performance
by reducing the number of idle markers in long-lived sessions,
particularly in shell emulation buffers.
Now `doom-debug-mode` manipulates `doom-log-level` if you activate it
with a prefix arg, setting it to 1 by default, reducing its verbosity
and cutting down on noise in the logs.
Provides more control over our auto-reverting feature, and changes its
behavior to only target non-remote buffers by default, because reverting
remote buffers could be tremendously slow.
This could be later improved to treat TRAMP buffers with local
methods (like sudo) as local buffers.
Fix: #8354
In function `+bidi--set-font`, the character set was incorrectly
hardcoded to `'hebrew` instead of using the provided character set `name`
parameter. This caused `+bidi-arabic-font` to have no effect when set.
Additionally, setting the scale throws an error:
```
string-match-p: Wrong type argument: stringp, DejaVu\ Sans
```
Converting the font family property to string fixed the issue.
Seems the naming convention of dirvish windows has changed at some
point, so the popup module's fallback rules were catching them, causing
each of Dirvish's side windows to be treated as implicit popups.
Fix: #8347
