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#53170: 29.0.50; Can't repetitively click next node button inside Info header line Date: Tue, 11 Jan 2022 20:55:29 +0200 Message-ID: <83fspu6r1a.fsf@gnu.org> References: <877db7nhjn.fsf.ref@yahoo.com> <877db7nhjn.fsf@yahoo.com> <86h7aaiqx6.fsf@mail.linkov.net> <83y23m769y.fsf@gnu.org> <86iluqku65.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22138"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, 53170@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 11 20:17:07 2022 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 1n7Mdl-0005XF-9X for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 11 Jan 2022 20:17:05 +0100 Original-Received: from localhost ([::1]:45698 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7Mdk-0001Fg-DP for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 11 Jan 2022 14:17:04 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60716) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7MJO-0004e7-G1 for bug-gnu-emacs@gnu.org; Tue, 11 Jan 2022 13:56:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34415) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7MJO-0007uO-2F for bug-gnu-emacs@gnu.org; Tue, 11 Jan 2022 13:56:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n7MJO-0004rK-0b for bug-gnu-emacs@gnu.org; Tue, 11 Jan 2022 13:56:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 11 Jan 2022 18:56:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53170 X-GNU-PR-Package: emacs Original-Received: via spool by 53170-submit@debbugs.gnu.org id=B53170.164192735718660 (code B ref 53170); Tue, 11 Jan 2022 18:56:01 +0000 Original-Received: (at 53170) by debbugs.gnu.org; 11 Jan 2022 18:55:57 +0000 Original-Received: from localhost ([127.0.0.1]:55551 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n7MJI-0004qt-IT for submit@debbugs.gnu.org; Tue, 11 Jan 2022 13:55:56 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59908) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n7MJC-0004qJ-6I for 53170@debbugs.gnu.org; Tue, 11 Jan 2022 13:55:55 -0500 Original-Received: from [2001:470:142:3::e] (port=56008 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7MJ6-0007tM-7X; Tue, 11 Jan 2022 13:55:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=F7rUD/aDSL1duPd+64LMoHj/GusOl6G46P5Dg86kbLI=; b=qY/DaFXrn9wb WRYBe3/C8xqZBqV2zuYOasoLuK8vflPxzBqKP26x7q8nJhqCcrHd2/fdaS9LTX6UoTM8t6Si6NqBy QO51TxRTDDTT5dGCd5MgHVlyqRPwZed8ocgyxlirGqzT/yFg9r5iUMwJAr5hMLoHSGic/d2yMQk4J Sj/vB+gyicsR/dxAwxVXRoFok5H27VLk9GnjwYLLGcPDGzy3gOBSWnTt72aPijQkQ3pmwfoOPAxUU Sh4IWms7UwA/5+1JNA2RT7JbHwFE0Wn02lcmsq4iC/OMOudVLCZSK22ptYzCppa5FfL81vMocJoq5 upaXLl85mjW70c/2OwHHdQ==; Original-Received: from [87.69.77.57] (port=3484 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 1n7MJ1-0001ik-2V; Tue, 11 Jan 2022 13:55:44 -0500 In-Reply-To: <86iluqku65.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 11 Jan 2022 20:24:02 +0200) 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:223960 Archived-At: > From: Juri Linkov > Cc: luangruo@yahoo.com, 53170@debbugs.gnu.org > Date: Tue, 11 Jan 2022 20:24:02 +0200 > > >> (define-key keymap [mouse-2] 'Info-mouse-follow-link) > >> (define-key keymap [follow-link] 'mouse-face) > > > > Sorry, I don't understand how these settings explain the issue. > > AFAIU, the 450 msec is the time one need to _hold_ mouse-1 to make > > such a long mouse-1 press be considered as meaning "move point here". > > By contrast, what happens here is that 2 separate mouse-1 clicks, if > > the time between them is too short, seem to have no effect at all: > > Emacs neither follows the link nor does anything else. > > > > So I suspect that something else is at work here, or maybe the effect > > of mouse-1-click-follows-link is not documented accurately enough? > > > > Can you explain the observed behavior in more detail given the above > > defaults, please? In particular, how come a feature that's > > documented to affect only "click and hold" mouse gestures seems to > > affect double-click? > > The second click selects the word. Why is it useful to select the word on the header line? It doesn't do anything useful, AFAICT. > Could you arrange the Info dir buffer such that clicking on a menu > item opens another Info node, where the second quickly pressed mouse > button is on another menu? Then you will see the effect. It > selects the word on the menu item, instead of navigating to the node > under the menu item. Which means that the documentation of mouse-1-click-follows-link is completely off target, because it says nothing about its effect on double-click! This is yet another bad UI change, whereby seemingly insignificant random factors in what the user does cause very significant changes in behavior. In general, this should be unacceptable from the UX POV. While it could be tolerated when the user needs to press a mouse button continuously for almost 0.5 sec to have the "unusual" effect, it is IMO completely unacceptable when a quick double-click sometimes is processed as two single clicks, and causes Emacs to do nothing if the time interval is short enough. I think we should undo this "feature", at least in Info.