search for: r_cmd_check

On Wed, 14 Aug 2002, Henrik Bengtsson wrote: > Sorry, but it was indeed the redirection of the standard output in > Cygwin/bash that cause the first problem, not R (I should stop doing > troubleshooting at 1:00 AM). So please forget about the problems reported in > R_CMD_check.out. However, it would still be nice if you still update R CMD > check to do join with "\n". Yes, on ME. That was my prime suspect. The change has already been made. > Also, the problem with TooLongLines.R still remains since it crashes [R] > also when sourced from within Rgu...

...temporary [R] file was correct. I narrowed down the problem to be with the redirecting of the standard input, i.e. <, into [R] and I also found that I could not get the same problem if I source()'d the same file. Then I thought it might be my shell (Cygwin/bash), but not! Doing % cat < R_CMD_check.out is just fine, but when doing R --vanilla --quiet < R_CMD_check.out I run into problems. It looks like every line that is long enough will get some garbage bytes inserted at column 1023. I have attached the R_CMD_check.out file with comments for you. As you see, it is not what R CMD chec...