unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 20538@debbugs.gnu.org
Subject: bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame
Date: Wed, 13 May 2015 10:11:10 -0500	[thread overview]
Message-ID: <27022.80056.898164.21843@gargle.gargle.HOWL> (raw)
In-Reply-To: <5552FDFB.8080500@gmx.at>

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





  reply	other threads:[~2015-05-13 15:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 19:35 bug#20538: 24.4; Attempt to delete a surrogate minibuffer frame Roland Winkler
2015-05-10  2:41 ` Eli Zaretskii
2015-05-10 12:30 ` martin rudalics
2015-05-10 19:46   ` Roland Winkler
2015-05-10 20:17     ` Drew Adams
2015-05-11  3:27     ` Stefan Monnier
2015-05-11 10:08     ` martin rudalics
2015-05-11 17:03       ` Roland Winkler
2015-05-12  9:36         ` martin rudalics
2015-05-12 19:42           ` Roland Winkler
2015-05-13  7:32             ` martin rudalics
2015-05-13 15:11               ` Roland Winkler [this message]
2015-05-14 10:13                 ` martin rudalics
2015-05-16 19:16                   ` Roland Winkler
2015-05-19  9:42                   ` martin rudalics
2015-05-19 16:12                     ` Roland Winkler
2015-05-20  9:50                       ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27022.80056.898164.21843@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=20538@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).