From: Alan Third <alan@idiocy.org>
To: Angelo Graziosi <angelo.g0@libero.it>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Scroll bars on macOS builds
Date: Wed, 26 Jan 2022 22:31:10 +0000 [thread overview]
Message-ID: <YfHLriOlIi6oPz4d@idiocy.org> (raw)
In-Reply-To: <147533788.292331.1643216844580@mail1.libero.it>
I'm afraid all I can suggest for now is trying to find a commit that
worked and doing a git bisect to find the actual commit that causes
the problem, because I can't see anything obvious in the logs for last
month that would've caused it.
If it was broken since, like, the middle of the year I'd strongly
suspect the change to using the custom layer, but it seems likely it
was only in the last couple of months it's happened?
--
Alan Third
next prev parent reply other threads:[~2022-01-26 22:31 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
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 [this message]
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=YfHLriOlIi6oPz4d@idiocy.org \
--to=alan@idiocy.org \
--cc=angelo.g0@libero.it \
--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).