This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-01
Channels
- # announcements (14)
- # aws (1)
- # babashka (22)
- # beginners (105)
- # biff (12)
- # calva (1)
- # cider (7)
- # cljsrn (1)
- # clojure (33)
- # clojure-europe (22)
- # clojure-germany (1)
- # clojure-uk (3)
- # clojurescript (28)
- # component (15)
- # copenhagen-clojurians (1)
- # core-typed (29)
- # cursive (8)
- # data-science (2)
- # datomic (2)
- # emacs (16)
- # gratitude (3)
- # humbleui (3)
- # introduce-yourself (4)
- # lsp (1)
- # other-languages (3)
- # rdf (3)
- # sci (6)
- # shadow-cljs (9)
- # spacemacs (12)
- # tools-build (1)
- # tools-deps (5)
- # vim (3)
- # vscode (1)
A discussion in #calva reminded me of a thing I often do, that might not be obvious to everyone. It is to use the integrated terminal to pipe output from a command to VS Code. Like so:
$ <some command> | code -<some command>. Say it is a curl command pulling down some big chunk of JSON. jq is fine, but if I want to do it more interactively I:
1. $ curl ... | code - . This opens the output in a VS Code editor tab and focuses it.
2. VS Code is excellent at guessing the language, if it fails: cmd/ctrl+k m and select JSON.
3. Format Document: shift+alt+f🤯 3
❤️ 7