This looks interesting, the tabbed effect is a major draw for me personally, but I feel like hes got a bit of a price tier issue with the rewards on the kickstarter... His target price for the released product is hopefully $10 ( a good deal ) The $20 pledge gets you 2 licenses Cost Per License: $10 Additional Perk: Nothing The $50 pledge gets you 1 license Cost Per License: $50 Additional Perk: Beta Access The $100 p…
If you want a tabbed Windows console, take a look at "Console": http://sourceforge.net/projects/console I've been using it for a while, and it works pretty well. From the project page: " Console is a Windows console window enhancement. Console features include: multiple tabs, text editor-like text selection, different background types, alpha and color-key transparency, configurable font, different window styles. "
Reimagining the Windows Command Line
31–40 of 74 posts
Re: Reimagining the Windows Command Line
#32This looks interesting, the tabbed effect is a major draw for me personally, but I feel like hes got a bit of a price tier issue with the rewards on the kickstarter... His target price for the released product is hopefully $10 ( a good deal ) The $20 pledge gets you 2 licenses Cost Per License: $10 Additional Perk: Nothing The $50 pledge gets you 1 license Cost Per License: $50 Additional Perk: Beta Access The $100 p…
If you want a tabbed Windows console, take a look at "Console": http://sourceforge.net/projects/console I've been using it for a while, and it works pretty well. From the project page: " Console is a Windows console window enhancement. Console features include: multiple tabs, text editor-like text selection, different background types, alpha and color-key transparency, configurable font, different window styles. "
http://code.google.com/p/conemu-maximus5/
ConEmu starts a console program in a hidden console window, and provides an alternative customizable GUI window with various features:
Re: Reimagining the Windows Command Line
#33When I work on windows, I just use cygwin with the mintty shell to get productive with a familiar look&feel. What am I missing with this setup that Wish fills?
A lot of Windows users (like myself) are somewhat committed to tools like Powershell in addition to Cygwin. I currently keep both Git Bash and Powershell open so I can switch back and forth as needed. Wish allows me to switch between these seemlessly with a common set of features across both.
Re: Reimagining the Windows Command Line
#34I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based tool. I've spent a week trying to finish the simple task of installing the framework. No success. Now, I don't make a living programming, so I'm definitely at the shallow end of the programming pool. But still. A week.
There are several problems as I see it:
- No discoverability. You are given no clues whatsoever as to what commands are available to you. You have to know exactly what you want to do. Yes, you can read manpages, forum posts, etc. but finding, learning and memorising a whole set of commands used in some program you might never use again seems like a terrible waste of productive time. Without the manual you're flying blind.
- All sorts of opaque dependencies. Composer for instance apparently requires git installed for it to work. But it doesn't say that anywhere. You also need to define paths, etc. which isn't covered anywhere.
- A million minor flaws and bugs. Until now I've run up against at least a few bugs, either in composer or in some other part of the chain of software. Only opaque general warnings are given, and finding out exactly what is wrong is next to impossible.
- Terrible UI. Copying and pasting doesn't follow convention, copying from a commandline to a notepad inserts linebreaks that you have to clean up manually, there's no way to maximise the cmd.exe window. The list of basic usability flaws goes on.
This isn't meant as trolling or ranting, although I must say I'm genuinely alienated by the commandline. I understand that text is great way for programs to talk to each other, I understand that the commandline is a great way to talk to a remote server, and I understand the power that piping, etc. gives you, so it's not like I'm denouncing the power that's inherent in the tool.
The problem is that the learning curve is tremendously steep, and I just don't feel it's worth it. To do the simplest thing I need to learn how a whole ecosystem works. I also have to page the information I need together from a number of different sources that I first have to find. It's kind of like having to build a car just to ride down to the baker to get some bread. It's quicker to walk than assemble a car before you can drive.
Re: Reimagining the Windows Command Line
#35This might be slightly off-topic, but am I the only one that thinks that command line tools are archaic with some pretty serious drawbacks? I see and acknowledge the power they can wield in the right hands, but for mere mortals it's a terrible experience. Especially on a windows box. I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based…
I can think of several GUI apps that have ALL of those problems but I also can't script them, alias them or fix them.
I spent 75% of my day in the terminal because I'm proficient and fast with it. Most of programming has a learning curve, I don't see why people expect otherwise when it comes to an interface that is every bit as powerful as a GUI but with a specific interface.
No offense but with the number of misconceptions in that post, maybe you need to spend more time with it before dismissing it out of hand. (edit) seriously, you don't know about Notepad.exe and line breaks. :/ Man... if you would spend a bit of time on tooling and learning your environment you probably wouldn't be spending half the time you are doing whatever it is you're doing. Jumping into something is fun, but for sufficiently complex things, you DO have to step back and read the manual.
Knowing what Symphony does, I'm quite sure that learning the CLI tool would be a far better use of everyone's effort than a GUI tool. This is even a place where I think the CLI tool makes exceedingly more sense to use.
edit: To be fair, if I had to use Windows default tools and a PHP generator tool all day long, my words would probably be more angry than yours.
Re: Reimagining the Windows Command Line
#36This might be slightly off-topic, but am I the only one that thinks that command line tools are archaic with some pretty serious drawbacks? I see and acknowledge the power they can wield in the right hands, but for mere mortals it's a terrible experience. Especially on a windows box. I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based…
Besides you can never learn everything all at once, but you slowly pick things up over time as you need them. Then, one day, you wake up and the command line feels like home. My advice, don't try to learn any of it until you have a specific need of doing something, only then will you really retain anything you gleam from it. And don't try to use/learn it on windows.
Re: Reimagining the Windows Command Line
#37This might be slightly off-topic, but am I the only one that thinks that command line tools are archaic with some pretty serious drawbacks? I see and acknowledge the power they can wield in the right hands, but for mere mortals it's a terrible experience. Especially on a windows box. I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based…
proper command line shells and tools offer auto-completion and inline help.
> - All sorts of opaque dependencies.
Bad or unfinished products is a concept orthogonal with command line. I've had to manually install a particular unspecified version of .NET to get some graphical application to work, for instance.
> - A million minor flaws and bugs.
Again, totally unrelated to CLI. Most applications are barely usable, for instance almost all of professional in-house applications at most companies are abysmal, though graphical.
> - Terrible UI.
Probably a unix program; you shouldn't use Notepad, it doesn't understand any other line end convention than . Notepad is mostly useless, and there are many valid replacements.
Re: Reimagining the Windows Command Line
#38This might be slightly off-topic, but am I the only one that thinks that command line tools are archaic with some pretty serious drawbacks? I see and acknowledge the power they can wield in the right hands, but for mere mortals it's a terrible experience. Especially on a windows box. I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based…
For example, there's absolutely no reason why command line tool options can't be discoverable in the same way object methods in Java/C#-ish IDEs are.
Re: Reimagining the Windows Command Line
#39Earlier quoted context omitted.
Great feedback and something I have been concerned about myself. I'm considering adjusting the higher tiers so the cost per license is more consistent.
Wow, thanks for responding! I hope it didn't come across as negative, it was just something I noticed and wondered if other people saw the same thing, or if I was just being nitpicky. I hope your project reaches funding, this looks like a really cool idea
Re: Reimagining the Windows Command Line
#40This might be slightly off-topic, but am I the only one that thinks that command line tools are archaic with some pretty serious drawbacks? I see and acknowledge the power they can wield in the right hands, but for mere mortals it's a terrible experience. Especially on a windows box. I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based…
> - No discoverability. proper command line shells and tools offer auto-completion and inline help. > - All sorts of opaque dependencies. Bad or unfinished products is a concept orthogonal with command line. I've had to manually install a particular unspecified version of .NET to get some graphical application to work, for instance. > - A million minor flaws and bugs. Again, totally unrelated to CLI. Most application…
This is not discoverability. How will it help me figure out curl's command line options? How will it help me not having to remember whether tool X wants "command [files] [options]" or "command [options] [files]" or either? How will it help me reuse something i just ls'ed into vision without having to retype half the path i just typed into that ls command?