Doom treats the use of package.el and its API as user error unless
they've called `package-initialize' themselves (in which case, it is
assumed you know what you're doing and truly want to use package.el).
A version of describe-char that, when given a prefix arg, will prompt
the user to click where to execute the command (so you can read
text-properties/overlay information for otherwise unselectable text, in
the minibuffer or special UIs).
This functionality falls under the umbrella of "better defaults" rather
than essential defaults, and so belongs in :config default.
Whats more, the naming convention (+emacs-...) was intentional, because
this function (and the :config default module) will be moved to :doom
emacs in the near future.
This also indirectly fixes#8373.
Fix: #8373
In case the mode is activated before gcmh is loaded (as is the case with
session persistance libraries like desktop.el or
persp{ective,-mode}.el).
Close: #8372
BREAKING CHANGE: Anyone used to realgud will find it missing as of this
commit. It's been replaced with Dape (see
https://github.com/svaante/dape).
This change was made because realgud's implementation was archaic and
over-complicated, dap-mode requires lsp-mode (and has a lot of moving
parts and points of failure), and dape is straight-forward by
comparison; to set up and use. Note that dap-mode and dap-ui is now
deprecated and will be removed in the future, but still remains behind
the +lsp flag for backwards compatibility, at least until v3.
This also adds a '<leader> d' prefix for debugger commands (except for
vanilla users, who already have dape's prefix on 'C-x C-a')
Adapted from Janfel's snippet in Wilfred/helpful#250.
And bound to C-{o,i} and {<,>} for evil users, and C-c C-{b,f} and {l,r}
for vanilla users (mirroring the back/forward keybinds for help.el).
Ref: Wilfred/helpful#250
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
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
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.
