They were a tad too aggressive. Our C-ret keybinds are more than enough.
I've removed them from insert state maps, however, so that those
keybinds won't override new C-ret keybinds on non-evilified minor mode
keymaps (for evil users).
If no selection is active, there is no initial input.
If selection is active, use the selection.
Also remove helm-google package, as the helm functionality is provided
by the core helm package already (and actually works).
Changes:
- Move <help>da to <help>u & <help>du = lookup docs for an autodef
- Rebind <help>dC = goto private init file (and jump to doom! block)
- Add <help>u & <help>du = lookup docs on an autodef
- Add <help>dl = text search on all packages in load-path
- Add <help>dL = text search on all load el files
New <help>p prefix for package help commands:
- <help>dpc = jump to a config block for a package
- <help>dpd = goto private packages.el file
- <help>dph = open a package's homepage (its repo or on melpa)
- <help>dpp = lookup docs on a package (including Doom info; what
module(s) install package, where it is configured, etc)
- Adds more keys under `<localleader> a`
- Reconfigures org-download to use org-attach system
- Make org-id-track-globally = t a global default now (not just for
org-brain)
- Renamed +org-init-centralized-attachments-h to +org-init-attachments-h
- org-attach-store-link-p = t (stores a link to an attachment when it is
attached)
- org-attach-use-inheritance = t (inherit attachment properties from
parent nodes)
If ':tools (eval +overlay)' is enabled, eval commands display their
output in a floating overlay at EOL. If the output is longer than
+eval-popup-min-lines (5), it will display it in a popup window instead.
With this, it also will use a popup window if the output is longer than
the minibuffer can display in one line,
- Pressing gd on a module in your doom! block will now browse that
module's directory.
- Pressing K on a module will jump to that module's documentation, if any.
- Pressing K on a module flag will jump to that flag's description
within that module's documenation.
- This is now explained in init.example.el
Closes#2249
