Viewing profile — binaryphile
binaryphile
HN member- Joined
- Tue, Dec 27, 2016, 8:53 PM UTC
- HN karma
- 84
- Public activity
- 16 items
- HN profile
- View on Hacker News ↗
About binaryphile
Recent public activity
- story
- story
- story
-
comment
Comment #18416786
Finally got around to updating the post with your suggestions. Thanks again.
-
comment
Comment #18384610
I can relate to the earlier poster because I had the same problem finding all of these rules in one place. I wrote it to be precisely what I wish someone had told me before I got s…
-
comment
Comment #18383378
Thanks for the tips. We're still running on 1.11 because of problems with the recent glibc updates not matching the kernels in our deployment environment.
-
comment
Comment #18383368
I found the nix-repl to be very helpful in this situation...you can also invoke command-line expressions directly with nix but it's a bit more arcane.
- story
- story
-
comment
Comment #17771851
A bashtardization: rb () { [[ $1 == -l ]] && shift case $? in 0 ) ruby -e "STDIN.each_line { |l| puts l.chomp.instance_eval(&eval('Proc.new { $* }')) }";; * ) ruby -e "puts STDIN.e…
-
comment
Comment #16199328
Yup. The moment you need editing capabilities more sophisticated than those three keys, though, I recommend switching to vi input mode (set -o vi) if you are familiar with vim keyb…
-
comment
Comment #15329542
Boy, those Trojans really got us with that last horse, hoowee, but this one looks solid.
-
comment
Comment #15068301
The irony of using the example of a statistics professor to prove a systemic conspiracy with a sample size of 1 is not lost on me.
- comment
-
comment
Comment #15000938
Here's what my take on the script would be in bash (albeit untested): https://gist.github.com/binaryphile/3cf01870516d5fffafbc84a0... Whoever wrote the initial bash script was clea…
-
comment
Comment #14909961
"Never go to sea with two chronometers; take one or three." - adage cited in the Mythical Man Month