From: martin rudalics <rudalics@gmx.at>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 37840@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#37840: Missing in the Emacs manuals:
Date: Mon, 2 Dec 2019 10:41:20 +0100 [thread overview]
Message-ID: <86d50719-d506-9bfa-5ffc-9420fa356ebb@gmx.at> (raw)
In-Reply-To: <95A8B31B-1FC5-4A28-A666-EBEE3791F206@univie.ac.at>
> Suppose I have two buffers open, say fooA.tex and fooB.tex, each in
> its own frame. Then I invoke Ediff to compare both buffers. Now
> suppose I kill the buffers fooA.tex and fooB.tex _before_
... but here already something must happen in any windows resp. frames
showing these buffers ...
> I quit the
> Ediff control panel. If I then quit the Ediff control buffer, it
> happens that some of the auxiliary Ediff buffers pops up, but _not_
> in the geometry customized with display-buffer-alist for *something*
> type buffers, but with a geometry according to default-frame-list
> modulo that the position is that of one of the former frames for
> fooA.tex or fooB.tex, depending on which was buffer A in Ediff's
> terminology. Thus, I can get a total frame layout which should not
> exist according to the customizations according to
> default-frame-alist and display-buffer-alist.
Note again that ediff doesn't care neither about ‘default-frame-alist’
nor 'display-buffer-alist'. It uses its own customary settings and
sometimes relies on 'switch-to-buffer' to DTRT. In addition, ediff
doesn't like it much when you kill one of its buffers too early, that
is before calling 'ediff-quit'.
You have two ways to interfere here: 'ediff-cleanup-hook' to clean up
the state _before_ 'ediff-quit' starts its own cleanup routine (so you
can, for example, delete frames showing buffers used by ediff) or
‘ediff-quit-hook’ which by default runs ediff's own cleanup function
'ediff-cleanup-mess' (where you will see a plethora of 'delete-window'
and 'switch-to-buffer' calls that probably cause the behavior you see
and dislike above). If you want to change or add to the latter, it's
probably best to run 'ediff-cleanup-mess' through the debugger first
in order to understand how it works and how it messes up your
buffer/frame relationships.
> How can I sole this? Or, even better, how can I manage that in the
> above scenario no buffer pops up if I close the Ediff control panel?
> Has the problem maybe something to do with the fact that the frame
> of the Ediff control panel has no minibuffer?
You cannot give a minibuffer window to a frame that has none. So by
all means, 'ediff-quit' should avoid reusing the control panel frame
for showing another buffer. Does it do that in your case?
martin
next prev parent reply other threads:[~2019-12-02 9:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 0:39 bug#37840: Missing in the Emacs manuals: Konrad Podczeck
2019-10-22 8:43 ` martin rudalics
2019-10-23 7:25 ` Konrad Podczeck
2019-10-23 7:46 ` martin rudalics
2019-10-28 17:37 ` Konrad Podczeck
2019-10-28 18:13 ` martin rudalics
2019-10-28 19:04 ` Konrad Podczeck
2019-10-29 9:28 ` martin rudalics
2019-10-30 0:56 ` Konrad Podczeck
2019-10-30 8:14 ` martin rudalics
2019-10-30 20:37 ` Konrad Podczeck
2019-10-31 7:59 ` martin rudalics
2019-11-02 21:47 ` Konrad Podczeck
2019-11-04 9:06 ` martin rudalics
2019-11-04 11:20 ` Konrad Podczeck
2019-11-04 18:27 ` martin rudalics
[not found] ` <A8BBF7A4-BFE0-44BB-BCB3-B26477FFC946@univie.ac.at>
2019-11-04 19:10 ` martin rudalics
2019-11-06 22:41 ` Juri Linkov
2019-11-07 8:39 ` martin rudalics
2019-11-07 21:58 ` Juri Linkov
2019-11-08 9:20 ` martin rudalics
2019-11-08 11:04 ` Konrad Podczeck
2019-11-08 18:27 ` martin rudalics
2019-11-08 21:12 ` Konrad Podczeck
2019-11-09 9:01 ` martin rudalics
2019-11-10 16:44 ` Konrad Podczeck
2019-11-10 18:33 ` martin rudalics
2019-11-14 10:03 ` Eli Zaretskii
2019-11-14 18:18 ` martin rudalics
2019-11-14 18:35 ` Eli Zaretskii
2019-11-15 8:50 ` martin rudalics
2019-11-22 13:09 ` Konrad Podczeck
2019-11-22 17:49 ` martin rudalics
2019-11-22 19:22 ` Eli Zaretskii
2019-11-23 1:42 ` Konrad Podczeck
2019-11-23 8:16 ` martin rudalics
2019-11-25 23:47 ` Konrad Podczeck
2019-11-26 9:32 ` martin rudalics
2019-12-02 1:35 ` Konrad Podczeck
2019-12-02 9:41 ` martin rudalics [this message]
2019-11-23 8:15 ` martin rudalics
2019-11-23 9:49 ` Eli Zaretskii
2019-11-26 9:31 ` martin rudalics
2019-11-26 9:42 ` martin rudalics
2020-09-20 11:12 ` Lars Ingebrigtsen
2019-11-10 20:11 ` Juri Linkov
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=86d50719-d506-9bfa-5ffc-9420fa356ebb@gmx.at \
--to=rudalics@gmx.at \
--cc=37840@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=konrad.podczeck@univie.ac.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).