Rewrite vanilla sandbox & report-bug commands

- Renamed doom/open-vanilla-sandbox to doom/sandbox (because it's not
  just for vanilla testing anymore)
- Renamed doom/open-bug-report to doom/report-bug (for consistency with
  `report-emacs-bug`; makes it easier to discover)
- Add SPC h d b for doom/report-bug
- Add SPC h d s for doom/sandbox
This commit is contained in:
Henrik Lissner 2019-04-23 20:58:19 -04:00
parent fa7f7042b0
commit 40f6a2b6e3
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
3 changed files with 47 additions and 61 deletions

View file

@ -1,12 +1,12 @@
;; Welcome to the vanilla sandbox!
;; Welcome to the sandbox!
;;
;; This is a test bed for running Emacs Lisp in an instance of Emacs with varying
;; amounts of Doom loaded:
;; This is a test bed for running Emacs Lisp in another instance of Emacs that
;; has varying amounts of Doom loaded:
;;
;; a) vanilla Emacs (nothing loaded) \\[doom--run-vanilla-emacs]
;; b) vanilla Doom (only Doom core) \\[doom--run-vanilla-doom]
;; c) Doom + modules - your private config \\[doom--run-vanilla-doom+]
;; d) Doom (normal) \\[doom--run-full-doom]
;; - vanilla Emacs (nothing loaded) \[doom--run-vanilla-emacs]
;; - vanilla Doom (only Doom core) \[doom--run-vanilla-doom]
;; - Doom + modules - your private config \[doom--run-vanilla-doom+]
;; - Doom + modules + your private config \[doom--run-full-doom]
;;
;; This is done without sacrificing access to installed packages. Use the sandbox
;; to reproduce bugs and determine if Doom is to blame.