DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 91744396EC89
From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
References: <CAPjM6w-mPf5h=xR2MK-cu-Eb7g313A3cZBcOuQ=ygTL2_dOmFw@mail.gmail.com>
 <20201229223820.7a010585bbfd0973faf618ae@nifty.ne.jp>
 <c8ad9cbf914e4594bc8ba9c15e61e882@BELBRU-EXMP101.eeas.europa.eu>
 <20210106103602.75dae17f4921bd624e09683a@nifty.ne.jp>
 <20210106185206.25036de8b4aa93cc19af6dd0@nifty.ne.jp>
 <77c04a8932e54806900cb88c6169c7da@BELBRU-EXMP101.eeas.europa.eu>
 <20210107180502.28f1939a4309cb8c4a1d92a4@nifty.ne.jp>
 <76b224dfb8444d2a94e30a1762356001@BELBRU-EXMP101.eeas.europa.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
Thread-Index: AQHnYVHroTOKJGzqZS927dQtZ20pswK3zPnXAesuDowCREbgpgLnoxH2AYHXGXkCGSe55AHguLmUqYDe5uA=
Content-Language: en-us
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

> -----Original Message-----
> From: KAVALAGIOS Panagiotis (EEAS-EXT)
> Sent: Thursday, January 7, 2021 4:40 AM
> 
> > -----Original Message-----
> > From: Cygwin <cygwin-bounces@cygwin.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@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