bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#37840: Missing in the Emacs manuals:


From: Konrad Podczeck
Subject: bug#37840: Missing in the Emacs manuals:
Date: Fri, 22 Nov 2019 14:09:58 +0100

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






reply via email to

[Prev in Thread] Current Thread [Next in Thread]