http://sourceforge.net/projects/console/
Some of you might find this really useful.. It lets you define console tab defaults such as what shell and start directory. Could be useful if you have special shells such as power shell or others that you work with often..
That and it has some nice visual tweaks
That actually would be handy for me if it came in a powershell flavour! :D
I hope it allows the use of bash or something similar. I can't stand cmd.exe or command.com style shells.
Quote from: Tom on April 01, 2011, 01:50:14 PM
I hope it allows the use of bash or something similar. I can't stand cmd.exe or command.com style shells.
Powershell man, it's Bash for Windows!
Quote from: Mr. Analog on April 01, 2011, 01:53:56 PM
Quote from: Tom on April 01, 2011, 01:50:14 PM
I hope it allows the use of bash or something similar. I can't stand cmd.exe or command.com style shells.
Powershell man, it's Bash for Windows!
From what I've heard, it isn't since you have to "Extend" it with C# plugins, rather than simple script functions.
Quote from: Tom on April 01, 2011, 01:55:48 PM
Quote from: Mr. Analog on April 01, 2011, 01:53:56 PM
Quote from: Tom on April 01, 2011, 01:50:14 PM
I hope it allows the use of bash or something similar. I can't stand cmd.exe or command.com style shells.
Powershell man, it's Bash for Windows!
From what I've heard, it isn't since you have to "Extend" it with C# plugins, rather than simple script functions.
How is that different from Bash?
Quote from: Mr. Analog on April 01, 2011, 02:04:31 PM
Quote from: Tom on April 01, 2011, 01:55:48 PM
Quote from: Mr. Analog on April 01, 2011, 01:53:56 PM
Quote from: Tom on April 01, 2011, 01:50:14 PM
I hope it allows the use of bash or something similar. I can't stand cmd.exe or command.com style shells.
Powershell man, it's Bash for Windows!
From what I've heard, it isn't since you have to "Extend" it with C# plugins, rather than simple script functions.
How is that different from Bash?
In bash I can just source a new script, or write a function inline, and it behaves like a new program. I've heard that in PowerShell you need to compile up a C# plugin and install it some place special for PowerShell to see, then it might see your new extension.
So the difference is you write your extensions in Bash woooooooooo
Well enjoy CMD.exe then! Have fun with that!
Quote from: Mr. Analog on April 01, 2011, 02:11:31 PM
So the difference is you write your extensions in Bash woooooooooo
Well enjoy CMD.exe then! Have fun with that!
Well I write them mostly in files in the path, or in my ~/.bashrc file. But you can write them inline. Don't need to compile them either, or specially install them.
But yeah, I don't enjoy CMD, I use linux. ;) Where the console has been useful for a decade or more.
troll'd
BAM!
FYI it isn't actually a shell it is a front end,
It can be used with CMD, Powershell and even BASH via Cygwin
Quote from: Lazybones on April 01, 2011, 03:07:12 PM
FYI it isn't actually a shell it is a front end,
It can be used with CMD, Powershell and even BASH via Cygwin
Yes! Thats what I was hoping, it was just a wrapper, or a terminal emulator itself. The available terminal emulators on windows SUCK. rxvt? PILE OF @%&#.
I went through a little Powershell tutorial on my "extended holiday", and I seem to recall being able to create scripts inline in it as well.
Scripting the command line in Windows is done (or used to be done) using batch files and PsTools. Surprising how much you can do with that combo.
And yes, I know, Linux has better command line capabilities. But let's not start a Linux v. Windows holy war on this site, seeing as how we're all friends, m'kay?
I use powershell very heavily at NAIT. It is a very powerful tool for Exchange, AD, and SQL, although it is even more useful with extensible snap-ins and external cli programs.
For example, I use powershell to collect computer accounts out of AD and then execute WMI queries and remote Shutdown.exe commands for certain patch installs. Then we report on them from the same powershell for success and failure.
Best feature stolen from unix cli's; Tab-Complete!!!!
Quote from: Melbosa on April 01, 2011, 03:29:50 PM
Best feature stolen from unix cli's; Tab-Complete!!!!
CMD has had tab complete for some time... but yes it is great to have.
Quote from: Lazybones on April 01, 2011, 04:05:43 PM
Quote from: Melbosa on April 01, 2011, 03:29:50 PM
Best feature stolen from unix cli's; Tab-Complete!!!!
CMD has had tab complete for some time... but yes it is great to have.
Yeah, though I think the default is that its turned off, or configured in such a way as to make it mind numbingly annoying. I can't remember which. Oh that reminds me, cmd.exe's command history is also annoying by default. :(
Quote from: Lazybones on April 01, 2011, 04:05:43 PM
Quote from: Melbosa on April 01, 2011, 03:29:50 PM
Best feature stolen from unix cli's; Tab-Complete!!!!
CMD has had tab complete for some time... but yes it is great to have.
Wasn't a statement about Powershell, was about the feature itself in any cli...
Quote from: Tom on April 01, 2011, 04:11:49 PM
Quote from: Lazybones on April 01, 2011, 04:05:43 PM
Quote from: Melbosa on April 01, 2011, 03:29:50 PM
Best feature stolen from unix cli's; Tab-Complete!!!!
CMD has had tab complete for some time... but yes it is great to have.
Yeah, though I think the default is that its turned off, or configured in such a way as to make it mind numbingly annoying. I can't remember which. Oh that reminds me, cmd.exe's command history is also annoying by default. :(
Been a while for you eh Tom... it is enabled by default (in fact I've never looked for it to disable it), although a lot of cli exe's you would use from CMD don't have it defined... but atleast there is Tab-Complete search that works on CMD directory lookup no matter what cli exe you are using. Powershell on the other hand has that you are required to provide Tab-Complete definitions for any powershell command, so it is never without.
Quote from: Melbosa on April 01, 2011, 04:30:49 PM
Quote from: Tom on April 01, 2011, 04:11:49 PM
Quote from: Lazybones on April 01, 2011, 04:05:43 PM
Quote from: Melbosa on April 01, 2011, 03:29:50 PM
Best feature stolen from unix cli's; Tab-Complete!!!!
CMD has had tab complete for some time... but yes it is great to have.
Yeah, though I think the default is that its turned off, or configured in such a way as to make it mind numbingly annoying. I can't remember which. Oh that reminds me, cmd.exe's command history is also annoying by default. :(
Been a while for you eh Tom... it is enabled by default (in fact I've never looked for it to disable it), although a lot of cli exe's you would use from CMD don't have it defined... but atleast there is Tab-Complete search that works on CMD directory lookup no matter what cli exe you are using. Powershell on the other hand has that you are required to provide Tab-Complete definitions for any powershell command, so it is never without.
I was just confusing things, just last night I went and fixed someone's Vista box, and used tab complete, but I do find the way it works annoying.