[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#30491: 26.0; (elisp) `Profiling'
From: |
Drew Adams |
Subject: |
bug#30491: 26.0; (elisp) `Profiling' |
Date: |
Sun, 18 Feb 2018 09:21:04 -0800 (PST) |
> 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.
I've submitted bug #30516 for this.
- bug#30491: 26.0; (elisp) `Profiling', (continued)
- bug#30491: 26.0; (elisp) `Profiling', Drew Adams, 2018/02/16
- bug#30491: 26.0; (elisp) `Profiling', Eli Zaretskii, 2018/02/17
- bug#30491: 26.0; (elisp) `Profiling', Drew Adams, 2018/02/18
- bug#30491: 26.0; (elisp) `Profiling', Drew Adams, 2018/02/18
- bug#30491: 26.0; (elisp) `Profiling', Drew Adams, 2018/02/18
- bug#30491: 26.0; (elisp) `Profiling',
Drew Adams <=