emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

bin/doom: move debugger config to core-cli

Browse source 
And remove unnecessary path expansion.
This commit is contained in:
Henrik Lissner 2020-08-25 05:07:24 -04:00
parent 93ac32d082
commit c0500df5fb
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
2 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

11
bin/doom
View file

@ -63,15 +63,6 @@
(load (expand-file-name "core/core.el" user-emacs-directory) nil t) (load (expand-file-name "core/core.el" user-emacs-directory) nil t)
(require 'core-cli) (require 'core-cli)
;; Use our own home-grown debugger to display and log errors + backtraces.
;; Control over its formatting is important, because Emacs produces
;; difficult-to-read debug information otherwise. By making its errors more
;; presentable (and storing them somewhere users can access them later) we go a
;; long way toward making it easier for users to write better bug reports.
(setq debugger #'doom-cli--debugger
debug-on-error t
debug-ignored-errors nil)
;; HACK Load `cl' and site files manually to prevent polluting logs and stdout ;; HACK Load `cl' and site files manually to prevent polluting logs and stdout
;; with deprecation and/or file load messages. ;; with deprecation and/or file load messages.
(quiet! (if EMACS27+ (require 'cl)) (quiet! (if EMACS27+ (require 'cl))
@ -93,7 +84,7 @@
(pred stringp) (pred stringp)
(pred keywordp)) (pred keywordp))
command) command)
(let ((script (doom-path (getenv "__DOOMPOST"))) (let ((script (getenv "__DOOMPOST"))
(coding-system-for-write 'utf-8-unix) (coding-system-for-write 'utf-8-unix)
(coding-system-for-read 'utf-8-unix)) (coding-system-for-read 'utf-8-unix))
(with-temp-file script (with-temp-file script

9
core/core-cli.el
View file

@ -548,6 +548,15 @@ best to run Doom out of ~/.emacs.d and ~/.doom.d."
(doom-log "Initializing Doom CLI") (doom-log "Initializing Doom CLI")
;; Use our own home-grown debugger to display and log errors + backtraces.
;; Control over its formatting is important, because Emacs produces
;; difficult-to-read debug information otherwise. By making its errors more
;; presentable (and storing them somewhere users can access them later) we go a
;; long way toward making it easier for users to write better bug reports.
(setq debugger #'doom-cli--debugger
debug-on-error t
debug-ignored-errors nil)
;; Clean slate for the next invocation ;; Clean slate for the next invocation
(delete-file doom-cli-log-file) (delete-file doom-cli-log-file)
(delete-file doom-cli-log-error-file) (delete-file doom-cli-log-error-file)