From: Gustavo Barros <email@example.com>
To: Kyle Meyer <firstname.lastname@example.org>
Subject: Re: [PATCH] ox: Prevent dispatcher from starting in scrolled window
Date: Fri, 26 Jun 2020 23:00:51 -0300 [thread overview]
Message-ID: <email@example.com> (raw)
On Fri, 26 Jun 2020 at 22:03, Kyle Meyer <firstname.lastname@example.org> 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
> 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.
next prev parent reply other threads:[~2020-06-27 2:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 4:56 Bug: Export dispatcher scrolling with hidden top [9.3.6 (9.3.6-17-g389288-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200224/)] Gustavo Barros
2020-06-02 11:03 ` Gustavo Barros
2020-06-02 11:45 ` Bastien
2020-06-09 4:48 ` Kyle Meyer
2020-06-09 11:48 ` Gustavo Barros
2020-06-27 1:03 ` [PATCH] ox: Prevent dispatcher from starting in scrolled window Kyle Meyer
2020-06-27 2:00 ` Gustavo Barros [this message]
2020-06-27 4:06 ` Kyle Meyer
2020-09-04 8:45 ` Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).