From: "Drew Adams" <drew.adams@oracle.com>
To: "'Aaron Meurer'" <asmeurer@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Mouse support does not work
Date: Sat, 14 Jan 2012 09:37:52 -0800 [thread overview]
Message-ID: <29552883E608471BA2ACB9004FAD7FDC@us.oracle.com> (raw)
In-Reply-To: <CAKgW=6KPH7uj5ZyChJAz4oh6Vq7KCrc-gYoeCmjAqkC6s6NhUw@mail.gmail.com>
> The problem I'm encountering is that when I scroll by the smallest
> amount with the mouse, it scrolls by two lines. I have the
> mouse-wheel-scroll-amount set to 1.
I'm no expert on this - perhaps someone else can help more.
But if the value of `mouse-wheel-scroll-amount' is 1 (or 2 etc.) then that is
wrong. It needs to be an alist or a number representing the fraction of the
screen to scroll.
Use `M-x customize-option' to change the option - do not just `setq' it to an
integer value. Read the variable's doc (`C-h v').
> If I set it to 2, it scrolls by
> 4, and so on. vim does the same thing, so I suspect that what's
> happening is that a single scroll is being reported as two.
> But the
> only way to be sure would be to get something that echos all
> keystrokes, so I could see if a single scroll is really being reported
> as two mouse-5 events. C-h k won't work for this, because it only
> would show the first such event (if my theory is correct).
Wrt keystroke echoing, you can use `echo-keystrokes', as I mentioned.
You also have `C-h l', to see the last 100 keystrokes.
> Actually, I think I figured out that it's correct anyway, because I
> did C-h k and then scrolled up, and it showed me the help for mouse-5
> *and then* scrolled the document up by exactly one line.
>
> So I'll be reporting this as a bug to iTerm2. I'll post back here if
> I find a solution.
next prev parent reply other threads:[~2012-01-14 17:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 9:18 Mouse support does not work Aaron Meurer
2012-01-10 17:24 ` Tassilo Horn
2012-01-10 18:29 ` Eli Zaretskii
2012-01-10 21:00 ` Tassilo Horn
2012-01-10 21:32 ` Peter Dyballa
2012-01-11 8:04 ` Tassilo Horn
2012-01-11 22:12 ` Peter Dyballa
2012-01-12 7:22 ` Tassilo Horn
2012-01-12 9:44 ` Peter Dyballa
2012-01-12 9:56 ` Tassilo Horn
2012-01-12 10:06 ` Peter Dyballa
2012-01-10 21:31 ` Peter Dyballa
2012-01-10 21:29 ` Peter Dyballa
2012-01-10 22:06 ` Aaron Meurer
2012-01-10 22:31 ` Peter Dyballa
2012-01-10 22:50 ` Aaron Meurer
2012-01-10 23:26 ` Peter Dyballa
2012-01-11 12:50 ` Aaron Meurer
2012-01-11 14:24 ` Drew Adams
2012-01-11 14:37 ` Drew Adams
2012-01-11 15:28 ` Aaron Meurer
2012-01-11 19:10 ` Drew Adams
2012-01-11 21:14 ` Aaron Meurer
2012-01-14 16:45 ` Aaron Meurer
2012-01-14 16:53 ` Drew Adams
2012-01-14 17:26 ` Aaron Meurer
2012-01-14 17:37 ` Drew Adams [this message]
2012-01-14 17:49 ` Aaron Meurer
2012-01-14 18:20 ` Drew Adams
2012-01-14 19:55 ` Aaron Meurer
2012-01-14 20:08 ` Drew Adams
2012-01-14 20:32 ` Aaron Meurer
2012-01-14 21:00 ` Drew Adams
2012-01-15 0:01 ` Aaron Meurer
2012-01-15 0:55 ` Peter Dyballa
2012-01-15 0:58 ` Drew Adams
2012-01-15 15:19 ` Peter Dyballa
2012-01-15 1:13 ` Aaron Meurer
2012-01-15 15:28 ` Peter Dyballa
2012-01-15 15:47 ` Aaron Meurer
2012-01-15 16:30 ` Peter Dyballa
2012-01-16 18:22 ` Aaron Meurer
2012-01-14 17:46 ` Aaron Meurer
2012-01-10 23:44 ` Peter Dyballa
2012-01-11 6:31 ` Jonathan Groll
2012-01-11 6:15 ` Jonathan Groll
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=29552883E608471BA2ACB9004FAD7FDC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=asmeurer@gmail.com \
--cc=help-gnu-emacs@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.
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).