unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 18:49:55 +0200	[thread overview]
Message-ID: <83lg26phzg.fsf@gnu.org> (raw)
In-Reply-To: <5C715252.1060104@gmx.at> (message from martin rudalics on Sat, 23 Feb 2019 15:01:54 +0100)

> Date: Sat, 23 Feb 2019 15:01:54 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: 34569@debbugs.gnu.org
> 
>  > If turning off scroll-bar-mode does work, then how about disabling the
>  > direct setting of 'scroll-bar-width', either silently or noisily?
> 
> Setting 'scroll-bar-width' is fragile.  With GTK builds you can set
> it, Emacs will respect it and GTK will either overdraw or leave a gap
> because you can't change the GTK scroll bar from within Emacs.  Note
> the dual use of this parameter: 'scroll-bar-width' is (1) passed on to
> the toolkit to draw scroll bars of the desired width and (2) used by
> Emacs to clear various areas of the window and calculate the width of
> the text area.
> 
> But yes: One way to fix the aborts should be to disallow setting the
> 'scroll-bar-width' frame parameter to zero.

Then I think we should do that.

> This hints at another way of fixing the aborts: Handle zero wide
> scroll bars just as if scroll bars were disabled/turned off.

Yes.

>  > If we disallow setting this parameter directly, or at least setting it
>  > to zero, this problem will also go away, right?
> 
> Why would we disallow setting this parameter directly?  On Windows it
> works perfectly.  On Lucid and Motif all widths but zero work well.

I said "or at least setting it to zero".





  reply	other threads:[~2019-02-23 16:49 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
2019-02-23 14:01   ` martin rudalics
2019-02-23 16:49     ` Eli Zaretskii [this message]
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=83lg26phzg.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).