X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org AE88539540B5
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1602844222;
	bh=L82MfHUe1krzIlwCXif45WpEFzD4NiW6oLYTVD61yRw=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=Xi2YitzhQzi8f8Ez2ojdYnizDqwxBoJsF/8jksv9+SOfANy8SZJ3zv0G3+NtXdOIj
	a53CNl/1X/gjZ/mnnUpThHjcDeghLj/Efao21QL+7/tDQPd+7/e3ARgJgTNWcST2ax
	87GJd+d6IAmPDAzU56n94Iqf+8tA1ZgwCV2qizro=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 870723857817
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 09GATnFI016652
X-Nifty-SrcIP:	[124.155.38.192]
Date:	Fri, 16 Oct 2020 19:29:54 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: How to disable formatting control characters in newer versions?
Message-Id:	<20201016192954.d005914b140d2edd064eaf0c@nifty.ne.jp>
In-Reply-To:	<CAFaDXvpEBPetKY7f34brHrJt0ox0qu4D-uu44N1J--o0Y5qm-A@mail.gmail.com>
References:	<CAFaDXvpEBPetKY7f34brHrJt0ox0qu4D-uu44N1J--o0Y5qm-A AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A,
	RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Cc:	=?UTF-8?B?Wm9sdMOhbiBWw6ly?= <vzolko AT gmail DOT com>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 09GAUnfa015431

On Fri, 16 Oct 2020 12:07:11 +0200
Zoltán Vér via Cygwin <cygwin AT cygwin DOT com> wrote:

> Hi,
> 
> We have been using Cygwin for a long time for a testing process. This
> process saves the output to a log file.
> 
> The main problem is that the newer versions of Cygwin puts the formatting
> characters into the log file also. So the logs are useless.
> 
> The affected formatting characters are backspaces and cursor positioner CSI
> control characters like \033[1;1H
> It seems like the log contains the clear screen data too.
> 
> So, is there an option to disable this feature, or do you have any solution
> to eliminate them?

Could you provide simple test case which replicates your issue?

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -