3. cmd: why we use it?
- to connect with remotes
- because we want to feel like a HACKER
- its useful and faster then clicking over GUI
- lot of tools have no GUI
4. cmd: why not?
- hard to love it (resizing, selecting and any
other regular actions are hard as f***)
- lack of completion
- lack of EVERYTHING we need?!
6. cmd: how to change it?
- unix-like shell environments
- Windows console window enhancements
- combos of two above
- other tools
7. unix-like shell: Cygwin
Pros:
- provides rich POSIX-compliant layer
- enables building from source on Windows
- two package managers: pact and apt-cyg
9. unix-like shell: Git for Windows 2.x
Pros:
- supports 64-bit and UTF-8
- maintained & frequently updated with
Cygwin
- basic auto completion
- Git Bash here context menu
10. unix-like shell: Git for Windows 2.x
Cons:
- tools like mysql works only with 3rd party
tools (winpty), but without completion
11. unix-like shell: Babun
Pros:
- pre-configured git & shell
- mysql works like a charm
- 'Open Here...' context menu entry
- surprisingly fast
13. cmd enhancements: ConEmu
Pros:
- smooth and friendly window resizing
- tabs
- drag and drop of files and folders in Far
Manager
- highly configurable
17. combos: cmder
Pros:
- built on top of (great) ConEmu
- portable version with only ~4.5MB in size
Cons:
- sometimes feels slow (lot of things going on
under the hood)
18. other tools (improvements)
GOW - Set of ~120 command line tools
Chocolately - package manager for Windows
wpkg - windows package manager
FAR - file manager (brilliant integration with
ConEmu)