From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: mintty window border?
Date: Thu, 24 Aug 2023 23:52:58 -0700 [thread overview]
Message-ID: <20230825065258.GB2657@phoenix> (raw)
In-Reply-To: <7d6b3a36-b1ce-6755-a97f-7cf52fd70ae0@towo.net>
On 2023-08-25, Thomas Wolff via Cygwin wrote:
>
>
> Am 25.08.2023 um 02:41 schrieb Gary Johnson via Cygwin:
> >On 2023-08-24, Backwoods BC via Cygwin wrote:
> >>On Thu, Aug 24, 2023 at 11:08 AM Jim Garrison via Cygwin
> >><cygwin@cygwin.com> wrote:
> >>>This is an update to a question I had a couple of years ago
> >>>https://cygwin.com/pipermail/cygwin/2021-April/248367.html
> >>>
> >>>Windows 11 now has an "accent color" option under
> >>>Settings/Personalization/Colors that adds a thin (1px?) border around
> >>>all windows, in a user-selectable color. This definitively eliminates
> >>>the problem seen with overlapping mintty windows that have a dark grey
> >>>or black background (where the shadow isn't visible).
> >>>
> >>>Just FYI
> >>>
> >>>--
> >>>Jim Garrison
> >>>jhg@acm.org
> >>This is also true for Windows 10, although I may have had to
> >>explicitly enable it (I don't remember).
> >It's in the same place on Windows 10. I just enabled it. Thank you both!
> But it adds the thin border only to the foreground window...
> Thomas
Yes, it's not as good as having a border around all windows all the
time, or around just mintty and gvim windows, but it is so much
better than nothing at all, or so it seems so far.
Regards,
Gary
next prev parent reply other threads:[~2023-08-25 5:53 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 [this message]
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
-- 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=20230825065258.GB2657@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).