Based on the fact that this bug is completely ignored by the Intellij team and has been introduced just couple of month before the major release, I can only conclude that this has been done intentionally, please keep in mind that this annoys a lot of people and take 0 time to fix. Just the fact that the old exe file works fine with any build means that the old script to generate the file is good enough as well, so don’t expect this to be fixed before the final build.
I agree with your assessment, though it's hard to see what the point is. This and the misbegotten "productivity hints" (not to mention the inaction over focus-stealing, the failure to fix certain long-standing code mark-up errors) have left a bad taste in my mouth.
Vladimir Goncharov wrote:
Based on the fact that this bug is completely ignored by the Intellij team and has been introduced just couple of month before the major release, I can only conclude that this has been done intentionally, please keep in mind that this annoys a lot of people and take 0 time to fix. Just the fact that the old exe file works fine with any build means that the old script to generate the file is good enough as well, so don?t expect this to be fixed before the final build.
you can also use the idea.bat and change
"%JAVA_EXE%" %JVM_ARGS% -cp "%CLASS_PATH%" %MAIN_CLASS_NAME% %*
into
start %JAVA_EXE% %JVM_ARGS% -cp "%CLASS_PATH%" %MAIN_CLASS_NAME% %*
But wasn't supose to point in idea.lax the vars
lax.stderr.redirect=c:
tmp
Pallada.err
lax.stdin.redirect=c:
tmp
Pallada.in
lax.stdout.redirect=c:
tmp
Pallada.out
Like I paste here so the console shouldn't appear?
Is not what happens.
The Batch trick works... but...
Isn't preferred idea.exe works also with idea.lax configured acordly old IntelliJ versions?
Tnx!
Based on the fact that this bug is completely ignored by the Intellij team and has been introduced just couple of month before the major release, I can only conclude that this has been done intentionally, please keep in mind that this annoys a lot of people and take 0 time to fix. Just the fact that the old exe file works fine with any build means that the old script to generate the file is good enough as well, so don’t expect this to be fixed before the final build.
My 2 cents.
I agree with your assessment, though it's hard to see what the point is.
This and the misbegotten "productivity hints" (not to mention the
inaction over focus-stealing, the failure to fix certain long-standing
code mark-up errors) have left a bad taste in my mouth.
Vladimir Goncharov wrote: