unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 53170@debbugs.gnu.org
Subject: bug#53170: 29.0.50; Can't repetitively click next node button inside Info header line
Date: Tue, 11 Jan 2022 20:24:02 +0200	[thread overview]
Message-ID: <86iluqku65.fsf@mail.linkov.net> (raw)
In-Reply-To: <83y23m769y.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 11 Jan 2022 15:26:17 +0200")

>> > Starting from emacs -Q, say "C-h i m tramp RET", then click the text
>> > that reads "Next: Overview".  As long as you don't move the mouse at
>> > all, you won't be able to click that button again.
>> 
>> I guess this is the case when you click the mouse button too fast?
>> By default, mouse-1-click-follows-link is 450, and Info-link-keymap
>> uses such settings:
>> 
>>     (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.  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.





  reply	other threads:[~2022-01-11 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877db7nhjn.fsf.ref@yahoo.com>
2022-01-11  2:16 ` bug#53170: 29.0.50; Can't repetitively click next node button inside Info header line Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11  9:01   ` Juri Linkov
2022-01-11  9:40     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 13:26     ` Eli Zaretskii
2022-01-11 18:24       ` Juri Linkov [this message]
2022-01-11 18:55         ` Eli Zaretskii
2022-01-11 19:12           ` Juri Linkov
2022-01-11 20:03             ` Eli Zaretskii
2022-01-12 17:20               ` Juri Linkov
2022-01-12 17:29                 ` Eli Zaretskii
2022-01-24 18:56                   ` Juri Linkov

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=86iluqku65.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=53170@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).