4 ms·

>I am always surprised to hear these statements. No kidding. I use it every day nearly all day and I can count the number of times I've had the OS itself get

>I am always surprised to hear these statements. No kidding. I use it every day nearly all day and I can count the number of times I've had the OS itself get in my way on 1 hand.

ethbro 9y ago
> I can count the number of times I've had the OS itself get in my way on 1 hand I could overflow both hands just counting two Explorer things: (1) trying to figure out where MS put a setting/option if it's not on Ribbon & (2) trying to use any advanced search operators.
- rjbwork 9y ago
  I usually grep (powershell Get-ChildItem | Select-String) if I'm trying to do anything crazy in searching files.
  - ethbro 9y ago
    Then there's also Powershell (as much as it improves on cmd) reminding me of adventure games where I have to remember which of the five synonymous verbs is recognized and does the thing I want.
    - lenkite 9y ago
      You don't have to remember anything in powershell as you get parameter completion and command completion by default. Powershell useability beats the standard UNIX shells (bash/zsh) in command discovery and assistance. You even use PSReadLine if you want VI keybindings at the command line.
      - ethbro 9y ago
        Am I using it wrong? I realize a large majority of those aren't used frequently, but there are ~250 cmdlets, each of which attempts to have a unique-but-also-generic name. https://technet.microsoft.com/en-us/library/ff714569.aspx https://technet.microsoft.com/en-us/library/ff714569.aspx Let's say I didn't know ForEach-Object existed (trivial example, but generalizes), how do I find out there is a cmdlet that does what I'm looking for?
        lenkite 9y ago
        `Get-Command` lists all the cmdlets in the current sesion. You can also alternatively hit `help -category cmdlet` which lists all cmdlets with their short alias and long name. You can do `man -category cmdlet` if you wish to page through. The first thing in powershell you should do is `help help` :).

>I am always surprised to hear these statements. No kidding. I use it every day nearly all day and I can count the number of times I've had the OS itself get in my way on 1 hand.

ethbro 9y ago

> I can count the number of times I've had the OS itself get in my way on 1 hand I could overflow both hands just counting two Explorer things: (1) trying to figure out where MS put a setting/option if it's not on Ribbon & (2) trying to use any advanced search operators.

rjbwork 9y ago
I usually grep (powershell Get-ChildItem | Select-String) if I'm trying to do anything crazy in searching files.
- ethbro 9y ago
  Then there's also Powershell (as much as it improves on cmd) reminding me of adventure games where I have to remember which of the five synonymous verbs is recognized and does the thing I want.
  - lenkite 9y ago
    You don't have to remember anything in powershell as you get parameter completion and command completion by default. Powershell useability beats the standard UNIX shells (bash/zsh) in command discovery and assistance. You even use PSReadLine if you want VI keybindings at the command line.
    - ethbro 9y ago
      Am I using it wrong? I realize a large majority of those aren't used frequently, but there are ~250 cmdlets, each of which attempts to have a unique-but-also-generic name. https://technet.microsoft.com/en-us/library/ff714569.aspx https://technet.microsoft.com/en-us/library/ff714569.aspx Let's say I didn't know ForEach-Object existed (trivial example, but generalizes), how do I find out there is a cmdlet that does what I'm looking for?
      - lenkite 9y ago
        `Get-Command` lists all the cmdlets in the current sesion. You can also alternatively hit `help -category cmdlet` which lists all cmdlets with their short alias and long name. You can do `man -category cmdlet` if you wish to page through. The first thing in powershell you should do is `help help` :).