cmder: Can't type backslash (clink issue)

From Sopor:

When i read that you had fixed the issue with backslash i started Cmder and updated it by running clink update.

After the update there was no message telling me that i should restart Cmder and therefore i thought i could continue and that the backslash now should work, but when tried to type backslash it didn’t worked.

I see. What’s a little unusual about Clink is that it doesn’t force you to close everything first (there are important technical reasons, as well as functional reason, but that gets into a long topic).

But when updating any software, you don’t get the results of the update in any instances that are already running. That’s universal in computing.

So, i closed the Cmder window and opened it again and now i could type the backslash.

You didn’t need to close Cmder. You could have opened a new tab. That’s part of what I mean about “nothing forces restarting Cmder”. You don’t have to restart ConEmu (the Cmder frame window). And you don’t need to restart cmd.exe tabs/windows/etc unless you absolutely need something in the update.

It would be misleading to say “you must restart all terminal hosts and integrated development environments and anything else that might be using cmd.exe”. I don’t want to get sucked into trying to explain all that context and what’s required and what isn’t, all in a one-sentence message added on to the existing output from clink update.

From daxgames:

Perhaps it might make sense for clink update to tell the user to restart all terminals.

That wouldn’t be accurate. Restarting terminals hosting bash or powershell or cmd-without-clink is unnecessary. Even restarting cmd.exe instances that do have clink installed isn’t “necessary” after updating – it’s only necessary if you want to immediately experience the updates.

Also, the more documentation is printed on every clink update, the more verbose and annoying it becomes.

What I Can Consider

I can consider adding more output from clink update to mention that the updates will take effect in new cmd.exe windows that are launched. Again, I’m concerned about printing too much text. As we all know, the more text is printed, the less likely any of it is to be read.