I'm currently experiencing problems getting the source code highlighting to work with https://github.com/markedjs/marked
The reason is that Marked outputs the following structure:
```html
<pre><code class="language-js">const hello = 'world';</code></pre>
```
and the current selector expects the `pre` tag to have a `lang` attribute.
This PR splits the forwarding of the `lang` attribute to a class and the code that initialise the highlighting for each block. It will try to initialise the highlighting for every `code` block that is inside a `pre` tag.
And move former 'SPC s m' (evil-show-marks) to 'SPC s r', since it is
slightly less useful do to evil having native keys for jumping to marks:
` ' and :marks
It makes more sense to store this file where you keep your org files,
rather than in Doom's .local files, which could be deleted for
debugging, or local only to a specific machine.
Also make ID links relative to org-directory, in case you use the same
org library on a different system with different filesystem
layout/system of symlinks.
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)
