public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: mintty 3.6.4 status line problem
Date: Sun, 18 Jun 2023 23:03:05 +0200	[thread overview]
Message-ID: <95b88d8d-b506-62e4-eb1d-978abf96695c@towo.net> (raw)
In-Reply-To: <SA0PR19MB4205C2F91850C43987A686DBB55EA@SA0PR19MB4205.namprd19.prod.outlook.com>



Am 18.06.2023 um 22:00 schrieb Ross Boulet via Cygwin:
> I was looking at the settings for mintty and saw the new option (new as of 3.6.4 from March) for a status line. I decided to try it out. Sure enough, a status line appeared at the bottom. All was well until I tried to open a new mintty window and nothing seemed to happen. After a little research, I saw a stackdump was being generated. I had to get to the .minttyrc file and remove the StatusLine=yes to get it to work again. I tried the same scenario on another Windows 10 machine as well as a Windows 11 machine with the same results.
>
> To reproduce the problem, right click on the icon in the upper left corner of a mintty window and choose options. On the options dialog, choose terminal and check the option to turn on the status line. Then click save. The current window shows a status line but attempts to start a new window will fail and generate a stackdump.
This issue occurs if the monitor DPI is 96 (or 100% display scaling).
It was fixed in the repository already. Still working on some other 
issues before a release though.
Thomas

      reply	other threads:[~2023-06-18 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18 20:00 Ross Boulet
2023-06-18 21:03 ` Thomas Wolff [this message]

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=95b88d8d-b506-62e4-eb1d-978abf96695c@towo.net \
    --to=towo@towo.net \
    --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).