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
Subject: bug#37840: Missing in the Emacs manuals:
Date: Wed, 30 Oct 2019 21:37:07 +0100	[thread overview]
Message-ID: <554177EF-4600-4F68-89F1-3AF67A551F65@univie.ac.at> (raw)
In-Reply-To: <fb3a0b18-6057-ba5b-cdca-5299142270fc@gmx.at>

Thanks for your response. I have another question, on the following customization:


(setq display-buffer-base-action
       (quote (
  (display-buffer-reuse-window display-buffer-pop-up-frame)
  (reusable-frames . t)
 )))

(setq display-buffer-alist
       (quote (
      ("\\*[^s][^s]" (display-buffer-reuse-window display-buffer-pop-up-frame)
       (pop-up-frame-parameters
        (width . 92)
        (height . 48)
        (left . 1150)
        (unsplittable)
        (tool-bar-lines . 0)
        (left-fringe . 0)
        (right-fringe . 0)
        (line-spacing . 0)
        (font . "Monaco-12")
        (top . 180)
      ))
)))

Suppose I have buffer A open in frame A. Issuing occur->some word, the occur buffer pops up in its own frame, say frame B, as intended with the above customization. Moreover, frame B has input focus. Returning to frame A, without closing frame B, and issuing another time occur-> some word, frame B now shows the new occur buffer, as intended, but this time frame B lacks input focus. What goes wrong the second time?

Let me mention that if, in window.el, I add 

(x-focus-frame (window-frame window))

at the very end of the defun "display-buffer-reuse-window", the problem goes away, i.e., in the above example, frame B gets input focus after every invocation of occur in frame A. How can I get this with a suitable customization on the "display-buffer-alist" level?

Thanks

Konrad






 

> Am 30.10.2019 um 09:14 schrieb martin rudalics <rudalics@gmx.at>:
> 
> > The entry (dedicated . t) did the job. (BTW, where is this possibility documented?)
> 
> In section 28.15 Dedicated Windows of the Elisp manual.  But as I said
> in my first answer in this thread, indiscriminately applying a non-nil
> 'dedicated' entry is not generally advisable since it might affect
> windows that pop up on the same frame too, with the consequence that
> you can no longer switch buffers in such windows.  And it won't handle
> the case where the buffer is shown in the selected window either.
> 
> As explained in section 28.16 Quitting Windows of the Elisp manual,
> 'quit-restore-window' could automatically DTRT for windows like that
> used for composing mail, so there would be no need for a 'dedicated'
> entry.  But 'message-send-and-exit' calls 'message-bury' and that uses
> a slightly weird strategy to possibly get rid of the window with the
> consequence that 'quit-restore-window' won't even get called here.
> 
> A zache Gschicht, so to say.
> 
> martin






  reply	other threads:[~2019-10-30 20:37 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 [this message]
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
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=554177EF-4600-4F68-89F1-3AF67A551F65@univie.ac.at \
    --to=konrad.podczeck@univie.ac.at \
    --cc=37840@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).