From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 37840@debbugs.gnu.org, juri@linkov.net
Subject: bug#37840: Missing in the Emacs manuals:
Date: Tue, 26 Nov 2019 00:47:43 +0100 [thread overview]
Message-ID: <3F21846D-7840-4CC7-A5D2-9AA7B35E79CE@univie.ac.at> (raw)
In-Reply-To: <69ef8cf3-9a81-34e6-7685-c60db5421134@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.
Konrad
> Am 23.11.2019 um 09:16 schrieb martin rudalics <rudalics@gmx.at>:
>
> > The patch does not do the job. With the customization from my
> > previous mail, start Emacs, open, say, foo.tex, and then do
> > occur->some text. In the frame with the occur buffer, do bury
> > buffer, so that the frame with the occur-buffer becomes iconified,
> > so everything is good up to now. But then, doing bury buffer in the
> > frame displaying foo.tex, the message-buffer displays in that frame,
> > then doing again bury-buffer in that frame, the occur-buffer shows
> > up, again in the frame originally intended for foo.tex, that is in
> > the wrong frame, i.e., not as intended with the display-buffer-alist
> > customization.
>
> If you want to keep the occur-buffer in an iconified frame, you have
> to customize 'switch-to-buffer-skip-visible' to 0 or t in order to
> avoid switching to it automatically in another window. When I do that
> here, 'bury-buffer' switches between foo.tex, *scratch* and *Messages*
> only.
>
> > Would it not be better to adopt a more radical approach? Say that
> > there are two basic defaults between which a user can choose: one as
> > it is now, and a second one where there is a strict one-to-one
> > correspondence between buffers and frames (i.e., in the terminology
> > of Emacs, with no “windows” at all). Given the second basis default,
> > the user could then customize whether for some buffer-types he/she
> > wants to have them displayed in windows, or, depending on the
> > buffer-type, customize geometry, fonts etc. of frames.
>
> I suppose that by customizing 'switch-to-buffer-skip-visible' to t and
> using a 'display-buffer-alist' that always makes a new dedicated frame
> that becomes invisible when it gets buried, you can largely achieve
> that. The only problems should result from internal Emacs functions
> that by default try to reuse or split the selected window. I'm quite
> sure that nothing can be done in this regard anyway.
>
> martin
>
next prev parent reply other threads:[~2019-11-25 23:47 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 [this message]
2019-11-26 9:32 ` martin rudalics
2019-12-02 1:35 ` Konrad Podczeck
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=3F21846D-7840-4CC7-A5D2-9AA7B35E79CE@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).