`C-x b` results in `Error in post-command-hook (ivy--queue-exihbit): (file-error ...)`
- Dominant language
- Emacs Lisp
- Stars
- 22.7k
- Forks
- 3.1k
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 4
Description
### I confirm that...
- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.
- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.
- [X] The issue can be reproduced on the **latest** available commit of Doom.
- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*
### Expected behavior
`C-x b` works and shows the list of buffers
### Current behavior
`C-x b` fails to list buffers, and shows the following error in the minibuffer:
```
[Error in post-command-hook (ivy--queue-exhibit): (file-error "Opening directory" "Not a directory" "/home/armael/.doom.d/init.el")]
```
where `/home/armael/.doom.d/init.el` is the file currently opened.
The `*Messages*` buffer does not seem to include a more detailed error message; I could not get a backtrace to show up either, even after enabling `doom-debug-mode`.
### Steps to reproduce
This bugs seems to only show up with a specific combination of packages. I tracked it down to the following:
1. Start with a fresh doom installation, with the default config
2. in `init.el`, enable `ivy` instead of `vertico`; disable `doom-dashboard`, and disable `(default +bindings +smartparens)`. As far as I can tell, all three changes are required for the bug to manifest.
3. open a file with emacs, for example `emacs ~/.doom.d/init.el`, then type `C-x b`.
### System Information
https://gist.github.com/Armael/6478254dce17d3272e5080e1ed913f12
Contributor guide
Assessment
This issue has not been assessed yet.