From: Juri Linkov <juri@linkov.net>
To: "João Guerra" <joca.bt@gmail.com>
Cc: 39649@debbugs.gnu.org
Subject: bug#39649: 27.0.60; tab-line doesn't scroll
Date: Wed, 19 Feb 2020 00:39:09 +0200 [thread overview]
Message-ID: <87imk3a5sa.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAGiBfP1FsFd3ppnrWoJH2+3ga4PmR+kZohkV2k6+2a6YmFU8nw@mail.gmail.com> ("João Guerra"'s message of "Tue, 18 Feb 2020 21:27:22 +0100")
> Seems to fix the issue in a specific situation, viz. after I select a
> tab manually with the mouse. However, when selecting a buffer that is
> already visible in the tab-line the tab-line still might get scrolled
> or if I just scroll the tab-line and change to a non-visible buffer
> the tab-line doesn't get scrolled. I'm a bit interested in knowing the
> reasoning to not always scroll the tab-line.
While you're manually scrolling the tab-line using the mouse wheel
or clicking on arrow buttons, auto-scrolling should be disabled
because it should not bring the current tab back into view immediately
on every step of manual scrolling. Just imagine that you clicked
on the arrow button to scroll, but it has no effect because auto-scrolling
immediately moved the tab-line back to its original state.
This is why auto-scrolling should be disabled during manual scrolling.
Now the question: how to detect the moment when you stop manually
scrolling? How would you indicate that manual scrolling is finished,
and it's time to enable auto-scrolling to bring the currently selected tab
back into view? I have no idea.
next prev parent reply other threads:[~2020-02-18 22:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 18:51 bug#39649: 27.0.60; tab-line doesn't scroll João Guerra
2020-02-17 23:03 ` Juri Linkov
2020-02-18 20:27 ` João Guerra
2020-02-18 22:39 ` Juri Linkov [this message]
2020-02-19 0:24 ` Juri Linkov
2020-02-19 20:57 ` João Guerra
2020-02-20 23:07 ` Juri Linkov
2020-02-21 1:34 ` Noam Postavsky
2020-02-22 23:52 ` Juri Linkov
2020-02-23 10:35 ` João Guerra
2020-02-23 23:06 ` Juri Linkov
2020-02-24 19:11 ` João Guerra
2020-02-25 21:20 ` Juri Linkov
2020-02-25 21:49 ` João Guerra
2020-02-26 23:16 ` Juri Linkov
2020-02-26 23:33 ` Juri Linkov
2020-02-28 9:12 ` Eli Zaretskii
2020-02-29 21:44 ` Juri Linkov
2020-03-01 16:12 ` Eli Zaretskii
2020-03-01 23:40 ` Juri Linkov
2020-09-20 8:40 ` Lars Ingebrigtsen
2020-02-27 21:13 ` João Guerra
2020-02-27 22:37 ` Juri Linkov
2020-02-28 18:30 ` João Guerra
2020-02-29 21:49 ` Juri Linkov
2020-03-04 17:25 ` João Guerra
2020-03-04 23:52 ` Juri Linkov
2020-03-05 8:04 ` João Guerra
2020-03-05 23:53 ` Juri Linkov
2020-09-20 8:41 ` Lars Ingebrigtsen
2020-10-14 6:16 ` Lars Ingebrigtsen
2020-02-28 13:16 ` Eli Zaretskii
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=87imk3a5sa.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=39649@debbugs.gnu.org \
--cc=joca.bt@gmail.com \
/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).