From: Duncan Roe <duncan_roe@optusnet.com.au>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: Failed assertion dialog box ATTN: Takashi Yano
Date: Fri, 20 Nov 2020 13:04:52 +1100 [thread overview]
Message-ID: <20201120020452.GA7078@dimstar.local.net> (raw)
In-Reply-To: <20201120091929.55e86d995ae3edf925f1fd7a@nifty.ne.jp>
On Fri, Nov 20, 2020 at 09:19:29AM +0900, cygwin wrote:
> Hi all,
>
> On Fri, 20 Nov 2020 11:06:58 +1100
> Duncan Roe wrote:
> > On Thu, Nov 19, 2020 at 07:30:20PM +0100, Thomas Wolff wrote:
> > >
> > > It does not seem to happen in xterm which is weird.
> >
> > It happens in an xterm for me.
> > xterm is /dev/pty1 and mintty is /dev/pty0. They both do it.
> > So I think it has to be pseudo-console.
> > (xterm has DISPLAY set to a Linux system but that shouldn't matter should it?)
>
> Could you please try latest cygwin snapshot?
>
> --
> Takashi Yano <takashi.yano@nifty.ne.jp>
Tried 20200909 - no popup
Cheers ... Duncan.
next prev parent reply other threads:[~2020-11-20 2:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 17:27 Failed assertion dialog box William M. (Mike) Miller
2020-11-14 3:45 ` Duncan Roe
2020-11-14 4:21 ` William M. (Mike) Miller
2020-11-14 4:37 ` André Bleau
2020-11-14 5:37 ` Lemures Lemniscati
2020-11-14 14:12 ` William M. (Mike) Miller
2020-11-14 15:24 ` Lemures Lemniscati
2020-11-14 15:53 ` William M. (Mike) Miller
2020-11-15 4:46 ` Duncan Roe
2020-11-15 13:12 ` William M. (Mike) Miller
2020-11-15 20:04 ` André Bleau
2020-11-15 20:39 ` André Bleau
2020-11-15 20:59 ` William M. (Mike) Miller
2020-11-19 14:21 ` Failed assertion dialog box ATTN: Takashi Yano André Bleau
2020-11-19 18:30 ` Thomas Wolff
2020-11-19 21:53 ` André Bleau
2020-11-20 0:06 ` Duncan Roe
2020-11-20 0:19 ` Takashi Yano
2020-11-20 1:40 ` Duncan Roe
2020-11-20 2:04 ` Duncan Roe [this message]
2020-11-20 7:09 ` Thomas Wolff
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=20201120020452.GA7078@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).