emacs-devel
[Top][All Lists]
Advanced

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

Re: Potential bug in the logic of rmail-select-summary


From: Eli Zaretskii
Subject: Re: Potential bug in the logic of rmail-select-summary
Date: Tue, 19 Jan 2021 20:33:11 +0200

> From: Göktuğ Kayaalp <self@gkayaalp.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 19 Jan 2021 20:14:17 +0300
> 
>  display-buffer-alist
>  '(("\\*Quail Completions" . (display-buffer-in-side-window))
>    ("\\*.*Completions\\*" . (display-buffer-in-side-window . ((side . 
> bottom))))
>    ("\\*Help\\*" . (display-buffer-reuse-window))
>    ("Checkdoc" . (display-buffer-pop-up-window))
>    ("Calendar" . (display-buffer-in-side-window . ((side . bottom))))
>    ("help\\[R\\]" . (display-buffer-pop-up-window))
>    (".*" . (display-buffer-same-window)))
> 
> When I commented out that last line it worked.  FWIW, I added the
> following advice which seems to help:
> 
> (define-advice rmail-show-message
>     (:around (fn &rest args) inhibit-display-buffer-alist)
>   (let ((display-buffer-alist nil))
>     (apply fn args)))
> 
> Is this an expected interaction or a bug?

Well, you in fact asked Emacs to use display-buffer-same-window for
displaying any buffer except the few you explicitly exempted, no?
Then I think it's what you asked for.

> AFAIU rmail-pop-to-buffer could use some form of display-buffer-* to
> avoid going through display-buffer-alist.

Yes, but I'm  not sure we should prevent users from customizing the
way Rmail buffers are displayed.

Perhaps Martin could comment on this?



reply via email to

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