To conform the module to Doom's naming and style conventions.
This introduces two breaking changes:
+ doom-bepo-cr-rotation-style was renamed +layout-bepo-cr-rotation-style
+ Replaces the doom-bepo- prefix for this module's bepo library with
+layout-bepo-
And the following fixes:
+ Corrects the file path in file header comments.
+ input/layout/autoload/bepo.el is no longer compiled/indexed if +bepo
isn't activated.
This hack was PRed 4+ years ago. The package has since been improved and
the original issue it tackled is very likely long gone (and is now
causing wrong-number-of-arguments errors).
Fixeskidd/org-gcal.el#151
gf (+lookup/file) has been changed to:
+ Use the active selection instead of the filename-at-point when
searching for a file (as requested in #4942).
+ Pre-fill the FFAP prompt with the thing at point if no obvious
filepath can be guessed from it (via ffap-alist).
+ Offer to search the current project for the thing-at-point (if
counsel-file-jump is available).
+ Fall back to a standard ffap prompt if all else fails.
I've also reversed te order of file lookup backends so that our FFAP
backend is treated as a never-failing last resort (also because the
bug-reference backend is known to fail gracefully, so we can trust it to
run first).
Closes#4942
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.
With current hacks involving `org-agenda-files`, one cannot use org agenda
commands like clock in or change the entry's state to done, etc.
Specifically, the mangled behavior observed at #4901. This commit fixes those
problems around `org-agenda` buffer specific commands.
For more details, please refer to https://github.com/hlissner/doom-emacs/issues/4759#issuecomment-822100632.
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.
This could potentially cause stuttering for long lived sessions where
the user takes few breaks, but could yield great performance benefits in
the shorter term. We'll have to experiment.
I was conservative before. I didn't want to change this globally in case
it had a negative performance impact on shy servers that don't talk
much, but this turned out to be too paranoid. Untalkative servers are
barely, if at all, affected, and chatty ones perform better across the
board.
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.
