16 ms·

No, the one with history going back more than an hour, and tab completions on anything except files in `pwd`.

• lzybkr 12y ago
  Try https://github.com/lzybkr/PSReadLine https://github.com/lzybkr/PSReadLine - included in Windows 10 now.
  • voltagex_ 12y ago
    Hey, do you have an announcement somewhere about it being included in 10? Congratulations, at any rate.
    • lzybkr 12y ago
      It hasn't been announced anywhere unless you count random tweets. I should post something on the PowerShell team blog one of these days.
• stinos 12y ago
  that's basically what conemu brings
  • maccard 12y ago
    Powershell has had that support for quite a while too.
  • maratc 12y ago
    Disclaimer ConEmu is not a shell, so it does not provide "shell features" like tab-completion, command history and others. [1] [1]https://code.google.com/p/conemu-maximus5/ https://code.google.com/p/conemu-maximus5/
    • stinos 12y ago
      Fair point, my mistake: my ConEmu does have history and copletion but it has been so long ago I installed it I didn't remember this is through clink https://code.google.com/p/conemu-maximus5/wiki/ConEmu_Clink https://code.google.com/p/conemu-maximus5/wiki/ConEmu_Clink
• useerup 12y ago
  > 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.
  • maratc 12y ago
    > When did you last try PowerShell? I fired it up just now on Windows 7 that I have available. > In PowerShell v3 that's increased to 4096 by default. Once I quit Powershell, all my history's gone. On my unix machine, I can search my command history all the way back to 2011. This short-term memory won't cut it for my needs. > Try this on PowerShell "ps <tab>" I tried, and immediately received the first file in my user directory. "dir /<tab>" will erase the / and complete it with some other file name. I was expecting it to list the options.