Sylvain Benner

I've got this same error and symptoms using Emacs 27.0.50 with all packages up to date and last develop version of Spacemacs. If I open a magit buffer or a...

I'm currently debugging it, more info to come.

Seems that I have a `#` in the buffer list which ends up being passed as `nil` down the line to Helm: ``` (persp-buffer-list-restricted) option: 0 (persp-buffer-list-restricted) bl: (persp-mode.el *Help*...

I can see there is some code to handle the killed buffers case, investigating if this code still works. Maybe the `nil` comes from somewhere else.

Interesting, this docstring says: ``` (defun persp-kill-buffer-query-function () "This must be the last hook in the `kill-buffer-query-functions'. Otherwise if next function in the list returns nil -- the buffer will...

It seems that the `#` is the culprit. In the logs above the `buffer:` value corresponds to `buffer-name-sorted` variable in the function `persp-restrict-ido-buffers`. The following filter function seems to fix...

To be more clear. With the following filtering function (that does nothing): ``` (defun toto (buffer-or-name) nil) ``` We get the bug with the following output: ``` (persp-buffer-list-restricted) option: 0...

Yeah but the tricky part is that I was able to open some markdown files without the bug. Maybe the issue here led me to believe that markdown files would...

Can you try to call: ```emacs-lisp (require 'pyvenv) (pyvenv-activate DIRECTORY) ``` In your `dotspacemacs/user-config` directory.

I agree we should not revert the setting to load newer `.elc` files. We need to find the cause with this option enabled. I remark that there is almost no...