clink VS cmder

It would allow portable graphics applications on the terminal, e.g. this C64-emulator-in-Docker only renders ASCII characters, but could be extended with sixels to render graphics (I actually tinkered with this, but didn't get far because most terminals have either none or too slow sixels support):

https://github.com/chrisant996/clink/releases

If you don't want to learn the powershell commands then clink can enhance the existing cmd shell. It provides a lot of features i was used from bash/zsh: completion, history across sessions, colors, fzf integration and so on. Can be extended with lua.

Windows Terminal is great and an enormous improvement over conhost. That said, cmd itself isn't any better unless you extend it with something like Oh My Posh and clink. Add GNU CoreUtils to your path if (like me) your muscle memory is to use ls and rm over dir and del.

- windows terminal https://apps.microsoft.com/store/detail/windows-terminal/9N0DX20HK701 - al cmd lo mejoro con clink https://github.com/chrisant996/clink

Clink (https://github.com/chrisant996/clink) combines the native Windows shell cmd.exe with the powerful command line editing features of the GNU Readline library, which provides rich completion, history, and line-editing capabilities. Readline is best known for its use in the Unix shell Bash, the standard shell for Mac OS X and many Linux distributions.

clink injected into cmd.exe + msys for the utilities, all hosted in OpenConsole

Download the zip file for portable clink from the clink site We will only use clink in the custom Windows Terminal profile by manually extracting the portable clink to the Program Files folder. If you want to install clink to the normal CMD also, you can use the installer and omit the following steps until step 3.0

It has been around for some time however I just found it. It is called Clink . Anyone interested in a video tutorial

[Windows only]

I recently discovered Cmder:

https://cmder.app/

It's a portable console emulator and gives you the ability to "place your own executable files into the bin folder to be injected into your PATH" when it's run.

So far I've added:

jq

Assuming you already have Visual Studio Code installed, the first thing you'll want to do is Download Cmder. Extract the files to C:\cmder, or wherever you like.

I use cmder, it's great https://cmder.app/

The multiple supported shells remind me a little bit of the Windows cmder app, which I recall being pretty decent: https://cmder.app/

But the cross platform aspect is really nice, even if in my experience using different terminal apps per platform hasn't been too big of an issue.

Maybe except for MobaXTerm feeling better than most Linux tabbed/split terminal offerings due to its usability and support for sending input to multiple remote sessions at the same time, SSH integration etc.: https://mobaxterm.mobatek.net/ (something like Remmina is on par with mRemoteNG, so nice but not quite there)

I've since found that dev workflows in Windows work pretty damn good now, actually. I hate PowerShell so I still don't use it, but I now use Nushell, Cmder, and Git-Bash as my shells within the native Windows terminal emulator and it's actually pretty damn good and very close to the Unix experience. I actually like the native Windows terminal more than Kitty and would switch to it on my Ubuntu machine and my work MacBook if it were available on these systems.

If you haven't tried Cmder yet you definitely should.

The Second was to directly avoid powershell & cmd altogether .. i also used cmder which gave me a feeling of Linux on windows