X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 91744396EC89
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=pdinc.us
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jpyeron AT pdinc DOT us
DKIM-Filter: OpenDKIM Filter v2.11.0 mail1.pdinc.us 107EdM7B030204
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pdinc.us; s=default;
 t=1610030362; bh=jnQAhwybLZQMMvvU6aCqKPTZkV3bTKyD6ujBfgd3vws=;
 h=From:To:References:In-Reply-To:Subject:Date:From;
 b=aubUCWo2VUqB7PlTlczJzFabCZmuXx70TEpBXz1pxlCf/mB2u8y8fPgWE9LbLEUN7
 4lRMoyje0ZaUCXWwT5aXrPS5SLWuvhq4DyA4UQTl3uZtGH1ZbONzrDHxJoukKhJ9AE
 HhvMAKscrTI9MGOm+LNJRgqOhzmDI0ETy8UOYDjWbb25Nj+dP6K7XMIOUt0MQ9fOpc
 NbvU5EcqbAbixNhFT3+xTwiEr7b/nRZ17Aw9kriakS89b9lEMQp4uk3QUgGvMtMJgh
 WL5OFMi7e1XctP0qAEi4NwsktlExTd/qVLIXW1twy2k05sAc+pZdx3T2UnXn0BB26j
 W8YnXNfVyP5rw==
From: "Jason Pyeron" <jpyeron AT pdinc DOT us>
To: <cygwin AT cygwin DOT com>
References: <CAPjM6w-mPf5h=xR2MK-cu-Eb7g313A3cZBcOuQ=ygTL2_dOmFw AT mail DOT gmail DOT com>
 <20201229223820 DOT 7a010585bbfd0973faf618ae AT nifty DOT ne DOT jp>
 <c8ad9cbf914e4594bc8ba9c15e61e882 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
 <20210106103602 DOT 75dae17f4921bd624e09683a AT nifty DOT ne DOT jp>
 <20210106185206 DOT 25036de8b4aa93cc19af6dd0 AT nifty DOT ne DOT jp>
 <77c04a8932e54806900cb88c6169c7da AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
 <20210107180502 DOT 28f1939a4309cb8c4a1d92a4 AT nifty DOT ne DOT jp>
 <76b224dfb8444d2a94e30a1762356001 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
In-Reply-To: <76b224dfb8444d2a94e30a1762356001@BELBRU-EXMP101.eeas.europa.eu>
Subject: RE: [cygwin] RE: cygwin introduces spaces in the console output when
 running a maven build for a java project in windows 10
Date: Thu, 7 Jan 2021 09:39:32 -0500
Message-ID: <021001d6e502$e9d9f900$bd8deb00$@pdinc.us>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQHnYVHroTOKJGzqZS927dQtZ20pswK3zPnXAesuDowCREbgpgLnoxH2AYHXGXkCGSe55AHguLmUqYDe5uA=
Content-Language: en-us
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_INFOUSMEBIZ, KAM_NUMSUBJECT,
 SPF_HELO_PASS, 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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

> -----Original Message-----
> From: KAVALAGIOS Panagiotis (EEAS-EXT)
> Sent: Thursday, January 7, 2021 4:40 AM
> 
> > -----Original Message-----
> > From: Cygwin <cygwin-bounces AT cygwin DOT com> On Behalf Of Takashi Yano via
> > Cygwin
> > Sent: 07 January 2021 10:05
> >
> > On Thu, 7 Jan 2021 08:38:42 +0000
> > "KAVALAGIOS Panagiotis (EEAS-EXT)" wrote:
> > >
> > > We also speak 1809 and the snapshot is not working for us either.
> > >
> > > I was thinking that the 3rd solution (TERM=cygwin) is easier. It can be
> > applied in a .sh and .csh script inside /etc/profile.d or is there a different
> > place recommended for Cygwin to set this variable? Is there any side effect
> > using "cygwin" from the default value "xterm"?
> >
> > Environment TERM is used by various cygwin application. So if you set it
> > cygwin globally, editor (vim, emacs), less etc. will be affected. Therefore, you
> > should set TERM to cygwin only for maven.
> >
> > The appropriate way is to set TERM=cygwin in /etc/mavenrc or
> > $HOME/.mavenrc

Our maven builds invoke Cygwin sub processes, this impacts them.

> 
> Yep, I confirm that the following has worked like a charm:
> 
> ------------
> kavalpa AT BELBRU-L1903700:[53] ~ > cat /etc/mavenrc
> # Temporary workaround for the jansi issue of Maven
> TERM=cygwin
> ------------

Instead (vice our previous mention of patching maven) adding the "unset PWD" in the mavenrc file also works, well.

I am still curious as to what is the reason that unsetting PWD or setting TERM=cygwin fixes this.

--
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