emacs-workspaces/kill-buffers-close-workspace is looping infinitely about tabspaces HOT 9 CLOSED

Unfortunately, I haven't. I will have to come back to this problem some other time, as I spent far too long trying to debug it, and I have a temporary work-around for now. I'll post any progress I discover here as I do, if nobody else encounters it/solves it in the meantime.

from tabspaces.

Yeah that won't help here. It never escapes the loop at all by error or otherwise, for the cleanup function to be applied, and I also tried dolist.

from tabspaces.

I just tried emacs -Q and requiring just emacs-workspaces and project, I cannot reproduce the problem, so perhaps this is not this package's problem. I'll have to dig deeper and see which package is to blame and figure out the appropriate patch some other time. I'm also not sure if this issue should be closed yet, as it's very unclear to me what is affecting this. I'll have to bisect my configuration and see what I can figure out when I have time.

from tabspaces.

Sorry no, I was never able to figure out what the problem was. Since I can't reproduce with emacs -Q I would say this isn't this package's fault, but just an incompatibility between some other package due to the global nature of Emacs. For that reason, I will close this issue now. Thanks for your work!

from tabspaces.

Interesting. I haven't seen this problem myself and I use this function all the time. Have you checked whether this happens in a bare config (i.e. with emacs -Q)?

from tabspaces.

I just pushed a small change that might help. Or it might be due to something else in your config. In any case I'll leave the issue open for awhile.

from tabspaces.

I do have a theory though. There might be shared structure with the original buffer list in emacs-workspaces--buffer-list-all, such that when a new buffer is created, the changes get picked up in the cons cells this function returns. A copy of that tree might do as a work-around.

Edit: Come to think of it, that is the only thing that makes sense as to what is happening. I can't see any reason the loop would continue forever if there wasn't any shared structure.

from tabspaces.

Sounds good -- especially since I'm unable to reproduce the problem so far!

from tabspaces.

Any updates @mfiano ?

from tabspaces.