From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#31546: 27.0.50; macOS child frames with no mode-line mouse click problem Date: Sun, 27 May 2018 20:38:53 +0300 Message-ID: <8336yd80cy.fsf@gnu.org> References: <20180523213124.GC36578@breton.holly.idiocy.org> <5B06679A.2020407@gmx.at> <83o9h5ax8n.fsf@gnu.org> <20180526163844.GA16324@breton.holly.idiocy.org> <20180526182215.GA18042@breton.holly.idiocy.org> <5B0A4EC3.6080403@gmx.at> <83h8mt851r.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1527442688 13335 195.159.176.226 (27 May 2018 17:38:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 27 May 2018 17:38:08 +0000 (UTC) Cc: 31546@debbugs.gnu.org, alan@idiocy.org To: Aaron Jensen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun May 27 19:38:04 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fMzcH-0003KT-Tm for geb-bug-gnu-emacs@m.gmane.org; Sun, 27 May 2018 19:38:02 +0200 Original-Received: from localhost ([::1]:52789 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMzeP-0005Hp-0l for geb-bug-gnu-emacs@m.gmane.org; Sun, 27 May 2018 13:40:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33911) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMzeI-0005HV-Na for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 13:40:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fMzeF-0001e6-Kh for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 13:40:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43313) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fMzeF-0001e2-HK for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 13:40:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fMzeE-0005T2-7B for bug-gnu-emacs@gnu.org; Sun, 27 May 2018 13:40:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 27 May 2018 17:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31546 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31546-submit@debbugs.gnu.org id=B31546.152744275720962 (code B ref 31546); Sun, 27 May 2018 17:40:02 +0000 Original-Received: (at 31546) by debbugs.gnu.org; 27 May 2018 17:39:17 +0000 Original-Received: from localhost ([127.0.0.1]:51210 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fMzdU-0005S2-RV for submit@debbugs.gnu.org; Sun, 27 May 2018 13:39:17 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42856) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fMzdQ-0005Rk-1L for 31546@debbugs.gnu.org; Sun, 27 May 2018 13:39:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fMzdH-0000xr-Ja for 31546@debbugs.gnu.org; Sun, 27 May 2018 13:39:06 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52422) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMzdH-0000xZ-Fs; Sun, 27 May 2018 13:39:03 -0400 Original-Received: from [176.228.60.248] (port=2582 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fMzdG-0001R3-Si; Sun, 27 May 2018 13:39:03 -0400 In-reply-to: (message from Aaron Jensen on Sun, 27 May 2018 10:13:55 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:146606 Archived-At: > From: Aaron Jensen > Date: Sun, 27 May 2018 10:13:55 -0700 > Cc: martin rudalics , Alan Third , 31546@debbugs.gnu.org > > On Sun, May 27, 2018 at 8:58 AM Eli Zaretskii wrote: > > Based on the description, I think it's redisplay that's scrolling, > > because the mouse click sets point in a line that is visible only > > partially. > > To be clear, this is only true if my patch is applied. If my patch is not > applied, clicking on the last line of a frame that has no minibuffer and no > mode-line also triggers the scroll as well because the fact that it has no > mode-line is not taken into account. Not sure I understand the connection between not having a mode line and the scroll. Can you elaborate? Apologies if this was already explained up-thread. > Also, why is it that the point can be set to a location past the buffer's > end? The point won't actually move there visually, so I'm not sure why it > can be set there. "Doesn't move there" and "can be set there" sounds like a contradiction, doesn't it? I'm probably missing something because I don't understand what you describe. Clicking on the empty area beyond the last buffer position should move point to EOB, but you seem to be talking about something else? > > One can make sure by invoking trace-redisplay before > > clicking (but make sure you have blink-cursor-mode and > > global-eldoc-mode turned off before you do that, to avoid unnecessary > > redisplay cycles that will muddy the waters). > > trace-redisplay is only in x, it doesn't appear to be defined in ns. You need to build with --enable-checking='yes,glyphs' to have that command compiled into Emacs. It's on xdisp.c, so it should be available on all builds. I usually find its output helpful because it provides hints for where to look for relevant code. Of course, if the problem is in NS specific code, we won't see anything interesting in the trace.