Hi, Andy, From: "Andy Finkel" > Is it my imagination, or is skip (both as a command and > as a refinement) completely out to lunch when used on files ?
In the context of a refinement, it has been known to flake out, especially in regard to also using /direct. You will find differences of opinions on the best work-around, but for getting an unbuffered binary file, the way that I use works as follows: port: open/direct/binary %//rebol/view/nyc.jpg copy/part p 100 ;throws away the first 100 bytes contents: copy p ;get rest of file close port The skip-as-a-refinement-bug has likely been reported to feedback, but one more time wouldn't hurt. :-) ... > Using SKIP as a command didn't work all that much better. (the example > in the new FAQ basically hangs, using up 100% of the CPU) Now that I've not seen before. In what way were you using it? Here is one way: data: [1 2 3 4] ; yields == [1 2 3 4] data: skip data 2 ; yields == [3 4] data ; yields == [3 4] data: head data ; yields == [1 2 3 4] Please feel free to ask further clarification, especially if someone else doesn't also answer. Now, stop "skipping" your work, and get back to it! :-) --Scott Jones -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
