ConEmuC: Root process was alive less than 10 sec, ExitCode=0.

[kayzzen01]

I was using the cmder with bash and closed with using control + D after about 3 seconds, then the following displayed the following message:

ConEmuC: Root process was alive less than 10 sec, ExitCode = 0.

Would you like to know if this is a bug or just a message ?
Can you corrupt something in the cmder or ConEmu?

cmder version 1.3.5
ConEmu version 180206

Thanks.

[TeamSpen210]

This is a convenience feature. If you run a process and it quits before 10 seconds are up, ConEmum keeps the tab open until you press a key. That ensures if you run some program that ends quickly, you can still see the messages it produces. You can change this to be always/never/10 seconds only in the settings.

[Maximus5]

You may suppress this with -new_console:n.

I can't say if it's a bug because:

• You are using Old Builds
• Windows version is missed
• How do you run bash is not described

[kayzzen01]

@TeamSpen210 So it's a feature. Thank you for the explanation.

@Maximus5 What @TeamSpen210 explained to me is not a bug. Thanks for listening.

[Maximus5]

ConEmu uses some AI to disable confirmation before 10sec. That's why I asked for details.

[kayzzen01]

@Maximus5

Follow the information you requested

• You are using Old Builds
  No, I`m using version 180206

• Windows version is missed
  Windows 10 1803 build 17134.48

• How do you run bash is not described
  Open cmder, Control + T, Startup Command option bash:bash and start button
  I waited for about 3 seconds and closed with Control + D

Sorry my English

[Maximus5]

180206 is definitely old build. Actual is 180506.

Content of the task matters.

[ghost]

@TeamSpen210
This is a convenience feature. If you run a process and it quits before 10 seconds are up, ConEmum keeps the tab open until you press a key. That ensures if you run some program that ends quickly, you can still see the messages it produces. You can change this to be always/never/10 seconds only in the settings.

Are you referring to Settings > Integration > Default Term > Confirm close (Press Enter or Esc to close console): [Automatic/Always/Never] ?

[Maximus5]

This feature is intended ONLY for DefTerm as page name says

[raffaem]

I would like to run the Anaconda environment when ConEmu starts. In order to do so I created a new task, put

[MY_ANACONDA3_DIR]\Scripts\activate.bat [MY_ANACONDA3_DIR]

inside it and set the task as the default at startup, but I keep getting this error message

ConEmuC: Root process was alive less than 10 sec, ExitCode = 0.

How can I achieve my purpose?

[UfoAkaJuggalo]

I just have this issue a moment ago. And yes, I downloaded the latest version of Cmder.
Go to Settings --> Integration --> ComSpec and in the bottom section click the clear button and then click Register ConEmu autorun. Save settings and restart Cmder. Should work.

[IvanPrzOl]

@UfoAkaJuggalo I don't know why this happened but it works, thanks

[jkingpin-zz]

This is a convenience feature. If you run a process and it quits before 10 seconds are up, ConEmum keeps the tab open until you press a key. That ensures if you run some program that ends quickly, you can still see the messages it produces. You can change this to be always/never/10 seconds only in the settings.

Where in the settings can you specify the /never or /10 secs?

[nmz787]

I'm also failing to get miniconda to open and stay open in conemu using a shortcut like this "C:\Program Files\ConEmu\ConEmu64.exe" "-Reuse" "/cmd" "C:\Users\myUserName\Miniconda3\Scripts\activate.bat"

[nmz787]

I got it to "work" with this command, but it seems like opening cmd.exe is overkill, no? "C:\Program Files\ConEmu\ConEmu64.exe" "-Reuse" "/cmd" "cmd.exe /k" "C:\Users\myUserName\Miniconda3\Scripts\activate.bat"