Live data from Hacker News

Fun at the Unix Terminal

blog.regehr.org

31–40 of 56 posts

Re: Fun at the Unix Terminal

#32
post #27

Earlier quoted context omitted.

Why would you even bother with that when `say` can take a string or read from stdin? Just use $ say $(fortune) or $ fortune | say -f- For bonus coolness, add "-i" (it prints the lines and highlights the current word during reading).

Because it's fun spawning a new process and watching the otherwise idle cores of your box reach 0.1% usage for a millisecond.

Don't all three of those commands spawn new processes?

Re: Fun at the Unix Terminal

#36
You kids today and your fancy command lines. When I was in sixth grade, state of the art joking around with technology meant multiplying two numbers on a calculator with red LEDs and turning it upside down to (sort of) spell SHELL OIL

Re: Fun at the Unix Terminal

#37

Does anyone have a place/site for browsing through new/popular utilities? I've been on Ubuntu for the last year and I love it, but reading this I just realised I don't have anywhere to browse or find things like this.

I wonder if it is time for a freshmeat.net alternative?

Re: Fun at the Unix Terminal

#38
post #22

Instead of: $ fortune > my_fortune.txt $ say -f my_fortune.txt One could use the underrated (bashism) process substitution: $ say -f Which works wonders for e.g diff'ing live: $ diff

Why would you even bother with that when `say` can take a string or read from stdin? Just use $ say $(fortune) or $ fortune | say -f- For bonus coolness, add "-i" (it prints the lines and highlights the current word during reading).

Not all commands accept input as arguments, so it's still a good trick to know.
Post reply on HN