From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 16475@debbugs.gnu.org
Subject: bug#16475: enhancement request: remove vertical scroll bar automatically when not needed
Date: Thu, 26 Oct 2017 19:30:17 +0300 [thread overview]
Message-ID: <83zi8d7tye.fsf@gnu.org> (raw)
In-Reply-To: <m2k1zic1az.wl%esq@lawlist.com> (message from Keith David Bershatsky on Wed, 25 Oct 2017 15:25:40 -0700)
> Date: Wed, 25 Oct 2017 15:25:40 -0700
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: 16475@debbugs.gnu.org
>
> Scroll bars are not immediately removed, however, when `window_contents_visible_p` is true and this-command is a keyboard stroke.
Most probably because some redisplay optimization bypasses your code.
> Any ideas on how to immediately remove scroll bars from the target window when `window_contents_visible_p` is true? [I have chosen the end of `redisplay_window` to perform the test because window start/end *should be* accurate at that location of the code.]
Like I said: I think the way this works will cause annoying visual
effects, so I propose to call set-window-scroll-bars from keyboard.c,
before we enter redisplay.
next prev parent reply other threads:[~2017-10-26 16:30 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
2017-10-27 2:44 ` Richard Stallman
2017-10-25 22:25 ` Keith David Bershatsky
2017-10-26 16:30 ` Eli Zaretskii [this message]
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=83zi8d7tye.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16475@debbugs.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.