search

Malabarba / elisp-bug-hunter

Hunt down errors in elisp files.
271 stars 15 forks source link

Re bug-hunter-init-file, emacs -q -l is not exactly identical to emacs #23

Open thblt opened 6 years ago

thblt commented 6 years ago

I'm facing a bug which happens only if the configuration is loaded the regular way, but not with emacs -q -l ~/.emacs.d/init.el. The details are not really important, but this specific property makes bug-hunter-init-file unusable, since even loading the full file with -q -l init.el doesn't trigger the bug.

The following screenshot shows the difference between the two invocations. Left is emacs -q -l ~/.emacs.d/init.el temp/test.org, right is emacs temp/test.org.

2018-06-23-191002_3840x2160_scrot

I'm not sure yet what the root cause is, but I suspect elisp-bug-hunter would be closer from "regular" emacs invocation if it did offer the option to override $HOME instead of using -q -l

thanks!

Malabarba commented 6 years ago

I'm not sure yet what the root cause is, but I suspect elisp-bug-hunter would be closer from "regular" emacs invocation if it did offer the option to override $HOME instead of using -q -l

Yes, I think you're right. But I think it would probably be harder to make it cross-plaform. Ultimately, bug-hunter is never going to be able to catch every single corner case. It's primarily designed as an aid for newer users with the most common issues.