popupinfo seems like a great addition, and solves the problem of too many chefs working in the echo area for docstrings/flymake/lsp info etc. On MacOS there is a noticeable visual flicker when each popupinfo frame is displayed, with or without hiding in between. What appears in the "flash" is the text of the current buffer, shifted by half a page or so (including the modeline from below it), before disappearing. To me it looks like the current window is being split, a new window visiting the same buffer is created, and then swiftly buried just as the child frame comes into view. Interestingly, if the frame already has two windows, the flashing does not occur. And the flashing is directional: if you've last split the window with C-x 3, it happens in a phantom horizontally aligned disappearing window.
popupinfo seems like a great addition, and solves the problem of too many chefs working in the echo area for docstrings/flymake/lsp info etc. On MacOS there is a noticeable visual flicker when each popupinfo frame is displayed, with or without hiding in between. What appears in the "flash" is the text of the current buffer, shifted by half a page or so (including the modeline from below it), before disappearing. To me it looks like the current window is being split, a new window visiting the same buffer is created, and then swiftly buried just as the child frame comes into view. Interestingly, if the frame already has two windows, the flashing does not occur. And the flashing is directional: if you've last split the window with C-x 3, it happens in a phantom horizontally aligned disappearing window.
https://user-images.githubusercontent.com/93749/205507594-6da4778e-2099-407f-8655-6e5d8749a3ab.mov
By tracing, I found
split-window
is called indirectly by elisp-mode capf's company doc function:And here is a telling comment: