unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 37840@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#37840: Missing in the Emacs manuals:
Date: Mon, 2 Dec 2019 02:35:56 +0100	[thread overview]
Message-ID: <95A8B31B-1FC5-4A28-A666-EBEE3791F206@univie.ac.at> (raw)
In-Reply-To: <d6fe9a85-9194-9341-3365-2094806b3df4@gmx.at>

Hi,

I cannot solve the following problem with Ediff:


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_ 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. 

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?

Thanks,

Konrad



> Am 26.11.2019 um 10:32 schrieb martin rudalics <rudalics@gmx.at>:
> 
> > I just noted that the ediff-control-panel does not react on any of
> > the display-buffer-alist possibilities to customize appearance of
> > frames.
> 
> Customize 'ediff-control-frame-position-function'.  You can stuff
> anything you want into the return value of that function, not just the
> location.  Consult 'ediff-control-frame-parameters' in ediff-wind.el
> for how ediff sets things up if you do not interfere.
> 
> And be aware that Emacs has many other frame creating packages that
> disregard 'display-buffer-alist'.
> 
> martin






  reply	other threads:[~2019-12-02  1:35 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 [this message]
2019-12-02  9:41                                                                       ` martin rudalics
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=95A8B31B-1FC5-4A28-A666-EBEE3791F206@univie.ac.at \
    --to=konrad.podczeck@univie.ac.at \
    --cc=37840@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --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).