macOS command-line tools you might not know about

Post by filoleg » Tue, Jun 27, 2023, 3:07 PM UTC

agos wrote: post #102

nomilk wrote: post #90

Surprised pngpaste isn't mentioned (in the article nor the comments). If you take a screen shot (command + shift + 4) or partial screen shot (command + shift + control + 4) you can save it directly to an image file with: pngpaste filename.png

command shift 4 already saves a file, maybe you were thinking about command + shift + control + 3?

Post by lloeki » Tue, Jun 27, 2023, 3:10 PM UTC

donatj wrote: post #22

When mentioning `open` they should have noted that `open ` will open the given file with its associated app. It’s indispensable.

     Opened applications inherit environment variables just as if you had
     launched the application directly through its full path.  This behavior
     was also present in Tiger.

    - ensure vscode is fully closed
    - enter project directory, something sets vars in your shell (you manually or automatically via direnv)
    - code .
    - vscode process now has the env from the shell it was started
    - open another directory from the UI
    - vscode forks and inherits from its parent process, thus the other project window has the original shell's env
    - go to another directory
    - code .
    - vscode finds out it's already running, forks and opens another window. this window has the original shell env
    - fully quit vscode and reopen it, but via the app in /Applications
    - vscode opens, now has a blank environment for its main process, and forks form there to restore previous windows, which now lack the environment they had

Post by lkbm » Tue, Jun 27, 2023, 3:11 PM UTC

klausa wrote: post #8

`pbcopy` and `pbpaste` are one of my most-loved in the list. Dealing with some minified json, switching to iTerm, doing `pbpaste | json_pp | pbcopy` and having a clean output is _so_ nice.

  #!/usr/bin/env python3
  import sys
  import json
  
  print(json.load(sys.stdin))

Post by shortrounddev2 » Tue, Jun 27, 2023, 3:15 PM UTC

Finnucane wrote: post #100

shortrounddev2 wrote: post #89

While you're at it, `brew install coreutils`. The coreutils that ship with macOS lack a lot of features available on Linux. If you use bash, I recommend upgrading it, too, since Apple ships a 16 year old build (iirc due to legal issues associated with GPLv3) `brew install bash`

They're shipping zsh now.

Post by shortrounddev2 » Tue, Jun 27, 2023, 3:15 PM UTC

lloeki wrote: post #138

shortrounddev2 wrote: post #89

While you're at it, `brew install coreutils`. The coreutils that ship with macOS lack a lot of features available on Linux. If you use bash, I recommend upgrading it, too, since Apple ships a 16 year old build (iirc due to legal issues associated with GPLv3) `brew install bash`

They come from BSD (and, nitpick, are not called coreutils). These BSD tools lack features mostly only if you're used to GNU coreutils. The expanse of GNU coreutils features is questionable too: some are nice, some you can do without easily and rarely to never miss, and some are downright annoying (yes I'm looking at you, ls with colors+quotes)