Request: add docs links to doom doctor

Development
#1

Currently this is what the doom doctor looks like on my machine:

> doom doctor
The doctor will see you now...

> Checking your Emacs version...
> Checking for Doom's prerequisites...
> Checking for Emacs config conflicts...
> Checking for missing Emacs features...
> Checking for private config conflicts...
> Checking for common environmental issues...
  ! Detected Fish as your $SHELL
    Fish (and possibly other non-POSIX shells) is known to inject garbage
    output into some of the child processes that Emacs spawns. Many Emacs
    packages/utilities will choke on this output, causing unpredictable
    issues. To get around this, either:

      - Add the following to $DOOMDIR/config.el:

        (setq shell-file-name (executable-find "bash"))

      - Or change your default shell to a POSIX shell (like bash or zsh)
        and explicitly configure your terminal apps to use the shell you
        want.

    If you opt for option 1 and use one of Emacs' terminal emulators, you
    will also need to configure them to use Fish, e.g.

      (setq-default vterm-shell (executable-find "fish"))

      (setq-default explicit-shell-file-name (executable-find "fish"))

> Checking for stale elc files...
> Checking for problematic git global settings...
> Checking Doom Emacs...
  āœ“ Initialized Doom Emacs 3.0.0-pre
  āœ“ Detected 46 modules
  āœ“ Detected 194 packages
  > Checking Doom core for irregularities...
    Found Symbols Nerd Font Mono
  > Checking for stale elc files in your DOOMDIR...
  > Checking your enabled modules...
    > :lang markdown
      ! Couldn't find a markdown compiler, `markdown-preview' won't work

To resolve the :lang markdown issue it would be really helpful if the output included a link to the docs. Iā€™m picturing something like:

    > :lang markdown (https://github.com/doomemacs/doomemacs/tree/master/modules/lang/markdown)
      ! Couldn't find a markdown compiler, `markdown-preview' won't work

That way I could more easily visit the docs for the module and find the list of supported markdown compilers so I can resolve the warning.

Since users can also create custom modules maybe each module has to opt-in to this with a doc-link-type setting.


Loading data dump...