- enable-lui-track-bar was deprecated for enable-lui-track.
- Neither function has buffer-local side-effects, so they shouldn't be
used with hooks.
Close: #7959
Co-authored-by: Thaodan <Thaodan@users.noreply.github.com>
- Remove redundant autoloads (already autoloaded by packages).
- Move lui configuration to lui use-package! block.
- Ensure consistent use of whitespace.
Prior to this, the user would need to know the precise load order of
circe and circe-color-nicks/circe-new-day-notifier to overwrite Doom's
defaults in an `after!` or `with-eval-after-load` block.
Also, `enable-circe-color-nicks` does not have buffer-local
side-effects, so shouldn't be hooked to `circe-channel-mode-hook`.
Close: #7959
Co-authored-by: Thaodan <Thaodan@users.noreply.github.com>
These variables don't add any value to the original variables whose
defaults they change, so they've been deprecated. Users should modify
the original variables themselves.
I'm not actually sure when this was fixed, but the bug report title
claims this was reported in 29.1, so I'll assume it was merged by 29.3.
Needs verifying.
The explanation could use some work, but this'll do for now. I'll
welcome PRs to expand it if I don't get to it first.
Ref: https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-08/msg00560.html
`treemacs-add-and-display-current-project-exclusively' seems to confuse
some people and please others when it is used in $HOME. To reduce
confusion, SPC o p will now resume from the last session if
default-directory isn't a valid project OR if it's $HOME. It will also
emit a warning informing them of that.
Fix: #7948
Amend: f9dfb7e92a
For evil users, TAB used to invoke `org-cycle` in insert mode, until
recent changes with the corfu module undid them, making them invoke only
completion.
Includes an advice to prevent the log buffer from being focused. This
way, the user can return to their work faster when in their play-debug
loop, as well as kill the game/Godot by killing the log buffer
remotely (with its process) with C-g/ESC.
Otherwise `+lookup/documentation` will fall through to the next handler
whether or not `gdscript-docs-browse-symbol-at-point` is successful.
Especially important if `gdscript-docs-use-eww` is nil.
`diff-hl-update-async` was enabled in f2696d7, causing a regression
where with-editor buffers wouldn't get cleaned up properly. This would
particularly affect Magit's COMMIT_EDITMSG buffers. To quote jds on
Discord:
It seems like after committing (with cc in the magit buffer), it
leaves COMMIT_EDITMSG around. The next time I try & commit, a single c
keypress immediately jumps to the old COMMIT_EDITMSG buffer, but it's
inactive - C-c C-c closes that buffer but makes no change to git.
I opt for advice instead of find-file or with-editor-mode hooks to
restore normal behavior should with-editor-mode be later disabled
without the death of its buffer (not relevant to magit, specifically,
but it might be to other consumers of with-editor, now or in the
future).
Ref: dgutov/diff-hl#213
Amend: f2696d7302
Monkey-patches counsel-rg to ignore non-zero exit codes. This may have
other side effects, but despite it still producing workable resutls, the
command will discard all its results if there are any errors while
scanning a directory.
Ref: abo-abo/swiper#2339
Fix: #3038
These advice were unnecessary when not only does diff-hl expose
variables to change them, but one of the overridden definitions is
identical to the function it's replacing.
Also includes some other minor refactors.
The NS build of Emacs (on MacOS) seems to struggle rendering our old
fringe bitmaps for diff-hl, leading to noticably slow-downs when
scrolling in buffers with diff-hl enabled. By pre-computing the pixel
height and width of the bitmap, rather than relying on passing `repeat`
to define-fringe-bitmap's ALIGN argument, this seems to spare it a chunk
of wasted cycles.
Ref: https://www.reddit.com/r/emacs/comments/1do1wgj/fringes_incredibly_slow_on_emacs_ns_with_macos/Fix: #7923
Enable `markdown-fontify-code-blocks-natively`, which was disabled in
f5570db due to performance issues, which I try to fix by suppressing
mode hooks on `markdown-fontify-code-block-natively`.
Amend: f5570db4c2Close: #7930
Co-authored-by: real-or-random <real-or-random@users.noreply.github.com>
