+ Default browse-at-remote-prefer-symbolic to nil because a permanent
URL is generally more desirable for developers sharing links.
+ 'SPC g y' and 'SPC o o' now support the prefix arg, which will negate
the default value of browse-at-remote-prefer-symbolic for that call.
An optimization that minimizes how much work is done when grabbing org
agenda files in the background prevented side-effects in
doom-first-file-hook. This had the indirect effect of preventing
save-place-mode from adding its hook to find-file-hook IF org-agenda was
the first thing you ran at startup.
* doc: add crystal README
* adding some punctuation
* adding the version tag
* removing tree/<hash> links and placeholder comments
* adding in the required metadata
According to the documentation of `evil-window-split` the variable
`evil-split-window-below` needs to be non-nil for the new window to be
created below; and for `evil-window-vsplit` it is the variable
`evil-vsplit-window-right` that needs to be non-nil for the window to be
created on the right.
flatwhatson/pdf-tools@eb6d406 -> vedang/pdf-tools@35e12b0
The original politza/pdf-tools is no longer maintained (?), and the PR
we were pullin from has been merged into a new, maintained fork at
vedang/pdf-tools.
Might address #4750
* Fix for missing overlay
Overlay might be nil before being used, so replicate what the package does
* Neater for for nav-flash issue
* Properly check for the value
This was an arbitrary default. It's easier to remove than to add
back (see #4746). I'd rather be faithful to treemacs' author's vision.
Closes#4746
Co-authored-by: daanturo <daanturo@users.noreply.github.com>
`git-commit-summary-max-length' should be a number, not a symbol.
`git-commit-major-mode' should be checked more carefully, as otherwise
exploits are possible (e.g. if it is `erase-buffer' or some more
dangerous function of the user's environment).
Some users may not be using a theme (*shudder*), in which case
ns-auto-titlebar-mode never kicks in.
That said, this "fix" didn't fix the targeted issue anyhow.
If triggered too early, it may read the wrong frame background mode and
you'll get dark text on a dark titlebar in MacOS dark mode (or light
text on a light titlebar in light mode).
Users (or packages) may add entries directly to prettify-symbols-alist.
The module would mistaken that as a green light to activate
prettify-symbols-mode. Instead, only activate the mode if this module's
ligatures (or extra symbols) are specifically asked for.
* Added emms dir to gitignore.
* Added emms module.
* Added emms module.
* Added emms module.
* I had a weird bug fixed it.
* I suck.
* Made the changer lissner requested.
* Made a restart music daemon func.
* Simplify config and bump package
* Proofread readme
Co-authored-by: Takoda J Horton <takodajhorton@protonmail.com>
Co-authored-by: Henrik Lissner <henrik@lissner.net>
The user can open the calendar directly, with `M-x
cfw:open-calendar-buffer`, which sidesteps the workspace init logic in
=calendar. This fixes +calendar/quit so it can deal with this use case.
Mentioned in #4019
If TAB was bound on the current keymap, our TAB dispatcher would fall
back on it, but it wouldn't see TAB keybinds on evil auxiliary keymaps
on the current keymaps (e.g. in cfw:calendar-mode).
* doc/adding editor config and hl-column-fill docs
* Adding inaugural versons to the modules
* Making the requested edits
* adding in some more spaces
* redoing the review
* ui/fill-column: correct & expand readme
Co-authored-by: Henrik Lissner <henrik@lissner.net>
