Strategies for *Warnings* buffer?

What strategies do you use for displaying or notifying about the `*Warnings*` buffer? Since a while I use a bottom side window (code below) to display it. But I grew dissatisfied with that solution, because often it eats valuable space (e.g. resizes the pdf-tools buffer, aww). I have other stuff in the bottom side window as well (e.g. SLY-REPL, shells and terminals) at different slots. I experimented with resizing the *Warnings* buffer window when it pops up, but that resizes other mentioned windows (also not a good solution). I think it is necessary to being notified about a fresh `*Warnings*` buffer, but that should not disturb to much. I thought about just displaying a message, or popping up a dedicated `*Warnings*` frame, or is there something more volatile?. What useful solutions do you use? --- Source code of my current handling of the `*Warnings*` buffer: (add-to-list 'display-buffer-alist '("\\*\\(Warnings\\)\\*" (display-buffer-reuse-window display-buffer-reuse-mode-window display-buffer-in-previous-window display-buffer-in-side-window) (window-height . 0.25) (side . bottom) (slot . 1)))

Am I missing something or does one often see the Warnings buffer? If it is once in a while, I wonder about the necessity to configure it as getting rid of the window is a single key.

I use [popper](https://github.com/karthink/popper) for buffers I only need to see briefly.

I get a warning regularly, when compiling LaTeX documents, due to synctex and my workflow. There is a `warning-suppress-warning` (for server-type warnings) button nearby, which I will not press, because in half a year, after doing nothing with latex at all, I will wonder why synctex stuff (or some other yet unknown feature) is not working (I know this can and would happen to me. ;))

I have not done it myself (but is in my evergrowing todo): display those dismissable-with-q windows with a centered new frame It would keep the same modal, blocking and focused UX without messing with what's behind that was already there

As with all such things, I let Emacs show me the buffer however it wants, because I'm using `winner-mode` and going back to the way things were before the buffer appeared is a `winner-undo` keystroke away.

Aha! That explains it then.

I though about something like this to, but without the "modal" feature. I wonder if this is gonna usable. :)

I experimented a bit with that, I have not yet grasped the full benefits of it. What would be the benefits over using side windows?

You can customize popper to show popups any way you’d like. Any display-buffer action function can work, or you can write your own. I automatically add some buffers to popper to hide/show them in a dedicated window via the popper key binding. I never investigated if we can immediately hide specific buffers, but if so then popper would be your thing.

Perhaps seeing the video presentation of popper by Karthik should tell a better story?

Poppers killer feature (for me) is popper-toggle-latest that hides (and unhides!) any window identified by regex in popper-reference-buffer use this: (setq popper-reference-buffers '("\\*Messages\\*" "\\*Error\\*" "Output\\*$" "\\*Warnings\\*" "\\*Async Shell Command\\*" ;; "\\*Ilist\\*.*" help-mode compilation-mode inferior-python-mode))