Closed Stebalien closed 7 years ago
OK, you can try the develop branch for now.
(see the persp-remove-buffers-from-nil-persp-behaviour
variable)
I will merge this to master in the end of the week(if I don't find any bugs).
Well, now it doesn't ask but... I can't kill the buffer at all!
Indeed, you can not kill a buffer that belongs to a perspective from another perspective. It needs to be fixed.)
I think I have fixed this 52b813a8a31c12fe0e5a5e5e2fd3e408b495887b
It never actually gets to persp--kill-buffer-query-function-foreign-check
as (persp-contain-buffer-p buffer persp)
returns t
(everything belongs to the nil
buffer). Unfortunately, this means foreign-check-passed gets set to
tand, further down,
(eq 'kill foreign-check-passed)is
nil`.
Yes, you are right. Thanks. I just committed a (possible:)) fix.
Thanks! It appears to work now.
(I'm leaving this open in case you prefer to keep issues open until fixed in master.)
I have changed the code a bit https://github.com/Bad-ptr/persp-mode.el/commit/c0249bd2201e361c55bbbab978a28dab288f6bd6 Hope this will not break it for you).
I haven't noticed any regressions.
Fixed in master, closing this.
How do I get persp-mode to stop interfering with kill-buffer. I've set
persp-kill-foreign-buffer-behavior
to'kill
but it's still asking: "Remove the ... buffer from all perspectives?". I'm guessing the problem is that the buffer isn't foreign.FYI, I'm using spacemacs if it makes a difference.
To reproduce, make two auto-persps, enter the first, open a buffer that automatically belongs to the second, and then kill it (never leaving the first perspective).