public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Jacek Caban <jacek@codeweavers.com>
Cc: jcb62281@gmail.com, Eric Pouech <eric.pouech@orange.fr>,
	fortran@gcc.gnu.org,  DejaGnu mailing list <dejagnu@gnu.org>
Subject: Re: testsuite under wine
Date: Sun, 8 Jan 2023 01:47:31 -0500	[thread overview]
Message-ID: <CAF1jjLv_Bp=qU1Z5TmdKvdnZeNgJvHdvq_HKKr4Zhc4x3iYJmQ@mail.gmail.com> (raw)
In-Reply-To: <d794f0da-5b8f-7189-53c3-4545f4ef7380@codeweavers.com>

On Fri, Jan 6, 2023 at 8:46 PM Jacek Caban <jacek@codeweavers.com> wrote:

> As I said, compatibility with other terminals could be improved, but
> curses does not fit the role. Anyway, for sake of testing, the attached
> patch disables escapes hiding the cursor during screen updates which
> seem the most problematic. With this patch, some tests may work without
> disabling conhost (but other discussed problems are expected).

I can confirm that with this patch, the "^[[?25l" sequences are gone
and ^M^M still remains.  So at least this is a less intrusive version
of the first patch that can hopefully be easily upstreamed.

  parent reply	other threads:[~2023-01-08  6:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  2:20 NightStrike
2022-12-16  6:44 ` Thomas Koenig
2022-12-17  0:26   ` NightStrike
2022-12-17 10:52     ` Thomas Koenig
2022-12-17 23:24       ` NightStrike
2022-12-18  3:44         ` Jacob Bachmeyer
2022-12-18 21:13           ` NightStrike
2022-12-19  4:29             ` Jacob Bachmeyer
2022-12-19 10:43               ` Torbjorn SVENSSON
2022-12-19 11:00                 ` NightStrike
2022-12-19 11:13               ` NightStrike
2022-12-20  3:51                 ` Jacob Bachmeyer
2022-12-21 17:37               ` Jacek Caban
2022-12-22  1:01                 ` NightStrike
2022-12-22  4:37                   ` Jacob Bachmeyer
2022-12-23 10:36                     ` NightStrike
2022-12-23 12:43                       ` Eric Pouech
2022-12-24  4:00                       ` Jacob Bachmeyer
2022-12-24 11:05                         ` Mark Wielaard
2023-01-05  2:50                         ` NightStrike
2023-01-06  3:33                           ` Jacob Bachmeyer
2023-01-06  3:44                             ` Jerry D
2023-01-08  7:12                             ` NightStrike
2023-01-11  2:30                               ` Jacob Bachmeyer
2023-01-11  9:33                                 ` NightStrike
2023-01-12  4:11                                   ` Jacob Bachmeyer
2023-01-06  3:41                           ` Jerry D
2022-12-22  4:16                 ` Jacob Bachmeyer
2022-12-22  8:40                   ` Eric Pouech
2022-12-23  3:51                     ` Jacob Bachmeyer
2022-12-23 23:32                       ` Jacek Caban
2022-12-24  5:33                         ` Jacob Bachmeyer
2023-01-07  1:45                           ` Jacek Caban
2023-01-07  3:58                             ` Jacob Bachmeyer
2023-01-09 16:03                               ` Jacek Caban
2023-01-10  9:19                                 ` NightStrike
2023-01-11  9:10                                   ` NightStrike
2023-01-11 18:41                                   ` NightStrike
2023-01-14 23:36                                     ` NightStrike
2023-01-11  2:44                                 ` Jacob Bachmeyer
2023-01-08  6:47                             ` NightStrike [this message]
2023-01-04 15:21                       ` Pedro Alves
2023-01-04 15:45                         ` Eric Pouech
2023-01-04 15:52                           ` Pedro Alves

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='CAF1jjLv_Bp=qU1Z5TmdKvdnZeNgJvHdvq_HKKr4Zhc4x3iYJmQ@mail.gmail.com' \
    --to=nightstrike@gmail.com \
    --cc=dejagnu@gnu.org \
    --cc=eric.pouech@orange.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=jacek@codeweavers.com \
    --cc=jcb62281@gmail.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).