From: Aaron Jensen <aaronjensen@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31546@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#31546: 27.0.50; macOS child frames with no mode-line mouse click problem
Date: Thu, 24 May 2018 08:58:32 -0700 [thread overview]
Message-ID: <CAHyO48wWvewzi=tPfGiqRvJdiCbP-CxJyXasjX6tEcEir4Tptg@mail.gmail.com> (raw)
In-Reply-To: <83o9h5ax8n.fsf@gnu.org>
On Thu, May 24, 2018 at 8:29 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Is this NS specific? I cannot reproduce any problem with the original
> recipe posted with this bug report, but maybe you are already using a
> modified one (the talk about pixelwise resizing seems to suggest
> that)?
> If it's NS-specific, I'd like to understand the issue deeper before we
> decide how and on which branch to fix it.
It could very well be. I don't have a non-NS machine to test. The behavior
seems isolated to frames that have no-accept-focus set. It doesn't actually
require the frame to be a child frame. This is the minimal repro so far:
(progn
(let ((buffer (get-buffer " *foo*")))
(when (buffer-live-p buffer)
(kill-buffer buffer)))
(let ((buffer (get-buffer-create " *foo*"))
(after-make-frame-functions nil))
(with-current-buffer buffer
(goto-char (point-min))
(insert "1 This is a test\n2 This is a test\n3 This is a test")
(delete-region (point) (point-max))
(setq-local resize-mini-windows nil)
(setq-local mode-line-format nil)
(setq-local repro-frame
(make-frame
`(
(minibuffer . nil)
(no-accept-focus . t)
)
))
(let ((win (frame-root-window repro-frame)))
(set-window-parameter win 'mode-line-format nil)
(set-window-buffer win buffer)))))
It's easier to repro if after evaling you move the new frame so that it no
longer overlaps the original frame. Then click a few px from the bottom of
the frame--about half of a line-height from the bottom. You may need to
click a couple of times (slowly) around this area. I tend to have the best
luck towards the bottom left of the frame. Here's a gif:
https://cl.ly/1R3Q231u201R/Screen%20Recording%202018-05-24%20at%2008.56%20AM.gif
One question is, on other platforms, if you inspect the start-event in
mouse-drag-region is it for the new frame or the original frame? For me on
macOS, it's for the new frame even though no-accept-focus is set.
> What do you mean by "a line that the buffer does not extend to"? Is
> that empty space beyond EOB, or is that something else?
Yes.
next prev parent reply other threads:[~2018-05-24 15:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 5:23 bug#31546: 27.0.50; macOS child frames with no mode-line mouse click problem Aaron Jensen
2018-05-22 7:25 ` martin rudalics
2018-05-22 7:33 ` Aaron Jensen
2018-05-22 8:40 ` martin rudalics
2018-05-22 12:51 ` Aaron Jensen
2018-05-22 19:33 ` Alan Third
2018-05-22 19:36 ` Aaron Jensen
2018-05-22 19:44 ` Alan Third
2018-05-22 19:51 ` Aaron Jensen
2018-05-23 6:36 ` martin rudalics
2018-05-23 11:14 ` Aaron Jensen
2018-05-23 21:31 ` Alan Third
2018-05-23 22:21 ` Aaron Jensen
2018-05-24 7:19 ` martin rudalics
2018-05-24 10:53 ` Aaron Jensen
2018-05-24 11:06 ` Aaron Jensen
2018-05-24 15:28 ` Eli Zaretskii
2018-05-24 15:58 ` Aaron Jensen [this message]
2018-05-25 6:34 ` martin rudalics
2018-05-26 16:38 ` Alan Third
2018-05-26 17:02 ` Aaron Jensen
2018-05-26 18:22 ` Alan Third
2018-05-26 20:15 ` Aaron Jensen
2018-05-27 6:22 ` martin rudalics
2018-05-27 15:57 ` Eli Zaretskii
2018-05-27 17:13 ` Aaron Jensen
2018-05-27 17:38 ` Eli Zaretskii
2018-05-27 17:52 ` Aaron Jensen
2018-05-27 18:52 ` Aaron Jensen
2018-05-27 21:24 ` Alan Third
2018-05-27 21:53 ` Aaron Jensen
2018-06-02 6:35 ` Aaron Jensen
2018-06-02 8:00 ` Eli Zaretskii
2018-06-02 15:41 ` Aaron Jensen
2018-06-14 16:37 ` Aaron Jensen
2018-06-14 20:40 ` Alan Third
2018-06-14 21:21 ` Aaron Jensen
2018-06-15 7:02 ` Eli Zaretskii
2018-06-17 11:08 ` Alan Third
2018-06-17 12:03 ` Aaron Jensen
2018-05-24 15:27 ` Eli Zaretskii
2018-05-24 7:19 ` martin rudalics
2018-05-23 6:36 ` martin rudalics
2018-05-23 6:36 ` martin rudalics
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHyO48wWvewzi=tPfGiqRvJdiCbP-CxJyXasjX6tEcEir4Tptg@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=31546@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs.git
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).