4 ms·

Too bad windows cmd is so fantastically horrible. This looks like a good project though.

by awestroke 14y ago

manojlds 14y ago
Use Powershell and ConEmu
lucian1900 14y ago
Console2 + msys bash is bearable.
shocks 14y ago
Perhaps you will find this useful: https://code.google.com/p/clink/ https://code.google.com/p/clink/
- bliker 14y ago
  Great! Now I am using cmd + clink + console2. Very natural solution... I have found powershell to be slower/less responsive for some reason
  - seewhat 14y ago
    Any advice on how to make these 3 tools work together? I scanned the web and experimented today for approx 1 hour but didn't succeed. My general efforts were: (i) injecting clink into the Console2 process (ii) hosting the injected cmd process in Console2.
    - bliker 14y ago
      I actually did nothing special, I just installed clink as executable. Tested it in cmd.exe (you will get the message about running clink). Afterwards added a tab for cmd.exe in console2 and it worked. Whas seems to be a problem for you?
      - seewhat 14y ago
        Hi, thanks for the info. The initial difference is that I cannot use the installer due to Windows group policies associated with my account (the PC is not mine to administer). So I've downloaded and extracted the v0.3 zip archive. I manually start clink by running "install_dir\clink inject" in a cmd session and this procedure works correctly. Problems arise when running the same command in a cmd session in Console2. The Console2 process disappears (crashes?) after approx 1 sec, then 10s later the clink executable disappears. Strange behaviour and I may simply drop this and perhaps try again in future once the tool(s) have matured. I hadn't used either Console2 or clink before now; I can get by without them as I'm not a rabid user of the Windows command line. I'll likely casually experiment with them separately.
    - RobinBlk7 14y ago
      Try out ConEmu instead of Console2. It also has clink integration from the box.
  - shocks 14y ago
    Glad you like it! (My brother is the author. :])
smogzer 14y ago
I use pycmd -> http://sourceforge.net/projects/pycmd/ http://sourceforge.net/projects/pycmd/ Also tried console2, and zsh win32 variants i found.
- rplnt 14y ago
  It's better but not really great. I just don't understand why it has to run within the cmd environment, which is horrible. I use Git++'s shell as my go-to cmd in windows but that's about the same. Why can't it be a complete application that would emulate the "cdm" under the hood? So I can get the feel of a real (as in anything you install on linux) terminal application.
shortlived 14y ago
Try clink (search on google code), it brings bash to cmd.
ConstantineXVI 14y ago
PowerShell's a massive improvement, but the terminal itself hasn't changed in ages (barely any change since NT4/W95 if I had to guess). There's replacements, but you can't count on arbitrary servers having them installed.

Too bad windows cmd is so fantastically horrible. This looks like a good project though.

manojlds 14y ago

Use Powershell and ConEmu

lucian1900 14y ago

Console2 + msys bash is bearable.

shocks 14y ago

Perhaps you will find this useful: https://code.google.com/p/clink/ https://code.google.com/p/clink/

bliker 14y ago
Great! Now I am using cmd + clink + console2. Very natural solution... I have found powershell to be slower/less responsive for some reason
- seewhat 14y ago
  Any advice on how to make these 3 tools work together? I scanned the web and experimented today for approx 1 hour but didn't succeed. My general efforts were: (i) injecting clink into the Console2 process (ii) hosting the injected cmd process in Console2.
  - bliker 14y ago
    I actually did nothing special, I just installed clink as executable. Tested it in cmd.exe (you will get the message about running clink). Afterwards added a tab for cmd.exe in console2 and it worked. Whas seems to be a problem for you?
    - seewhat 14y ago
      Hi, thanks for the info. The initial difference is that I cannot use the installer due to Windows group policies associated with my account (the PC is not mine to administer). So I've downloaded and extracted the v0.3 zip archive. I manually start clink by running "install_dir\clink inject" in a cmd session and this procedure works correctly. Problems arise when running the same command in a cmd session in Console2. The Console2 process disappears (crashes?) after approx 1 sec, then 10s later the clink executable disappears. Strange behaviour and I may simply drop this and perhaps try again in future once the tool(s) have matured. I hadn't used either Console2 or clink before now; I can get by without them as I'm not a rabid user of the Windows command line. I'll likely casually experiment with them separately.
  - RobinBlk7 14y ago
    Try out ConEmu instead of Console2. It also has clink integration from the box.
- shocks 14y ago
  Glad you like it! (My brother is the author. :])

smogzer 14y ago

I use pycmd -> http://sourceforge.net/projects/pycmd/ http://sourceforge.net/projects/pycmd/ Also tried console2, and zsh win32 variants i found.

rplnt 14y ago
It's better but not really great. I just don't understand why it has to run within the cmd environment, which is horrible. I use Git++'s shell as my go-to cmd in windows but that's about the same. Why can't it be a complete application that would emulate the "cdm" under the hood? So I can get the feel of a real (as in anything you install on linux) terminal application.

shortlived 14y ago

Try clink (search on google code), it brings bash to cmd.

ConstantineXVI 14y ago

PowerShell's a massive improvement, but the terminal itself hasn't changed in ages (barely any change since NT4/W95 if I had to guess). There's replacements, but you can't count on arbitrary servers having them installed.