unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: , emacs-devel@gnu.org
Subject: Re: mouse not working in 'info'
Date: Sun, 25 Mar 2018 16:47:22 +0100	[thread overview]
Message-ID: <87o9jcnomt.fsf@yandex.com> (raw)
In-Reply-To: <83a7uwgonw.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 25 Mar 2018 18:28:35 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

    >> From: Colin Baxter <m43cap@yandex.com> Date: Sun, 25 Mar 2018
    >> 15:15:17 +0100
    >> 
    >> I'm using emacs-27.0.50 (build 1, i686-pc-linux-gnu, GTK+ Version
    >> 3.14.5) on 3.16.0-5-686-pae #1 SMP Debian 3.16.51-3+deb8u1.
    >> 
    >> With emacs -q, M-x info RET, if I attempt to use the mouse to go
    >> up the hierarchy of links, i.e., Next: Prev: Up:, I get the
    >> errors
    >> 
    >> <header-line> <header-line> <mouse-2> is undefined <header-line>
    >> <mouse-3> is undefined
    >> 
    >> if I left- and right-click respectively. I only have a *two*
    >> button mouse. The issue exists only on going up the hierarchy of
    >> nodes, not down.

    > Can you show the output of "C-h l" after these errors?

M-x			;; execute-extended-command
 i			;; self-insert-command
 n			;; self-insert-command
 f			;; self-insert-command
 o			;; self-insert-command
 <return>		;; minibuffer-complete-and-exit
 <help-echo> <help-echo> <help-echo> <help-echo> <down-mouse-1> ;; mouse-drag-region
 <help-echo> <mouse-movement> ;; anonymous-command
 <mouse-1>		      ;; Info-mouse-follow-nearest-node
 <help-echo> <help-echo> <help-echo> <down-mouse-1> ;; mouse-drag-header-line
 <mouse-1>					    ;; nil
 C-h l						    ;; view-lossage



  reply	other threads:[~2018-03-25 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-25 14:15 mouse not working in 'info' Colin Baxter
2018-03-25 15:28 ` Eli Zaretskii
2018-03-25 15:47   ` Colin Baxter [this message]
2018-03-25 16:44     ` Eli Zaretskii
2018-03-25 17:03       ` Colin Baxter
2018-03-25 17:19         ` Eli Zaretskii
2018-03-25 17:32           ` Eli Zaretskii
2018-03-25 20:10             ` Stefan Monnier
2018-03-26 15:00               ` Eli Zaretskii
2018-03-25 18:47           ` Colin Baxter

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87o9jcnomt.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).