From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
To: eliz@gnu.org
Cc: tkk@misasa.okayama-u.ac.jp, 26599@debbugs.gnu.org
Subject: bug#26599: patch for mwheel.el
Date: Thu, 27 Apr 2017 08:33:56 +0900 (JST) [thread overview]
Message-ID: <20170427.083356.368391024.tkk@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <83pofznq1x.fsf@gnu.org>
>> >> Let’s consider a buffer consists of very long lines and an empty line.
>> >> Point starts from A with auto-hscroll-mode t.
>> >>
>> >> 0000..0000 A
>> >> 0000..0000 I
>> >> C B
>> >> D 00..0000 Z
>>
>> Point reaches to B by scrolling up and as soon as auto-hscroll-mode is
>> set to t, scope will be shifted to point C.
>>
>> I want to maintain scope with B instead of having scope with C before
>> another scrolling.
>
> If that's what you want, why do you need to turn auto-hscroll-mode
> back on? Just leave it off.
Yes. However, after wheel cruise with auto-hscroll-mode nil, I want
to start editing.
Sooner or later I want to use C-a to go outside of current scope.
This is the timing when I want to set auto-hscroll-mode nil. An event
from me should do it. The event must be some events besides
<wheel-up>, <wheel-down>, <wheel-right>, or <wheel-left>, and can be
C-a or <down-mouse-1>.
My picture is having a minor mode with keymap <down-mouse-1>
configured to set auto-hscroll-mode t.
next prev parent reply other threads:[~2017-04-26 23:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 1:27 bug#26599: patch for mwheel.el Tak Kunihiro
2017-04-22 7:52 ` Eli Zaretskii
2017-04-23 6:13 ` Tak Kunihiro
2017-04-26 5:01 ` Eli Zaretskii
2017-04-26 6:08 ` Tak Kunihiro
2017-04-26 10:50 ` Eli Zaretskii
2017-04-26 12:32 ` Tak Kunihiro
2017-04-26 15:31 ` Eli Zaretskii
2017-04-26 23:33 ` Tak Kunihiro [this message]
2017-04-27 2:36 ` Eli Zaretskii
2017-04-27 5:27 ` Tak Kunihiro
2017-04-27 14:25 ` Eli Zaretskii
2017-04-27 23:16 ` Tak Kunihiro
2017-04-28 6:47 ` Eli Zaretskii
2017-04-28 9:12 ` Tak Kunihiro
2017-05-19 8:55 ` Eli Zaretskii
2019-06-24 16:38 ` Lars Ingebrigtsen
2020-01-20 20:06 ` Stefan Kangas
2020-01-20 22:47 ` Juri Linkov
2020-01-21 7:17 ` Tak Kunihiro
2020-01-21 9:46 ` Stefan Kangas
2020-01-22 5:46 ` Tak Kunihiro
2020-03-13 23:43 ` Tak Kunihiro
2020-03-13 23:52 ` Tak Kunihiro
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=20170427.083356.368391024.tkk@misasa.okayama-u.ac.jp \
--to=tkk@misasa.okayama-u.ac.jp \
--cc=26599@debbugs.gnu.org \
--cc=eliz@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).