It's hardcoded to return t for symbols that end in any of '-command',
'-frame-alist', '-function', '-functions', '-hook', '-hooks', '-form',
'-forms', '-map', '-map-alist', '-mode-alist', '-program', or
'-predicate' -- which I think is excessive next to a safety check.
I'll trust that: if the user marks X as safe, and it isn't *explicitly*
marked risky, and it destroys the universe, then it's their fault, not
mine, not Emacs'.
Pass the "noraise" flag to okular if it is used as a Latex viewer. If an
okular instance is already displaying the Latex compilation result,
subsequent invocations won't make okular steal focus from Emacs.
Gives the user the option to hide the top-level heading when presenting,
and defaults it to nil, since that is org-tree-slide-mode's default
behavior.
Also reduces the default text-scale for org-tree-slide-mode from 6 -> 5.
Fixes#2182Closes#4907
The Skim.app `displayline` command takes the flag `-g` which is "Do not bring Skim to the foreground"
when viewing the pdf results of the latex build, bringing skim to the foreground saves an `Alt+Tab` to open the app that I was intending to lauch by the auctex View command.
When opening an org file and the point is placed in a folded region (by
saveplace), it reveals the current subtree. Instead, it will reveal the
current subtree *and* its ancestors (and their siblings), which is more
intuitive.
I've noticed that some docs are a bit outdated, as homebrew doesn't have
`brew cask` command now, all features regarding to casks were moved to
the option `--cask` instead.
This commit just introduce such changes to be up-to-date with homebrew instructions.
Some keys were bound to no-longer-existing commands, or commands which changed
name.
Others only made sense in the REPL, or /also/ in the REPL, so the keybinds are
now in `scheme-mode-map', `geiser-repl-mode-map', or both accordingly.
Due to case shenanigans, ob-C.el's feature name is ob-C, not ob-c,
preventing folks from using 'c' (lowercase) as a language name for org
babel blocks.
emacs-geiser/geiser@aa26163 -> emacs-geiser/geiser@c5a9aae
With emacs-geiser/geiser@c5a9aae, geiser-impl--add-to-alist is now
autoloaded. This fixes#4863 by preventing void-function errors at
startup or 'doom sync'-time.
But this presents a new problem: geiser-impl is guaranteed to be
needlessly loaded at startup, the first time geiser-impl--add-to-list is
called among, say, geiser-chez's package autoloads. To get around this I
forcibly redefine it as an inline-able function (with defsubst) and
shove this new definition into Doom's autoloads file (where it will
appear before package autoloads).
Since Doom byte-compiles its autoloads file (containing concatenated
autoloads from all doom modules and packages), geiser-impl--add-to-alist
calls (and geiser-activate-implementation calls too, which is already
inline-able) will be inlined, fixing the issue.
Fixes#4863
+ Adds electric alignment of amounts on RET
+ Fixes all of beancount's config (which was running because the package
is called beancount, not beancount-mode)
+ Fixes flood of "invalid face org-level-N" warnings
+ Fixes beancount-electric-currency for appending currency to unlabelled
amounts. Also enables this to fall back to first operating_currency in
document, in available
+ Binds TAB to beancount-outline-cycle on outline heading, otherwise
indent-according-to-mode. No need for completion popup when company
already provides this.
This fixes a class of issues where doom-first-file-hook would fire even
for files not opened interactively (e.g. via org-agenda reading agenda
files or helpful scraping definitions from source files).
In instances like these, hooks like find-file-hook or pre-command-hook
are set to nil to speed up this process and reduce noise, but many
packages add to these hooks when they are loaded; these are lost when
their lexical values fall out of scope, leading to odd errors (like the
one in #4759).
Fixes#4759 (again)
First brought up in hlissner/doom-emacs@9f08db8
