unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29478@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#29478: 26.0.90; `C-h k' followed by mouse clicks no longer shows down event
Date: Sat, 9 Dec 2017 17:18:16 +0000	[thread overview]
Message-ID: <20171209171816.GA15719@ACM> (raw)
In-Reply-To: <83o9ni3l3i.fsf@gnu.org>

Hello, Eli.

On Fri, Dec 01, 2017 at 10:31:45 +0200, Eli Zaretskii wrote:
> > Date: Tue, 28 Nov 2017 20:33:00 -0800 (PST)
> > From: Drew Adams <drew.adams@oracle.com>
> > Cc: 29478@debbugs.gnu.org

> > > > > The down mouse-button event is no longer listed along with the up
> > > > > event when you use `C-h k' with a click event.  Dunno whether this
> > > was
> > > > > by design or is an oversight.

> > > I think if you press and hold the mouse button for (default) half a
> > > second, when you finally release it, C-h k will report the down mouse
> > > event.  At least this is how GPM behaves for me on a Linux tty.

> > Ah yes, thanks.  I see that now on MS Windows too.

> > > This seems to make sense, because anything bound to a down mouse
> > > event is going to be something like a drag event, where the mouse
> > > button is held for an extended period of time.

> > Sorry, no, I don't buy that.  I mean it's probably true that
> > most such bindings involve dragging.  But (1) a user who wants
> > to check what `mouse-N' does won't necessarily use it the same
> > way when checking with `C-h k' as when using it for its real
> > purpose.  And (2) the problem with this is that it is not
> > easily discoverable.

> > I've used Emacs for quite a while.  OK, I expected both up and
> > down to be documented.  But even I would likely never have
> > thought to hold the button pressed for a long time before
> > releasing, just to see what `C-h k' had to tell me.

> Alan, can we arrange for the doc string of mouse-N clicks (with or
> without all the possible modifiers) to say something like

>   For documentation of the corresponding mouse-down event, click and
>   hold the mouse button longer than %s sec.

> (where %s gets replaced by double-click-time)?

Yes, I'm sure I can manage that, hopefully in the coming week.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2017-12-09 17:18 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 23:21 bug#29478: 26.0.90; `C-h k' followed by mouse clicks no longer shows down event Drew Adams
2017-11-28  1:50 ` Noam Postavsky
2017-11-28 17:11   ` Eli Zaretskii
2017-11-28 22:10   ` Alan Mackenzie
2017-11-29  0:44     ` Noam Postavsky
2017-11-29  3:36       ` Eli Zaretskii
2017-11-29  4:33     ` Drew Adams
2017-12-01  8:31       ` Eli Zaretskii
2017-12-09 17:18         ` Alan Mackenzie [this message]
2017-12-23 14:28         ` bug#29478: [Patch 2]: " Alan Mackenzie
2017-12-23 14:48           ` Andreas Schwab
2017-12-24  8:43             ` Alan Mackenzie
     [not found]   ` <<20171128221036.GC14868@ACM>
     [not found]     ` <<bbcb1d00-a728-4b5e-b65f-bd2b168c4a51@default>
     [not found]       ` <<83o9ni3l3i.fsf@gnu.org>
2017-12-01 15:35         ` Drew Adams
2017-12-01 16:51           ` Eli Zaretskii
2017-12-09 16:13             ` Eli Zaretskii
2017-12-09 17:23               ` Alan Mackenzie
2017-12-22 22:05               ` Alan Mackenzie
2017-12-23  9:42                 ` Eli Zaretskii
2017-12-23 11:17                   ` bug#29478: [Patch] " Alan Mackenzie
2017-12-23 12:41                     ` Eli Zaretskii
2017-12-23 16:33                     ` Stefan Monnier
2017-12-23 21:04                       ` Alan Mackenzie
2017-12-24  4:55                         ` Stefan Monnier
2017-12-24  5:41                           ` Eli Zaretskii
2017-12-24  6:52                         ` Stefan Monnier
2017-12-24 11:48                           ` Alan Mackenzie
2017-12-24 15:41                             ` Stefan Monnier
2017-12-30 10:50                           ` Eli Zaretskii
2018-01-03  3:56                             ` Stefan Monnier
2018-01-06 17:40                               ` Eli Zaretskii
2018-01-07 15:31                                 ` bug#29478: [SUSPECTED SPAM] " Stefan Monnier
2018-01-07 17:46                                   ` Eli Zaretskii
2018-01-07 18:03                                     ` Stefan Monnier
2018-01-26 22:00                                 ` bug#29478: " Stefan Monnier
2018-01-26 22:37                                   ` Stefan Monnier
2018-01-27  8:28                                     ` Eli Zaretskii
2018-01-28 16:02                                       ` Stefan Monnier
2018-01-28 17:18                                         ` Eli Zaretskii
2018-01-29 21:54                                           ` Stefan Monnier
2018-01-30  3:23                                             ` Eli Zaretskii
2018-01-30 14:18                                               ` Stefan Monnier
2018-01-30 15:40                                                 ` Eli Zaretskii
2018-01-30 16:59                                                   ` Stefan Monnier
2018-01-27  7:59                                   ` Eli Zaretskii
2017-12-30 10:51                         ` Eli Zaretskii
2017-12-30 11:32                           ` Alan Mackenzie
2017-12-30 12:49                             ` Eli Zaretskii
2017-12-23 16:19             ` bug#29478: " Stefan Monnier
2020-08-26 13:43 ` bug#29478: 26.0.90; " Lars Ingebrigtsen
2020-08-26 17:12   ` Drew Adams

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=20171209171816.GA15719@ACM \
    --to=acm@muc.de \
    --cc=29478@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).