From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 34569@debbugs.gnu.org
Subject: bug#34569: 26.1.90; Zero wide scroll bars
Date: Sat, 23 Feb 2019 11:51:17 +0200 [thread overview]
Message-ID: <83sgweq1d6.fsf@gnu.org> (raw)
In-Reply-To: <5C6BC77F.6020104@gmx.at> (message from martin rudalics on Tue, 19 Feb 2019 10:08:15 +0100)
> Date: Tue, 19 Feb 2019 10:08:15 +0100
> From: martin rudalics <rudalics@gmx.at>
>
> Setting 'scroll-bar-width' to zero can have unforeseen consequences
> depending on the toolkit used.
Why would users set 'scroll-bar-width' to zero, instead of turning off
scroll-bar-mode? Or are you saying that turning off scroll-bar-mode
also produces the same bugs?
If turning off scroll-bar-mode does work, then how about disabling the
direct setting of 'scroll-bar-width', either silently or noisily?
> /* Width that a scroll bar in frame F should have, if there is one.
> Measured in pixels.
> If scroll bars are turned off, this is still nonzero. */
> #define FRAME_CONFIG_SCROLL_BAR_WIDTH(f) ((f)->config_scroll_bar_width)
>
> This comment is, unfortunately, wrong
But the comment says "disabled", not "width set to zero". is it
correct when scroll-bar-mode is turned off? If so, perhaps just
qualifying the comment by the method by which the scroll bars are
disabled will be good enough?
> Note also that with emacs 27.1 the bug can be produced more directly by
> including
>
> (setq default-frame-alist '((vertical-scroll-bars . nil) (scroll-bar-width . 0)))
>
> in the early-init.el and then enabling vertical scroll bars. The
> indirection via 'frame-notice-user-settings' is not needed there.
If we disallow setting this parameter directly, or at least setting it
to zero, this problem will also go away, right?
Thanks.
next prev parent reply other threads:[~2019-02-23 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:08 bug#34569: 26.1.90; Zero wide scroll bars martin rudalics
2019-02-23 9:51 ` Eli Zaretskii [this message]
2019-02-23 14:01 ` martin rudalics
2019-02-23 16:49 ` Eli Zaretskii
2019-02-24 8:43 ` martin rudalics
2019-02-24 16:09 ` Eli Zaretskii
2019-02-24 18:31 ` martin rudalics
2019-02-24 19:04 ` Eli Zaretskii
2019-02-25 10:13 ` martin rudalics
2019-02-26 16:07 ` Eli Zaretskii
2019-03-04 10:14 ` 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
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=83sgweq1d6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34569@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).