all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49784@debbugs.gnu.org, morelli@flux.utah.edu
Subject: bug#49784: 27.2; mouse-2 error with "No cross-reference here"
Date: Fri, 30 Jul 2021 21:49:03 +0200	[thread overview]
Message-ID: <87k0l7k2fk.fsf@gnus.org> (raw)
In-Reply-To: <8335rvr59j.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 30 Jul 2021 22:06:00 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> ;; The doc string is meant to explain what buttons do.
>> (defun help-follow-mouse ()
>>   "Follow the cross-reference that you click on."
>>   (interactive)
>>   (error "No cross-reference here"))
>> 
>> I guess the point is to...  not say
>> 
>> Buffer is read-only: #<buffer *Help*>
>> 
>> to be helpful?  It might just confuse more than it helps.
>
> Perhaps the comment before the function hints on why this was done
> that way.  IOW, if this binding didn't exist, what would C-h show for
> mouse-2, and how?

It'd say

It is bound to <mouse-2>.

(mouse-yank-primary CLICK)

like in any other buffer it's not bound.  I understand that the binding
was done to be helpful, but I'm just not sure that it's helpful to make
*Help* buffers behave weirdly.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-07-30 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 17:20 bug#49784: 27.2; mouse-2 error with "No cross-reference here" Robert Morelli
2021-07-30 18:09 ` Lars Ingebrigtsen
2021-07-30 18:22 ` Eli Zaretskii
2021-07-30 18:54   ` Lars Ingebrigtsen
2021-07-30 19:06     ` Eli Zaretskii
2021-07-30 19:49       ` Lars Ingebrigtsen [this message]
2021-07-31 11:29         ` Lars Ingebrigtsen

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=87k0l7k2fk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49784@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=morelli@flux.utah.edu \
    /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.