On 2 April 2010 08:35, <[email protected]> wrote: > > Well, thanks a lot guys. Its been over two weeks. No one has even bothered > to answer the question even as far as saying, "Ive got no clue, dude"
If we replied to everything we knew nothing about, the lists would be unusable for the noise. http://www.google.com/linux?hl=en&q=vim-7.2+%22test37+FAILED%22&btnG=Search only finds your report. Same for vim-7.2 "test47 FAILED". Testsuites are mostly hard to understand. Vim particularly. Failures nobody else has reported might mean general breakage in your new system (terminfo, perhaps), or something unusual about your system (old processor ? old or unusual host system ?). Looking at what you posted, its an oldstyle diff between what was expected and what actually resulted. If you look at test37.in you will see it's something to do with scrolling, and at the end are two blocks of "text" with line numbers at the end. I think the failure means vim thinks your terminal is losing lines when data scrolls. That would definitely imply a mismatch between the term and how vim is addressing it. I normally build in a urxvt (x)term, which causes me some annoyance when I try to use the new system in chroot - setting TERM=xterm-color almost makes it usable in my case. Once I've booted the new system, that problem disappears. The only way to be certain if it really works, as with all software, is to run it. I guess that means you have to install it first, then you can try editing a big file and scrolling about (in a regular terminal, or perhaps in an xterm), but the best thing to do is to carry on until you can boot the new system. ĸen -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
