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