Anyone who tries to take my general purpose computer or my photolithography equipment will meet the nasty end of my shotgun.
I FUCKING HATE YOU DIE IN A FIRE CRETIN.
Name:
Anonymous2012-11-05 14:26
>>80
That's me, but I'm truly going to shut up and I suggest everyone else does too because there is one hell of a Erlang programmer being the blackest black a nigger could ever be. His truly black and nigger and the best programmer I know.
Name:
Anonymous2012-11-05 20:41
>>78 > is really 1> (stdout), 2>&1 redirects fd 2 (stderr) into fd 1's stream. So if the program produces any output on stderr you need to redirect that as well, and this is how.
It's not important whether you redirect them separately to /dev/null, but if you want to capture both streams as one (into a file, say), you have to do it that way... and in that order last I checked.
Name:
Anonymous2012-11-06 5:20
>>83
Problem is, "&>" was supposed to do that in one single operation, as opposed to having to split them into two (">/dev/null" and "2>&1"). It's why that doesn't always work, that I don't get.
Name:
Anonymous2012-11-06 5:44
this thread is so full of simultaneous fail and insight, just like bash!
Name:
Anonymous2012-11-06 6:13
it was mentioned before in this thread, but it's still a fact that sort of eludes me. the parsing of " versus '. the programmatic escaping of quotes? these are things which bug me the most, especially when loops break lines on spaces. fucking bullshit.
>>91
Literally everyone on /prog/ has at least one half-finished textboard or imageboard implementation somewhere on his hard drive.
Just look through people's Github accounts. There's dozens.
>>93
Suitably self-absorbed riders with githubs should agree on a common signature to place in an agreed-upon place on their github profiles or projects.