-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TerminalDetection not detecting IntelliJ #67
Comments
Until IntelliJ is consistent about setting an environment variable, it's probably not possible to detect it in all cases. If you know of any envvar etc. that we can use, I'm happy to add it. Does that |
For the record, in IntelliJ IDEA 2023.2 I'm getting colored output with Mordant in the |
I suspect it's not possible to detect terminal size in IntelliJ's run console. On Windows at least, GetConsoleScreenBufferInfo fails. Even powershell itself can't detect anything. |
I have a problem when I try to create a fat jar, no problem with IntellI console when I use a run.
It is a problem with JNA, you need to include it to execute as a jar No problem with 2.0.0-beta9 |
Maybe the whole issue will get resolved with https://blog.jetbrains.com/idea/2024/02/the-new-terminal-beta-is-now-in-jetbrains-ides/? |
on Unix like Systems it could work to see if the |
The TerminalDetection computes
AnsiLevel.NONE
although I'm running my unit testsinside of IntelliJ (Build #IU-221.6008.13, built on July 19, 2022).
The
runningInIdeaJavaAgent
method does not match.On my mac
ManagementFactory.getRuntimeMXBean()
returns the following elementsSystem.getProperty("sun.java.command")
reports "worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 61'"My environment reported by
System.getenv()
does neither containIDEA_INITIAL_DIRECTORY
,__INTELLIJ_COMMAND_HISTFILE__
norTERMINAL_EMULATOR
.The following environment properties might help you:
The text was updated successfully, but these errors were encountered: