GNU bug report logs - #20538
24.4; Attempt to delete a surrogate minibuffer frame

Previous Next

Full log

Message #38 received at 20538 <at> debbugs.gnu.org (full text, mbox):

From: "Roland Winkler" <winkler <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 20538 <at> debbugs.gnu.org
Subject: Re: bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame
Date: Wed, 13 May 2015 10:11:10 -0500

On Wed May 13 2015 martin rudalics wrote:
>  > How do you use the undocumented function ediff-setup-windows-plain?
>  > (Could this usage be properly documented?)
> 
> It's an option (a customizable variable).  Do
> 
> M-: (require 'ediff) RET
> 
> C-h v RET ediff-window-setup-function RET

Thanks - so the option is ediff-window-setup-function.

I suggest to give the function ediff-setup-windows-plain a docstring
like

  Set up windows for Ediff in one frame.
  Useful as value for `ediff-window-setup-function'.

Then your previous email telling me only about the function
ediff-setup-windows-plain gives an ignorant user like myself already
all the info he needs.

>  > Perhaps the error message could be changed to something like
>  >
>  >    "Attempt to delete frame with a surrogate minibuffer for frame XYZ"

Is the problem with the above that frames do not have
selfexplanatory unique names?  Oh well, too bad.

> Maybe we should say in the documentation of `delete-frame' something
> like
> 
>    A frame may not be deleted if its minibuffer serves as surrogate
>    minibuffer for another frame.

Yes, thanks, that would be better than the current phrase.  If the
buzzword "surrogate" appears also in the corresponding section of
the elisp manual, I might have never started this thread.

Roland

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.