From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29272@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#29272: 26.0.90; "C-h k C-mouse-3" followed by menu selection asks for more keys
Date: Fri, 1 Dec 2017 16:57:40 +0000 [thread overview]
Message-ID: <20171201165740.GE3840@ACM> (raw)
In-Reply-To: <83609s52xt.fsf@gnu.org>
Hello, Eli.
On Wed, Nov 29, 2017 at 20:56:30 +0200, Eli Zaretskii wrote:
> > Date: Wed, 29 Nov 2017 18:37:17 +0000
> > Cc: Eli Zaretskii <eliz@gnu.org>,
> > Noam Postavsky <npostavs@users.sourceforge.net>, 29272@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > Personally, I think the value t is a bad idea, and we should obsolete
> > it.
> That's not going to fly. We have absolutely no reason for making this
> obsolete.
> in any case, this discussion is not about double-click-time's purpose,
> it's about what should "C-h k" when it is not a number. I proposed a
> practical solution; does anyone see a problem with it?
> > Maybe we should interpret t as a moderately long finite interval, say 10
> > seconds.
> 10 seconds is too long, I think 1 sec is much better.
I hope I'm not bikeshedding, but 1 second may be too little. I'm
thinking about two use cases: (i) where a user's mouse button is almost
worn out, and it takes several attempted presses before one registers;
(ii) A disabled user who has physical difficulty in pressing the mouse
button, and needs that extra time to do so. Either of these may be a
reason for setting double-click-time to t.
Maybe not as long as 10s. How about compromising with the geometric
mean of 1s and 10s, namely 3.162s?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-12-01 16:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 11:23 bug#29272: 26.0.90; "C-h k C-mouse-3" followed by menu selection asks for more keys Eli Zaretskii
2017-11-12 12:38 ` Eli Zaretskii
2017-11-12 13:24 ` Alan Mackenzie
2017-11-14 20:54 ` Alan Mackenzie
2017-11-18 11:27 ` Eli Zaretskii
2017-11-18 15:15 ` Alan Mackenzie
2017-11-19 16:19 ` Alan Mackenzie
2017-11-19 17:04 ` Eli Zaretskii
2017-11-19 17:44 ` Eli Zaretskii
2017-11-19 17:54 ` Alan Mackenzie
2017-11-19 18:17 ` Eli Zaretskii
2017-11-19 20:26 ` Alan Mackenzie
2017-11-29 0:50 ` Noam Postavsky
2017-11-29 3:38 ` Eli Zaretskii
2017-11-29 8:39 ` martin rudalics
2017-11-29 13:19 ` Noam Postavsky
2017-11-29 17:53 ` Eli Zaretskii
2017-11-30 7:22 ` martin rudalics
2017-11-29 17:55 ` Eli Zaretskii
2017-11-29 18:37 ` Alan Mackenzie
2017-11-29 18:56 ` Eli Zaretskii
2017-12-01 16:57 ` Alan Mackenzie [this message]
2017-12-01 19:18 ` Drew Adams
2017-12-01 19:43 ` Eli Zaretskii
2017-11-30 7:22 ` martin rudalics
[not found] <<83shdjn3ju.fsf@gnu.org>
[not found] ` <<83mv3rn02t.fsf@gnu.org>
[not found] ` <<20171114205449.GA8025@ACM>
[not found] ` <<87fu8xnc17.fsf@users.sourceforge.net>
[not found] ` <<83h8td4uw5.fsf@gnu.org>
[not found] ` <<5A1E724A.5030507@gmx.at>
[not found] ` <<20171129183717.GA8914@ACM>
[not found] ` <<83609s52xt.fsf@gnu.org>
[not found] ` <<20171201165740.GE3840@ACM>
[not found] ` <<1c4abffb-e975-41b1-a368-29518bc3b360@default>
[not found] ` <<83y3mm1bfu.fsf@gnu.org>
2017-12-01 21:12 ` Drew Adams
2017-12-02 8:13 ` Eli Zaretskii
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=20171201165740.GE3840@ACM \
--to=acm@muc.de \
--cc=29272@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).