> No, the one with history going back more than an hour When did you last try PowerShell? In version 1.0 the history size was 64 by default - but could be cha

> No, the one with history going back more than an hour When did you last try PowerShell? In version 1.0 the history size was 64 by default - but could be changed. In PowerShell v3 that's increased to 4096 by default. If you can overflow that in an hour you are a seriously impressive typist! That more than one command line per second - sustained. If you manage to break that, you can assign any value up to 32767 - yes that's 9 different commands per second. PowerShell can discard duplicates, so if you manage to break 4096 different commands in the run of one day you are doing something wrong. Like not using snippets (http://blogs.msdn.com/b/powershell/archive/2012/06/27/snippets-in-windows-powershell-ise-3-0.aspx http://blogs.msdn.com/b/powershell/archive/2012/06/27/snippe...). Oh - i forget - bash don't do snippets. > and tab completions on anything except files in `pwd`. Seriously, have you tried PowerShell - like ever? PowerShell's tab completion blows anything bash out of the water: o PowerShell tab completions are based on command metadata - not on external "completion definitions". The result is that tab completion works for all cmdlets - not just for those that has a "completion file". o PowerShell will complete on anything: Command names, parameter names (options), parameter values - even dynamic values. Try this on PowerShell "ps <tab>" - and you'll be allowed to complete based on the names of running processes. o PowerShell tab completion also works for parameters of user defined functions - and even for parameters of script files. If you declare a script to take parameters, PowerShell will pick it up and allow tab completion on the parameter names and allowed values.