From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: mintty window border?
Date: Mon, 26 Apr 2021 11:37:18 -0700 [thread overview]
Message-ID: <18a9f44e-976f-e079-416e-2afee200efea@jhmg.net> (raw)
In-Reply-To: <ef3af5d5-c90b-5cf2-15f6-2ad07cbc3bf0@maxrnd.com>
On 4/25/2021 5:15 PM, Mark Geisert wrote:
> Jim Garrison via Cygwin wrote:
>> Mintty's window does not seem to have any border at the left and bottom.
>> The top of the window has the title menu bar and the right side is the
>> scroll bar. When I have multiple mintty windows open, and they overlap,
>> since there is no border, one window blends into another.
>>
>> I searched mintty's options and there doesn't seem to be a way to
>> specify a border. If the window background is a light color, there's
>> a subtle drop shadow that helps a bit, but with a dark style it's
>> impossible to distinguish the windows.
>>
>> Here's a sample:
>> https://drive.google.com/file/d/10zKWdie_nA-_hzsN8i_GeCw7VadJBmol/view?usp=sharing
>>
>>
>> Is there a way to make it draw a border?
>
> As Thomas pointed out, not mintty's fault. I ran into the same issue on
> first upgrade to Windows 10. Windows 7 allowed one to set window
> borders; Windows 8 and up don't. But one can adjust registry entries to
> fix the issue. Check here:
> https://www.thewindowsclub.com/change-desktop-windows-metrics-border-width-windows-8
>
> The fix outlined there works for Windows 10 too.
> HTH,
>
> ..mark
>
Perfect, that's exactly what I need. Thanks.
--
Jim Garrison
jhg@acm.org
next prev parent reply other threads:[~2021-04-26 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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=18a9f44e-976f-e079-416e-2afee200efea@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.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.
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).