Indeed, perhaps a more nuanced fix might be applicable here. If you have an existing Jira account at the ASF, you should be able to create an issue after logging in. If you don't have an account, please follow the instructions here:
https://infra.apache.org/jira-guidelines.html#who It involves sending an email to priv...@groovy.apache.org with some details and we can get you set up. It's a pain but spam was becoming a problem when self-serve accounts were being used. See also some guidelines for creating PRs if you want to work on the fix: https://groovy.apache.org/#code Cheers, Paul. On Sat, Feb 18, 2023 at 10:32 AM Simon Sadedin <ssade...@gmail.com> wrote: > Hi all, > > I noticed after updating to Groovy 3.0 that some of my groovy applications > were misbehaving when I ran them inside a GNU screen session, but not > outside. I investigated a bit more and saw that when running on Linux, > startGroovy overrides the TERM variable and hard codes it to "linux" no > matter what terminal the user is actually using. Tracing this change back I > saw it was added in Groovy 3.0.8 as a response to a specific terminal issue > here: > > https://issues.apache.org/jira/browse/GROOVY-9875 > > However I think this logic isn't correct, as the terminal variable needs > to reflect the user's actual terminal software, not just the operating > system they are using. > > I'm not sure if there was more context to this change? But otherwise I > think it would be good to log a bug for this and see if we can have better > handling (I couldn't see how to log a bug myself on the ASF Jira page but > happy to if that's the right thing to do). > > Cheers / thanks! > > Simon >
