Hi Kyle,
On Fri, 26 Jun 2020 at 22:03, Kyle Meyer <k...@kyleam.com> wrote:
I've managed to trigger it now. Your picture gave me the hint that
maybe my "making my frame height very small" wasn't the thing to do.
Plus I should have realized that the default-frame-alist in your
minimal
configuration probably isn't going to matter on my end because I use a
tiling window manager. So here's what I could trigger it:
(setq scroll-margin 1) ; or anything > 0
(setq display-buffer-base-action '(display-buffer-at-bottom))
For reasons I don't really understand, if I make my frame height small
(say half my computer screen) the issue goes away.
Anyway, I'm able to resolve the issues I see with this patch. Can you
confirm that it fixes things on your end?
Nice that you could find a way to trigger it too. Indeed, that was a
tricky one to pin down.
And I'm glad to confirm the patch fixes things on my end for the recipe
provided in the report. Same as you, I don't fully understand the
interactions which trigger the issue, so I can only claim that "I can no
longer reproduce". Which is great, of course. But, as far as I
understand, the patch makes sense to me.
Thank you very much for sticking with me and finding a fix.
Best,
Gustavo.
