- Move Doom core elisp API demos out of docs/examples.org into lisp/demos.org.
- Recognize and search demos.org file in modules for additional
demos (including $DOOMDIR/demos.org).
- Refactor emacs-lisp module to use new elisp-demos-user-files variable
instead of an advice. This way, elisp-demo's commands (such as
`elisp-demos-find-demo` and `elisp-demos-add-demo`) will include
Doom's demos.
- Rename doom--empty-module-context to doom-module--empty-context.
- Nest doom-module-context symbol plist in its 'keys' property. (By
convention, Doom uses keywords as keys in most places. Let's be
consistent)
- Updates all uses of doom-module--context-field and
doom-module-context-get.
BREAKING CHANGE: This deprecates the IS-(MAC|WINDOWS|LINUX|BSD) family
of global constants in favor of a native `featurep` check:
IS-MAC -> (featurep :system 'macos)
IS-WINDOWS -> (featurep :system 'windows)
IS-LINUX -> (featurep :system 'linux)
IS-BSD -> (featurep :system 'bsd)
The constants will stick around until the v3 release so folks can still
use it -- and there are still some modules that use it, but I'll phase
those uses out gradually.
Fix: #7479
`org-link-set-parameters` accepts `:face` for a function returning a face
or a symbol naming a face. Use a lambda returning `org-priority` to
avoid it being called directly as a function.
And move setter out of condition (it will no-op if :tools lsp +eglot
isn't enabled). Plus, it should be configured even when +lsp isn't
enabled for :lang swift.
Amend: #7567Close: #7577
Co-authored-by: ncihnegn <ncihnegn@users.noreply.github.com>
This fixes a bug introduced in bb3431a (#7509). This shows up for
example in `org-capture`, which uses multiple org buffers and the
initial one (with name `*Capture*`) will be dead already by the time the
timer runs.
Amend: #7509
Current LaTeX module uses `TeX-command-run-all` for compilation, which
by default opens the compiled document in a viewer. This behavior causes
a loss of focus from the Emacs window. We address this by adding a
custom compilation function.
The `use-package!` declaration for lsp-sourcekit in `config.el` did not
match the `package!` declaration in `packages.el`: this resulted in
`lsp-sourcekit` being loaded but never installed. The removal of this
package also resulted in there no longer being a proper LSP client with
eglot--this has also been fixed.
The flycheck-plantuml is by default configured to always run plantuml
via "java". This only works with a downloaded plantuml. However, I would
prefer to have plantuml installed via my package manager (fedora/dnf).
A locally installed PlantUML executable is already detected by default
for normal use (export/preview), we can also use it for flycheck.
If plantuml is downloaded using plantuml-download-jar, this jar is still
used by default (see setq plantuml-exec-mode), so this should not affect
previous setups.
Sometimes, `org-reveal` is called in the wrong buffer which throws an
error. For example, `org-link-open-from-string` creates an temporary
org-mode buffer that gets killed very quickly which means that
`org-reveal` gets called in a different buffer. I have also had issues
with org-reveal getting called in the org-roam buffer, which is why this
commit also saves the buffer it was called in.
Co-authored-by: Leo Okawa Ericson <git@relevant-information.com>
When invoking `rustic-cargo-run` a buffer called `*cargo-run*` is
opened. This adds a rule such that this buffer opens in a popup window
that is the same as the popup windows for other rustic cargo commands.
Ref: #2623
Eager expansion of the flycheck-define-checker macro causes flycheck to
be unavoidably eager-loaded at startup, regardless of other deferral
techniques, slowing down startup considerably, as it pulls in a number
of associated packages/config with it.
To match +beancount/previous-transaction's docstring: this command
should jump to the start of the transaction/directive at point first,
before jumping to the previous one. Now it does so.
It should also return nil if it fails.
+beancount/next-transaction and +beancount/previous-transaction would
formerly skip timestampped directives, e.g.
2016-09-15 * "Foo" ""
Expenses:Y 779.00 DKK
Assets:X:Checkings
2016-11-16 balance Assets:X:Checkings 8,417.58 DKK
2016-12-13 * "Bar" ""
Assets:X:Checkings 2,100.00 DKK
Income:Z
The `balance` directive would be skipped over. This commit changes that
to include them. Perhaps the commands should be renamed to
+beancount/{next,previous}-entry to better reflect my intended purpose
for them?
