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: Fri, 22 Nov 2019 14:09:58 +0100 [thread overview]
Message-ID: <70BE5DCC-07C6-4A0D-9A5C-1700BBCB1DC5@univie.ac.at> (raw)
In-Reply-To: <7e6f19a1-fa45-0315-9d22-9bbb7223d695@gmx.at>
>
> The other approach is to specify in that function all buffers that
> interest you (mostly based on the extension of the file they visit)
> instead of _every_ buffer. Would that be so difficult?
>
>
> The other approach is to specify in that function all buffers that
> interest you (mostly based on the extension of the file they visit)
> instead of _every_ buffer. Would that be so difficult?
>
I followed this advice, and the new display-buffer customization mechanism works indeed great. However, the following problem arises. Suppose I have the customization
(customize-set-variable 'display-buffer-base-action
'((display-buffer-reuse-window display-buffer-pop-up-frame)
(reusable-frames . t)))
(customize-set-variable 'display-buffer-alist
'(("\\`\\*[^s][^s].*\\*\\'"
(display-buffer-reuse-window display-buffer-pop-up-frame)
(dedicated . t)
(pop-up-frame-parameters
(width . 83)
(height . 42)
(left . 778)
(unsplittable)
(tool-bar-lines . 0)
(left-fringe . 0)
(right-fringe . 0)
(line-spacing . 0)
(font . "Monaco-12")
(top . 110)
))
("[.]"
(display-buffer-reuse-window display-buffer-pop-up-frame)
(pop-up-frame-parameters
(tool-bar-lines . 1)
(left . 1)
(left-fringe . 2)
(top . 0)
(height . 46)
(width . 80)
(font . "SF MONO-15")
(line-spacing . 3)
))))
With this, start Emacs, open a file, foo.tex say, and in the mini-buffer of the frame displaying foo.tex do occur->some text, so that the occur-buffer displays in its own frame. Now, in the mini-buffer of the frame with foo.tex do bury-buffer. Then also this frame displays the occur-buffer, so that I end up with two frames displaying the same occur-buffer. How to solve this problem?
Konrad
next prev parent reply other threads:[~2019-11-22 13:09 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 [this message]
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
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=70BE5DCC-07C6-4A0D-9A5C-1700BBCB1DC5@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).