schwarzerf at gmail.com
Fri Jan 2 03:21:46 UTC 2009
--- Please enter the report below this line. ---
I now created a file with multiple shorter lines (about 800 chars).
for k in `seq 0 1000`; do for i in `seq 0 200`; do echo -n "$i " >>file.test; done; echo >>file.test; done
for i in `seq 0 5000`;do cat file.test >>file2.test; done
file2.test is 3.3G then.
Opening it in vim leads to the same issue. Instantly "file2.test"
[New File] is shown and nothing else happens. After typing
:wq [Enter], the file is empty.
My /tmp is only 350M.
My swap is 2.7G but is never used.
Also, using a 2.6G file doesn't change anything.
However, with a file size of 2.0G, I have the behaviour you
described. It takes its time and the rest of the system complains
all the time (swap is at ~25%), but the file is actually loaded,
can be edited...
But when I want to save it, there is an error: "E297: Write error in swap file" and vim works really hard on the system's cpu and MEM
continuously. Swap is now at 70% and rising.
This is an expected behaviour. If the file I want to edit does not (or hardly) fit in my memory, it is hard to edit it.
The [New file] and overwrite on saving behaviour however, doesn't
feel intended. Did you really never experience that in your tests?
--- System information. ---
Kernel: Linux 2.6.26
Debian Release: 5.0
500 unstable www.debian-multimedia.org
500 unstable ftp2.de.debian.org
1 experimental ftp2.de.debian.org
--- Package information. ---
Depends (Version) | Installed
vim-common (= 2:7.2.049-2) | 2:7.2.049-2
vim-runtime (= 2:7.2.049-2) | 2:7.2.049-2
libacl1 (>= 2.2.11-1) | 2.2.47-2
libc6 (>= 2.7-1) | 2.7-16
libgpm2 (>= 1.20.4) | 1.20.4-3.1
libncurses5 (>= 5.6+20071006-3) | 5.7+20081220-1
libselinux1 (>= 2.0.59) | 2.0.65-5
More information about the pkg-vim-maintainers