From: Stephen Berman <stephen.berman@gmx.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 886@emacsbugs.donarmstrong.com
Subject: bug#886: 23.0.60; Info-mouse-follow-nearest-node fails
Date: Mon, 15 Sep 2008 11:25:46 +0200 [thread overview]
Message-ID: <87hc8h221x.fsf@escher.local.home> (raw)
In-Reply-To: <48CE1DF9.6020904@gmx.at> (martin rudalics's message of "Mon, 15 Sep 2008 10:34:01 +0200")
On Mon, 15 Sep 2008 10:34:01 +0200 martin rudalics <rudalics@gmx.at> wrote:
> The fix seems to have the following side-effect: In my .emacs I bind
>
> (define-key Info-mode-map [mouse-1] 'Info-mouse-follow-nearest-node)
> Now when I use mouse-1 to just "select" the Info-window I usually get
>
> Info-follow-nearest-node: Point neither on reference nor in menu item description
>
> which is annoying :-(
>
> martin
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)
Steve Berman
next prev parent reply other threads:[~2008-09-15 9:25 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 [this message]
2008-09-15 12:11 ` martin rudalics
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=87hc8h221x.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=886@emacsbugs.donarmstrong.com \
--cc=rudalics@gmx.at \
/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.