unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34569@debbugs.gnu.org
Subject: bug#34569: 26.1.90; Zero wide scroll bars
Date: Mon, 25 Feb 2019 11:13:13 +0100	[thread overview]
Message-ID: <5C73BFB9.8010109@gmx.at> (raw)
In-Reply-To: <83d0nhnh3t.fsf@gnu.org>

 >> You didn't answer that question:
 >>
 >>   > Note that x_report_frame_params inserts the
 >>   > zero value automatically via
 >>   >
 >>   >   store_in_alist (alistptr, Qscroll_bar_width,
 >>   >           (! FRAME_HAS_VERTICAL_SCROLL_BARS (f)
 >>   >            ? make_fixnum (0)
 >>   >            : FRAME_CONFIG_SCROLL_BAR_WIDTH (f) > 0
 >>   >            ? make_fixnum (FRAME_CONFIG_SCROLL_BAR_WIDTH (f))
 >>   >            /* nil means "use default width"
 >>   >               for non-toolkit scroll bar.
 >>   >               ruler-mode.el depends on this.  */
 >>   >            : Qnil));
 >>   >
 >>   > What should we use instead?
 >
 > I thought I did.  Maybe I didn't understand what exactly you are
 > asking.

I wanted to know which value to assign when a frame does not have
vertical scroll bars.  We could try with

   store_in_alist (alistptr, Qscroll_bar_width,
		  (FRAME_CONFIG_SCROLL_BAR_WIDTH (f) > 0
		   ? make_fixnum (FRAME_CONFIG_SCROLL_BAR_WIDTH (f))
		   /* nil means "use default width"
		      for non-toolkit scroll bar.
		      ruler-mode.el depends on this.  */
		   : Qnil));

but I'm not sure whether that's what you meant.

martin





  reply	other threads:[~2019-02-25 10:13 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
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 [this message]
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=5C73BFB9.8010109@gmx.at \
    --to=rudalics@gmx.at \
    --cc=34569@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).