unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Scroll bars on macOS builds
Date: Sun, 23 Jan 2022 10:06:08 +1100	[thread overview]
Message-ID: <87tudvtlh9.fsf@gmail.com> (raw)
In-Reply-To: <835707023.1539255.1642863979389@mail1.libero.it>


Angelo Graziosi <angelo.g0@libero.it> writes:

>> Il 22/01/2022 12:33 Alan Third <alan@idiocy.org> ha scritto:
>> 
>>  
>> On Wed, Jan 12, 2022 at 01:12:05AM +0100, Angelo Graziosi wrote:
>> > 
>> > > Il 04/01/2022 12:08 Alan Third ha scritto:
>> > > 
>> > > Do the scrollbars work if you click where they should be?
>> > > 
>> > 
>> > It looks as if they are hidden, at least for what would be the vertical scroll bar...
>> > 
>> > > Can you try loading a theme with a dark background (wombat, for
>> > > example)? They might be displaying as white on white. I don't think
>> > > they should do that themselves, but I have seen that sort of thing
>> > > before.
>> > 
>> > No, I tried wombat all the other themes.
>> 
>> It sounds like either they're not being drawn at all, or they're being
>> drawn in the wrong place (outside the frame bounds). I have no
>> immediate ideas why either should happen.
>> 
>> Are you comfortable using a debugger? 
>
> No, I am afraid..
>
> All I can say is that the frame is drawn as if they are there.
>
> When I visit a buffer with many lines and long wrapped lines, holding mouse-1
> pressed and dragging where they should be, the result is as if they are there.
> For example, long wrapped lines become not wrapped exactly as on Windows build
> where scroll bars are visible...

Could this be due to a macOS setting? I know that macOS has a couple of
options relating to when scroll bars become visible, including one where
they are hidden until you start to scroll. 



  reply	other threads:[~2022-01-22 23:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 21:58 Scroll bars on macOS builds Angelo Graziosi
2022-01-02 14:20 ` Alan Third
2022-01-02 18:41   ` Angelo Graziosi
2022-01-04 11:08     ` Alan Third
2022-01-04 14:29       ` Angelo Graziosi
2022-01-12  0:12       ` Angelo Graziosi
2022-01-22 11:33         ` Alan Third
2022-01-22 15:06           ` Angelo Graziosi
2022-01-22 23:06             ` Tim Cross [this message]
2022-01-23 20:11               ` Alan Third
2022-01-23 20:06             ` Alan Third
2022-01-23 21:31               ` Angelo Graziosi
2022-01-23 22:23                 ` Angelo Graziosi
2022-01-25 23:01                   ` Alan Third
2022-01-26 17:07                     ` Angelo Graziosi
2022-01-26 22:31                       ` Alan Third
2022-01-27 19:59                       ` Alan Third
2022-01-27 22:10                         ` Angelo Graziosi
2022-01-29 15:43                           ` Angelo Graziosi
2022-01-30  4:19                             ` Richard Stallman
2022-01-30 22:08                               ` Angelo Graziosi
2022-01-30 12:37                             ` Alan Third
2022-01-30 21:57                               ` Angelo Graziosi
2022-02-03 13:47                               ` Angelo Graziosi
2022-02-03 16:39                                 ` Angelo Graziosi
2022-01-30 12:50                             ` Po Lu
2022-01-30 22:03                               ` Angelo Graziosi
2022-01-27 14:44                     ` Angelo Graziosi
2022-01-27 17:18                     ` Angelo Graziosi
2022-01-22 23:10           ` Brahimi Saifullah

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=87tudvtlh9.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-devel@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).