From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#15783: 24.3; posn-at-x-y is relative to the buffer area, posn-at-point is relative to the text area. Date: Sat, 23 Oct 2021 09:49:13 +0300 Message-ID: <83wnm45j86.fsf@gnu.org> References: <83fvrgaxrp.fsf@gnu.org> <87k1yp4aar.fsf@gmail.com> <83zi7lgshu.fsf@gnu.org> <87mv3kqekw.fsf@gmail.com> <837euogeu7.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22773"; mail-complaints-to="usenet@ciao.gmane.io" Cc: shiino.yuki@gmail.com, 15783@debbugs.gnu.org, agrambot@gmail.com To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 23 08:50:48 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1meArg-0005nO-Pq for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Oct 2021 08:50:48 +0200 Original-Received: from localhost ([::1]:51648 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1meArf-0003qX-9M for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 23 Oct 2021 02:50:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38568) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1meAqx-0003qO-0t for bug-gnu-emacs@gnu.org; Sat, 23 Oct 2021 02:50:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50905) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1meAqw-0001cc-Oi for bug-gnu-emacs@gnu.org; Sat, 23 Oct 2021 02:50:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1meAqw-0001RS-HQ for bug-gnu-emacs@gnu.org; Sat, 23 Oct 2021 02:50:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 23 Oct 2021 06:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15783 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 15783-submit@debbugs.gnu.org id=B15783.16349717895519 (code B ref 15783); Sat, 23 Oct 2021 06:50:02 +0000 Original-Received: (at 15783) by debbugs.gnu.org; 23 Oct 2021 06:49:49 +0000 Original-Received: from localhost ([127.0.0.1]:34218 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1meAqh-0001Qt-V7 for submit@debbugs.gnu.org; Sat, 23 Oct 2021 02:49:49 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:41152) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1meAqT-0001QS-IV for 15783@debbugs.gnu.org; Sat, 23 Oct 2021 02:49:47 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52960) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1meAqO-0001MA-0f; Sat, 23 Oct 2021 02:49:28 -0400 Original-Received: from [87.69.77.57] (port=3430 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1meAqN-0000lS-Dx; Sat, 23 Oct 2021 02:49:27 -0400 In-Reply-To: (message from Stefan Kangas on Fri, 22 Oct 2021 19:27:38 -0400) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:217945 Archived-At: > From: Stefan Kangas > Date: Fri, 22 Oct 2021 19:27:38 -0400 > Cc: Alex , shiino.yuki@gmail.com, 15783@debbugs.gnu.org > > > Therefore, the doc string is accurately describing the actual behavior. > > Do you agree now? > > I looked into this for a bit, and as far as I understand, Eli is > correct. > > > We are not going back. The current behavior, while less than ideal, > > caused zero bugs since it was introduced, AFAIK. The documentation > > should be updated, of course (I see that the above-mentioned commit > > didn't do that, which is probably why the old description survived to > > this day). > > How does the attached patch look? Yes, but with one correction: > --- a/doc/lispref/commands.texi > +++ b/doc/lispref/commands.texi > @@ -2354,10 +2354,11 @@ Accessing Mouse > coordinates @var{x} and @var{y} in a specified frame or window, > @var{frame-or-window}, which defaults to the selected window. > The coordinates @var{x} and @var{y} are relative to the > -frame or window used. > -If @var{whole} is @code{nil}, the coordinates are relative > -to the window text area, otherwise they are relative to > -the entire window area including scroll bars, margins and fringes. > +text area of the selected window. > +If @var{whole} is @code{nil}, the @var{x} coordinate is relative to ^^^^^^^^^^^^^^^^^^^^^^^^^ You mean, non-nil, right? > +the entire window area including scroll bars, margins and fringes, > +while the @var{y} coordinate remains unchanged and relative to the > +text area. And I wouldn't mention what WHOLE does to Y, because it just confuses things. Y remains unchanged simply because there are no window decorations that affect Y coordinates, but there's no need to tell that in a doc string; if we say nothing about Y, it still tells that Y is unchanged.