From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Maximizing windows during "git log" locks mintty both in "Git for Windows" and cygwin 3.4.3
Date: Tue, 10 Jan 2023 19:40:57 +0000 [thread overview]
Message-ID: <20230110194057.xqrywdtiqwfsezg3@lucy.dinwoodie.org> (raw)
In-Reply-To: <CALas-ih810bhLeTKVvKqjP5Qy5i=mNZsexAqL05caXq7xHDreA@mail.gmail.com>
On Tue, Jan 10, 2023 at 04:50:26PM +0100, Francesco Pretto via Cygwin wrote:
> Hello,
>
> I want to report a bug in mintty that is mostly suffered by "Git for
> Windows" users, which in version 2.39.0.2 they are using mintty 3.6.1.
> The bug has been reported in this "Git for Windows" issue[1].
> Basically maximizing the mintty window during a "git log" session
> locks the tty session and the window must be quit/killed. I can
> reproduce within a vanilla cygwin mintty 3.6.3 session, which is
> present in the latest cygwin 3.4.3, using the same "Git for Windows"
> git binary. To reproduce;
>
> - Open a cygwin mintty window, keep it **default** size, don't maximize here;
> - Go to a git repository directory;
> - Enter "git log" (I'm using the git binary from "Git for Windows",
> location "/cygdrive/c/Program Files/Git/cmd/git";
> - Maximize the window;
> - Try to exit "git log" by pressing "q" -> lock!
I've tried this, as described, using both Cygwin's git and MinTTY, and
using the Git for Windows versions, and both work just fine for me.
However...
> There was some debate of who was supposed to report the issue to this
> ML. Please, ask for more details "Git for Windows" maintainers, if you
> need, either by contacting them here/privately or writing to their
> Github issue.
>
> Regards,
> Francesco Pretto
>
> [1] https://github.com/git-for-windows/git/issues/4060
...this is the same issue on GitHub as was reported at [0], however
in that email thread the problem occurred only when using the Windows
terminal emulators, calling git or less from within a PowerShell or cmd
window, *not* when using MinTTY. I believe that's fixed in an upcoming
Cygwin release, per [1], although I don't know when that release will
happen, or how long it will take downstream projects like Git for
Windows to pick it up.
[0]: https://cygwin.com/pipermail/cygwin/2022-December/252737.html
[1]: https://cygwin.com/pipermail/cygwin/2022-December/252745.html
I'll put a comment on the Git for Windows issue now, more-or-less
duplicating the above.
Adam
prev parent reply other threads:[~2023-01-10 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 15:50 Francesco Pretto
2023-01-10 17:02 ` Takashi Yano
2023-01-10 21:24 ` Francesco Pretto
2023-01-10 23:36 ` Takashi Yano
2023-01-10 19:40 ` Adam Dinwoodie [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=20230110194057.xqrywdtiqwfsezg3@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--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).