gerrc.blogg.se

It is much easier to pipe the output directly into the clipboard, than to select and copy the output. I use the last command a lot when I need UUIDs for custom configuration profiles. $ system_profiler SPHardwareDataType SPSoftwareDataType | pbcopy

$ textutil -convert txt MyBook.docx -stdout | pbcopy # converts Word Doc to plain text and puts it in the clipboard While all references visible to the user where changed to the Mac OS naming, you still find the old NeXTSTEP names in the ‘innards’ of macOS, hence pbcopy and pbpaste.)Įxamples: # easier than open, select all, copy What was called the ‘clipboard’ in Mac OS was called ‘pasteboard’ in NeXTSTEP. (NeXTSTEP was the operating system that Mac OS X was originally based on. So, anything you pipe into pbcopy will end up in the clipboard, so you can paste it into a different application. Pbcopy will take the contents of stdin (usually text, but could be any stream of data) and put them in the clipboard. There are however, two commands, specific to macOS that connect the clipboard closer to other shell commands.

You can simply copy the command from the iBook text and paste into Terminal.) (This is useful when you read a great iBook with many Terminal commands. You can select text in the Terminal and copy it, and then paste it elsewhere, you can also paste text in the command prompt itself. Terminal can trivially interact with the clipboard. Later the system reads from the clipboard (and possibly converts the data) when you paste (⌘V). The clipboard is the ‘place’ where macOS stores anything you cut (⌘X) or copy (⌘C). Continuing in my informal series of Terminal articles, I’d like to visit two tools that help interact from the shell to a particular part of the macOS UI: the clipboard.