It'll be another week or two before our Discourse and new docs are
ready, and signing up for Discourse seems to be the end of the world for
some people, so I've replaced the discourse links with gists or links to
our old docs.
...Rather than current directory.
While +default/search-project-for-symbol-at-point should operate out of
the current project's root, +default/search-notes-for-symbol-at-point
must operate out of org-directory, and no where else, even if
org-directory is not a valid project. 411ed0c8f8 was written to fix
that, but it indirectly broke
'+default/search-project-for-symbol-at-point' (causing it to always
resolve to the current directory, rather than the current project's
root).
Amend: 411ed0c8f8Fix: #5831
setenv treats the TZ (and only TZ) envvar especially, so we have to too,
since I'm intentionally avoiding iteratively setenv'ing envvars to avoid
the unnecessary extra work it does.
Fix: #5760
This is a huge set of pedantic changes, none them affecting actual code.
Mostly, I tried to:
- use consistent names; e.g, use LaTeX wherever possible, not latex;
- fix broken symbol links;
- use capitalized comments with full stops.
Reduce cases where native-comp procedures were executed in
non-native-comp contexts (somehow).
Also:
- Adds a NATIVECOMP constant for statically detecting the feature.
- Remove native-comp-* -> comp-* aliases (Emacs HEAD has long since
moved on from these).
- Add 'no-native-compile: t' to autoloads file.
- Defer citar-org, since citar autoloads it.
- Add introducing PR to #+SINCE and use new calver scheme.
- Move <localleader> @ keybind to :lang org
Ref: #5810
Xref started many backwards incompatible changes in the name of
performance. The marker ring no longer exists as a variable.
+lookup--xref-show will silently fail every time.
Switches to using xref-after-jump-hook to test whether xref actually
jumped to a definition. The hook is part of the exposed interface and
should hopefully not change in the near future.
Fix: #5737
An incompatibility between forge and evil-collection-forge causes this
error when starting Forge:
Cannot insert ("N" "Forge" forge-dispatch) into magit-dispatch; o not
found
evil-digit motions were refactored in emacs-evil/evil#1519 (where
evil-digit-argument-evil-beginning-of-line was removed), which was
pulled in during 8645634608.
Fix: #5731
Ref: 8645634608
Ref: emacs-evil/evil#1519
It was `evil-show-registers' that we wanted, not
`evil-ex-registers' (which never existed in the first place). Folks who
did not have :completion ivy enabled (e.g. vertico and helm users) would
see 'commandp, evil-ex-registers' errors when pressing `SPC i r`. Folks
who had it enabled would transparently invoke `counsel-evil-registers'
instead (because it was remapped).
Fix: #5753
The message simply test for the "not-a-version-yet" patch number and
displays an explanation to prepare users for raised error frequency and
having a backup version of Emacs if they do not want to deal with
issues.
