Cmder: Cmder doesn't show lambda - just normal "prompt"

[gabriellima]

Hi there. Yesterday I first opened Cmder and everything was working.

After restarting the PC, I don't get that beautiful lambda sign anymore. It's just a "normal conemu prompt".

If it helps, I can't even use "keyboard shortcuts" like CTRL+L. Instead of clearing the log, it just inserts a ^L sign

[gabriellima]

I'm in corporate network right now.

Out of nowhere, I had an idea to try using my personal WIFI before starting Cmder. Turns out that was the issue.

But, could anybody explain why Cmder needs to have an "open internet connection" in order to open correctly?

It makes no sense to me.

After it opened as supposed to, I finished it and logged back to my corporate network, and after reopening it it came back to "default not funny cmd.exe" again.

What's going on here?

EDIT: After seeing the default cmd.exe and logged on corporate network, I clicked on "Settings" in order to check if there was any proxy issue. Without changing anything, I closed the "Settings" window and after some seconds the cmd.exe turned into "Cmder" default again, with the lambda sign.

Then I decided to make another test: Closed Cmder and reopened again. Lambda sign is being displayed correctly.

Does anybody have any clue on what may be happening?

[CollinChaffin]

Yep, @gabriellima see https://github.com/cmderdev/cmder/issues/2166

Remove the "--nolog" (assuming you upgraded to latest build) as I pointed out in that issue and restart cmder and your cmd prompts return to normal.

[gabriellima]

@CollinChaffin , thank you. I'm sorry, I'm running latest released version (v1.3.12.915) but can't seem to find any nolog statement on cmder\vendor\init.bat file.
I even downloaded a new zip file directly from github, in doubt that I may had already remove that statement, but couldn't find either.

Was it released?

Anyway, I think we can close this issue, at least for me, as I'm not seeing the issue anymore.

Thank you for all support.

[daxgames]

@gabriellima Cmder with clink --nolog has not been released. Also I can't explain tour original ossue and Cmder does not require a network connection.

[CollinChaffin]

Okay thanks @daxgames so obviously this is a one-off. I have myself had instances where opening cmder with many tasks that then focuses on the last task opened, where my first few are cmd.exe based where I'll get no prompt but it's been rare.

[gabriellima]

Gentlemen, I'm again with the referred issue. Didn't change anything, so there's something mysterious going on.

How may I share some log?

[daxgames]

@gabriellima you could Dd -d to the cmder task to print some debug statements on startup. You can also run cmder_diag and share the output. Please look at the data before you post it as it may contain sensitive data.

I doubt any of this will help though since as i said before cmder does not require any network connection.

[gabriellima]

@daxgames , thank you. I've uploaded cmder_d_output.txt (output of /d on cmder init), and cmder_diag_output (output of cmder_diag command).

Also, I've already tried closing and reopening cmder several times, without success on lambda sign. If it's of any help, shortcuts like CTRL+L doesn't do as expected (call the clear command), as if "shortcuts" could not be attached to console.

cmder_d_output.txt
cmder_diag_output.txt

[daxgames]

@gabriellima I see no obvious issues with your configuration but I can't explain the issues that you're having. I think there is something possibly on your system that is causing the problem but I don't believe it's cmder.

It is very difficult to diagnose an issue that you can't reproduce so unless you can for providee some steps to reproduce it I'm closing the issue. You can re open it when you can providethe steps.

[gabriellima]

dax, thank you. I'll keep investigating. It might have something to do with "Trend micro" AV, as everything in my corporate computer does.

[daxgames]

@gabriellima @CollinChaffin Try this