Henrik Lissner

This is [a known issue with how counsel-rg interprets its program's error codes](https://github.com/abo-abo/swiper/issues/2339) -- or perhaps how ripgrep returns a fatal error code despite a partial result. A crude workaround...

@sfc-gh-mpilman Try this instead: ```elisp (after! counsel (setq counsel-rg-base-command "rg -M 240 --with-filename --no-heading --line-number --color never %s || true")) ```

> I've discovered that it can happen if one has a directory without read/execute rights As I've said [above](https://github.com/hlissner/doom-emacs/issues/3038#issuecomment-624165004), [this is a known issue with how counsel-rg interprets its program's...

Could you see if the following works for you? ```elisp (defadvice! +ivy--always-return-zero-exit-code-a (fn &rest args) :around #'counsel-rg (letf! (defun process-exit-status (_proc) (let ((code (funcall process-exit-status proc))) (if (= code 2)...

I suppose the problem here is that tangling "0 code blocks" is considered an error state (and perhaps erroneously assumed to be due to an invalid config.org, rather than an...

Please tell me about your system: 1. Operating System and version. 2. Installed version of Emacs (and how it was installed). 3. Where Doom was cloned. 4. Are you using...

A commonality in the reports I'm seeing is that they come from users who have installed Emacs (with native-comp) with Snap or Flatpak. Can either of you confirm?

> load-file-name is nil This isn't consistent with the errors reported. If `load-file-name` were `nil`, file-truename (or something inside it) should throw a type error, but OP reports void-variable (i.e....

@Qfl3x Does running `bin/doom` in debug mode produce a backtrace? I.e. ```sh DEBUG=1 doom sync ```

Thanks for the PR! I've converted this to a draft for now because it needs a lot of work to conform to our conventions, cut down on superfluous flags, and...