all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30491@debbugs.gnu.org
Subject: bug#30491: 26.0; (elisp) `Profiling'
Date: Sun, 18 Feb 2018 08:22:30 -0800 (PST)	[thread overview]
Message-ID: <bf5e200e-3401-43df-a327-69d436eb7916@default> (raw)
In-Reply-To: <cd12e8a4-a660-4816-b330-b0f63319153d@default>

> Not only that, but the normal behavior of non-nil
> `mouse-1-click-follows-link' is that if you hold `mouse-1'
> depressed for a moment the command simply sets point.
> But in the profiler report buffer doing that instead
> shows `C-h f' output for the function.
> 
> So it seems that the Profiler report key bindings do
> not respect `mouse-1-click-follows-link' for either
> a nil or a non-nil value.
> 
> This is bad design, IMO - a design bug.  It is pretty
> much impossible, it seems, to use `mouse-1' to set
> point.

My bad about that part.  Holding `mouse-1' depressed
does not show help on the function.  But I was right
that it also does not set point (as it should, if
`mouse-1-click-follows-link' were respected).

Holding `mouse-1' for a moment does nothing different.
The slow click just toggles the entry, same as a fast
click.

---

I was confused here by reading the help for `C-h k'
for the `mouse-1' click.  At the end of that help I
read this:

  For documentation of the corresponding mouse down
  event <down-mouse-1>, click and hold the mouse button
  longer than 0.5 second(s).

I was misreading that as applying to the command whose
doc I was reading: `profiler-report-toggle-entry'.

Instead, that sentence is about the key action I used
at the prompt of `C-h k'.

I think this help text is unclear.  99% of the text
is about a COMMAND - the command bound to the mouse
up event.  And then, with no separation at all, we
read a sentence that is suddenly about the second
event you caused in response to the `C-h k' prompt'.

This is awful (IMHO).  At the very least, that
sentence should be set off with a clear separator
(e.g. horizontal line or C-l char), and it should
be in parentheses.

Some better help design is needed for this, in any
case.  I'm sure I won't be the last user to fall
prey to this design gotcha.





  reply	other threads:[~2018-02-18 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<d0e242c5-d77b-407e-a2a9-f60b3a48fcef@default>
     [not found] ` <<837ercc4mp.fsf@gnu.org>
2018-02-17 15:45   ` bug#30491: 26.0; (elisp) `Profiling' Drew Adams
2018-02-17 16:16     ` Noam Postavsky
2018-02-17 16:24     ` Eli Zaretskii
2018-02-18 17:36       ` Drew Adams
2018-02-20 18:26         ` Drew Adams
2021-10-23 17:01       ` Stefan Kangas
2021-10-23 18:18         ` bug#30491: [External] : " Drew Adams
2021-10-23 18:36           ` Stefan Kangas
2021-10-23 19:06             ` Drew Adams
2021-10-23 19:14             ` Eli Zaretskii
2021-10-23 19:38               ` Drew Adams
2021-10-24  5:49                 ` Eli Zaretskii
2021-10-23 21:13               ` Stefan Kangas
2021-10-23 19:12           ` Eli Zaretskii
2018-02-18 15:52     ` Drew Adams
2018-02-18 16:22       ` Drew Adams [this message]
2018-02-16 18:11 Drew Adams
2018-02-16 18:15 ` Drew Adams
2018-02-17 10:06 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf5e200e-3401-43df-a327-69d436eb7916@default \
    --to=drew.adams@oracle.com \
    --cc=30491@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.