From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 9541@debbugs.gnu.org, Le Wang <l26wang@gmail.com>
Subject: bug#9541: mouse-1 inside scroll-margin causes undesirable region activation
Date: Sat, 24 Sep 2011 14:38:20 -0400 [thread overview]
Message-ID: <87vcsh6b1f.fsf@stupidchicken.com> (raw)
In-Reply-To: <87zkhvx9pe.fsf@gnu.org> ("Johan \=\?utf-8\?Q\?Bockg\=C3\=A5rd\=22's\?\= message of "Fri, 23 Sep 2011 22:52:45 +0200")
Johan Bockgård <bojohan@gnu.org> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> This said, the current behavior of scroll-margin is clearly problematic
>> and even buggy (e.g. it seems that displaying the EOB prevents the
>> mouse-clicks from causing a scroll, even when that scroll would be
>> towards the BOB).
>
> The real bug is that mouse-clicks set the mark (always). (Search for
> push-mark in mouse-drag-track.)
No, that's intended behavior. The OP's suggestion of disabling the
scroll margin while tracking a mouse drag is on the right track. I've
committed a change along those lines.
next prev parent reply other threads:[~2011-09-24 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 9:14 bug#9541: mouse-1 inside scroll-margin causes undesirable region activation Le Wang
[not found] ` <handler.9541.B.131633755619433.ack@debbugs.gnu.org>
2011-09-18 11:31 ` bug#9541: Acknowledgement (mouse-1 inside scroll-margin causes undesirable region activation) Le Wang
2011-09-19 18:34 ` bug#9541: mouse-1 inside scroll-margin causes undesirable region activation Stefan Monnier
2011-09-23 20:52 ` Johan Bockgård
2011-09-24 18:38 ` Chong Yidong [this message]
2011-10-02 10:03 ` New mouse click behavior (was: bug#9541: mouse-1 inside scroll-margin causes undesirable region activation) Johan Bockgård
2011-10-02 12:14 ` New mouse click behavior martin rudalics
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=87vcsh6b1f.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=9541@debbugs.gnu.org \
--cc=l26wang@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.