From: martin rudalics <rudalics@gmx.at>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 886@emacsbugs.donarmstrong.com
Subject: bug#886: 23.0.60; Info-mouse-follow-nearest-node fails
Date: Mon, 15 Sep 2008 14:11:38 +0200 [thread overview]
Message-ID: <48CE50FA.4030501@gmx.at> (raw)
In-Reply-To: <87hc8h221x.fsf@escher.local.home>
> Does the following patch fix it?
>
> *** emacs/lisp/info.el.~1.544.~ 2008-09-11 11:49:36.000000000 +0200
> --- emacs/lisp/info.el 2008-09-15 11:22:53.000000000 +0200
> ***************
> *** 3123,3129 ****
> (Info-goto-node
> (Info-extract-menu-item (match-string-no-properties 1)) fork)
> t)))
> ! (error "Point neither on reference nor in menu item description")))
>
> ;; Common subroutine.
> (defun Info-try-follow-nearest-node (&optional fork)
> --- 3123,3130 ----
> (Info-goto-node
> (Info-extract-menu-item (match-string-no-properties 1)) fork)
> t)))
> ! (unless (eq this-command 'Info-mouse-follow-nearest-node)
> ! (error "Point neither on reference nor in menu item description"))))
>
> ;; Common subroutine.
> (defun Info-try-follow-nearest-node (&optional fork)
Yes - the following seems simpler:
! (eq this-command 'Info-mouse-follow-nearest-node)
! (error "Point neither on reference nor in menu item description")))
I'm not sure though whether we should raise an error for mouse-2 clicks.
But I also fail to understand why we should raise an error at all.
martin
next prev parent reply other threads:[~2008-09-15 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 8:34 bug#886: 23.0.60; Info-mouse-follow-nearest-node fails martin rudalics
2008-09-15 9:25 ` Stephen Berman
2008-09-15 12:11 ` martin rudalics [this message]
2008-09-15 13:48 ` Stephen Berman
2008-09-17 6:54 ` martin rudalics
-- strict thread matches above, loose matches on Subject: below --
2008-09-04 14:31 Stephen Berman
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=48CE50FA.4030501@gmx.at \
--to=rudalics@gmx.at \
--cc=886@emacsbugs.donarmstrong.com \
--cc=stephen.berman@gmx.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 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.