From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16475@debbugs.gnu.org, esq@lawlist.com
Subject: bug#16475: enhancement request: remove vertical scroll bar automatically when not needed
Date: Fri, 27 Oct 2017 10:25:54 +0200 [thread overview]
Message-ID: <59F2ED92.70702@gmx.at> (raw)
In-Reply-To: <8360b199yx.fsf@gnu.org>
>> Obviously, an equivalent of ‘set-window-scroll-bars’ would have to be
>> used here.
>
> I agree, but then the right place to call this is not from redisplay,
> but from keyboard.c, before it calls read_char (which calls
> redisplay). set-window-scroll-bars triggers a redisplay cycle, so
> calling it from (the end of) redisplay is not very wise, IMO.
It's ecologically questionable in any case: After every change affecting
the buffer (insertion/deletion, overlays, visibility) we'd have to check
whether its text still fits into its window(s) and then either add or
remove the scroll bar(s). And note that we may scroll lines out of view
(and thus implicitly should show a vertical scroll bar) even when the
text would entirely fit into its window.
martin
next prev parent reply other threads:[~2017-10-27 8:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 4:42 bug#16475: 24.3.50; enhancement request: remove vertical scroll bar automatically when not needed Drew Adams
2014-01-17 14:35 ` Stefan Monnier
2016-02-12 2:46 ` Keith David Bershatsky
2017-10-25 5:27 ` bug#16475: " Keith David Bershatsky
2017-10-25 7:47 ` martin rudalics
2017-10-25 14:40 ` Eli Zaretskii
2017-10-26 7:56 ` martin rudalics
2017-10-26 15:59 ` Eli Zaretskii
2017-10-27 8:25 ` martin rudalics [this message]
2017-10-27 2:44 ` Richard Stallman
2017-10-25 22:25 ` Keith David Bershatsky
2017-10-26 16:30 ` Eli Zaretskii
2017-10-26 16:03 ` Keith David Bershatsky
2017-10-26 17:07 ` Eli Zaretskii
2017-10-27 8:26 ` 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=59F2ED92.70702@gmx.at \
--to=rudalics@gmx.at \
--cc=16475@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=esq@lawlist.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 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.