Re: Stop frames stealing eachothers' minibuffers!

[martin rudalics]

>> The problem that Miha highlighted is that when there is an open
>> minibuffer when that last frame is deleted, that open minibuffer remains
>> in existence, fouling up the next emacsclient session.
>>
>> Maybe such open minibuffers should just be aborted (along with any other
>> recursive edits) when the last frame gets deleted.  This would be
>> simpler to code than preserving those minibuffers somewhere, and
>> restoring them at the next emacsclient session.  Aborting them also
>> seems more natural, since their contents are unlikely to have any
>> relevance to the next emacsclient session.
>
> Martin, can you comment on this, please?

What about answering questions about unsaved buffers, running processes
...  in such a situation?  I never use emacsclient so I have no idea how
this should behave in practice.  But any non-crucial dialog should be
aborted IMHO.

martin