From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-05.nifty.com (conssluserg-05.nifty.com [210.131.2.90]) by sourceware.org (Postfix) with ESMTPS id 870723857817 for ; Fri, 16 Oct 2020 10:30:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 870723857817 Received: from Express5800-S70 (v038192.dynamic.ppp.asahi-net.or.jp [124.155.38.192]) (authenticated) by conssluserg-05.nifty.com with ESMTP id 09GATnFI016652; Fri, 16 Oct 2020 19:29:49 +0900 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 From: Takashi Yano To: cygwin@cygwin.com Cc: =?UTF-8?B?Wm9sdMOhbiBWw6ly?= Subject: Re: How to disable formatting control characters in newer versions? Message-Id: <20201016192954.d005914b140d2edd064eaf0c@nifty.ne.jp> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2020 10:30:21 -0000 On Fri, 16 Oct 2020 12:07:11 +0200 Zoltán Vér via Cygwin 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