unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 32882@debbugs.gnu.org
Subject: bug#32882: 27.0.50; thin border around emacs frame on macOS mojave
Date: Sun, 30 Sep 2018 09:54:01 +0100	[thread overview]
Message-ID: <20180930085401.GA87958@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2zhvz4g8f.fsf@gmail.com>

On Sun, Sep 30, 2018 at 12:05:52AM -0700, Aaron Jensen wrote:
> 
> emacs -Q
> M-x load-theme manoj-dark
> 
> See
> https://dzwonsemrish7.cloudfront.net/items/272S1013403W1e1i2W1Y/Image%202018-09-29%20at%2011.44.39%20PM.png
> 
> vs
> 
> https://cl.ly/115ddf656a41/Image%202018-09-30%20at%2012.04.17%20AM.png
> 
> Since upgrading to Mojave there is a thin border around the frame that
> was not there prior to Mojave if my memory serves. The border's color
> appears to be influenced by the theme, but I don't know how. Is there an
> option for this I don't know about or is this some unintentional change
> triggered by Mojave?

Hi Aaron,

My money is on this being related to Mojave’s new theming stuff. If
you look very closely at the second screenshot you’ll notice there is
actually a black border round the frame.

Are you using the dark theme in macOS?

Perhaps try changing ns-appearance to see if it affects the colours.

FWIW, I think we tell macOS what our background and foreground colours
are, but the colour there doesn’t seem to match either so I wonder if
it’s automatically choosing a colour that will show up against the
background. I take it this border doesn’t exist on non‐emacs windows?
-- 
Alan Third





  reply	other threads:[~2018-09-30  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30  7:05 bug#32882: 27.0.50; thin border around emacs frame on macOS mojave Aaron Jensen
2018-09-30  8:54 ` Alan Third [this message]
     [not found]   ` <CAHyO48yeE1NP7fTXgKw7k=y26YtzCn0HkW7iycksMk0UHErrFw@mail.gmail.com>
2018-09-30 18:16     ` Alan Third
2018-09-30 18:24       ` Aaron Jensen
2018-09-30 20:42         ` Aaron Jensen

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=20180930085401.GA87958@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=32882@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    /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).