Re: pop-to-buffer and friends new behavior or bug?

[David Koppelman]

> Are you sure this happens?  I looked into this and it seems to me that
> deleting a frame created via C-x 5 2 could not be deleted by deleting
> the "last buffer".

I usually open a new frame with C-x 5 b or C-x 5 f, so maybe that's the
problem. I'll set the new frame-auto-delete to nil, but maybe it would
be a good idea to not have the kill buffer commands also kill frames,
except under very limited circumstances.

Thanks for adding the option, setting it to nil works.

martin rudalics <address@hidden> writes:

>> On a similar note, I find annoying the new behavior of deleting a frame
>> when its last buffer (whatever that means) is deleted, at least for
>> frames which I explicitly open.
>
> Are you sure this happens?  I looked into this and it seems to me that
> deleting a frame created via C-x 5 2 could not be deleted by deleting
> the "last buffer".
>
>> Is that intended? Perhaps there should
>> be some kind of option for this (more convenient than advicing
>> window-deletable-p).
>
> I have now installed an option called `frame-auto-delete'.  Please try
> whether it helps you to get rid of the advice.  (If you set this to t
> then you can now even delete frames created via C-x 5 2 ;-) )
>
> martin