public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: mintty window border?
Date: Fri, 25 Aug 2023 14:08:01 -0700	[thread overview]
Message-ID: <20230825210801.GC2657@phoenix> (raw)
In-Reply-To: <adc45bcf-5ca2-42a0-8a96-781fd9539594@jhmg.net>

On 2023-08-25, Jim Garrison via Cygwin wrote:
> On 8/25/2023 00:18, Backwoods BC via Cygwin wrote:
> [snip]
> >
> >I get borders around both active and inactive windows, but then I've
> >spent hours (probably days) messing with registry values in an attempt
> >to gain the kind of UI control that was built into XP. I don't know
> >which change I made that gave me borders, but it is possible.
> >
> [snip]
> 
> In my setup (plain Win11 without registry hacks) the border is
> highlighted on the focused window, and other windows have a much
> fainter border, just enough to be visible when you have multiple
> overlapping minttys with black background.  Not sure if this was
> the case on Win10 as well.

I see that now on my Windows 10 machine.  I don't know why I didn't
notice it before.  Perhaps the accent color was too dark.  I changed
the accent color to white, which doesn't seem to interfere with my
color scheme, and paid more attention to overlapping mintty and gvim
windows (which have black backgrounds), and as you say, it's faint
but there.

Regards,
Gary


  reply	other threads:[~2023-08-25 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 18:07 Jim Garrison
2023-08-24 22:58 ` Backwoods BC
2023-08-25  0:41   ` Gary Johnson
2023-08-25  1:20     ` Thomas Wolff
2023-08-25  6:52       ` Gary Johnson
2023-08-25  7:18         ` Backwoods BC
2023-08-25  7:33           ` Sam Edge
2023-08-25 18:26           ` Jim Garrison
2023-08-25 21:08             ` Gary Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-25 21:49 Jim Garrison
2021-04-25 23:07 ` Thomas Wolff
2021-04-26  0:15 ` Mark Geisert
2021-04-26 18:37   ` Jim Garrison

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230825210801.GC2657@phoenix \
    --to=garyjohn@spocom.com \
    --cc=cygwin@cygwin.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.
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).