Beyond the quite horrifying, although harmless content (hint: it's only a jpg, windows users won't be infected by anything), I'd like to challenge you: try to retrieve the content in the most optimized way.
>>1
Sorry if this is obvious, but you just want us to serialize those bytes to disk? Not worth my time, IMO.
Name:
Anonymous2009-04-28 5:43
>>3
Actually this is the aim... Obviously it's not worth, but the point is: are you smart enough to make it in a very optimized way?
If you are clever enough, you can do it with only two shell commands without write a single line of code
Name:
Anonymous2009-04-28 5:45
>>4
I'm guessing some esoteric grepping to isolate the bytes, then redirect that to output...
I would do this but I have a homework assignment due in a couple of days and I need to work on that :(
>>11
ctrl-V.
specifically ctrl-V ctrl-space for \0.
it works in nvi and vim 3 (before vim became non-free), but \0 doesn't seem to work in real vi.
the vi man page says: A ^@ cannot be part of the file due to the editor implementation (7.5f).
(http://ex-vi.sourceforge.net/vi.html#2)
>>19 nvi is more vi-compatible than vim 3, but vim 3 is more free (public domain vs. 3-clause bsd)... i'd recommend using the real vi and only resorting to either of those if you have to work with files with null characters in them.
>>20 vim 3 was public domain. later versions are licensed under one of those non-free copywrong licenses.
Name:
Anonymous2009-04-29 6:37
I'M EX/VI
SON OF A BITCH VIM
VIM IS PIG
DO YOU WANT FORCED UPSTREAM CODE SUBMISSION ?
DO YOU WANT PROPRIETARY RELICENSING ?
VIM IS PIG DISGUSTING
BRAM MOLENAAR IS A MURDERER
FUCKING UGANDA
>>21
"Public domain" is not a license. Nothing is actually in the public domain until its copyright term has expired. Was Vim 3 under an actual legally binding public license like the WTFPL, or did it just say "public domain?"