835 reputation
11028
bio website
location
age
visits member for 3 years, 3 months
seen Dec 2 '13 at 5:05

Apr
2
comment head command options and reading man files
Thanks for answering my question, you also taught me some more in the process, I appreciate it.
Apr
2
comment head command options and reading man files
I guess another point to learn is: some options fall out of fashion, get deprecated and are actively hidden/deprecated so that new users (like me) will avoid them. You know what I think would be better than this hiding (not putting in plain sight) approach? Just show the option and say: don't use this - it may not be there in a future version. I would have been less confused. Probably just me though.
Apr
2
comment head command options and reading man files
So the answer to one of the points above is: sometimes look into the info of the command after reading the --help and man..
Apr
2
comment head command options and reading man files
And by doing so, succumb to the hopelessness of the dev/user divide, plunging into a life of pessimism and psycho-active tablets. There must be hope beyond browsing the source!
Apr
2
comment head command options and reading man files
head -2 is synonym to head -n 2, why? Where does it say so in the manual? head -3 is synonym to head -n 3, etc. This being the case but not being explicitly documented has a feel of "black magic"/"secret lore".. ;)
Apr
2
asked head command options and reading man files
Apr
1
accepted ping timeout differences between OS X and Linux/other OSs
Apr
1
comment ping timeout differences between OS X and Linux/other OSs
Precise timeout: so that I know 100 hosts will take at most 100 seconds. Bash command autocompletion: I have my functions all starting with my_function_ so that I can tab-complete them and have the standard options (in this case -c 1) auto-selected. Readable is a matter of personal taste: for functions I define with many options "pre-selected" I find reading the function name more "natural language like" than ping -o1 -o2 -o3 -o4..
Apr
1
comment scp and compress at the same time, no intermediate save
I think that 7z and tar are a very powerful combination, I get with them better savings than with other compression algorithms. I am sure new and better ones will replace 7z.. but I don't understand why you would be against using the pair "in principle".. am I missing something?
Apr
1
comment ping timeout differences between OS X and Linux/other OSs
why have that function? 1. no stdout output; 2. precise timeout, indep. from the platform (predictable wait on batch execution) 3. can use auto-completion and is more readable 4. in a script, I can add logging of unavailable hosts by editing a single func def
Apr
1
comment ping timeout differences between OS X and Linux/other OSs
Why would you not use that function?
Apr
1
revised ping timeout differences between OS X and Linux/other OSs
added 385 characters in body
Apr
1
asked ping timeout differences between OS X and Linux/other OSs
Mar
30
revised scp and compress at the same time, no intermediate save
added 14 characters in body
Mar
30
comment scp and compress at the same time, no intermediate save
Thanks! I am going to accept this great answer but please, add a full, stand-alone command line that uses both rsync and 7za, with final output to the remote filesystem. I liked -z but I would like to decouple the compression stage so.. how would I use rsync in that case, please?
Mar
30
revised scp and compress at the same time, no intermediate save
added 156 characters in body
Mar
30
revised scp and compress at the same time, no intermediate save
deleted 1 characters in body
Mar
30
asked scp and compress at the same time, no intermediate save
Mar
30
comment Human readable system memory reading crom CLI?
It is, certainly, more precise to display it as so.. no doubt about that.. probably the "humans" this is intended for are still aware of the issues you raise.. (I had not thought of that).
Mar
29
awarded  Critic