On 23-05-2015 13:23, Ken Moffat wrote: > On Sat, May 23, 2015 at 10:44:23AM -0500, Bruce Dubbs wrote: >> Fernando de Oliveira wrote: >>> On 22-05-2015 22:44, Bruce Dubbs wrote: >>>> Ken Moffat wrote: >>> >>>>> 1. One of my colleagues used to read out some of the advert titles in >>>>> the weekly trade rag for jobs in the Thames Valley : "Anal Progs, >>>>> Berks" and then she would say "I've got a chance, then" ;-) >>>> >>>> LOL. >>> >>> Me too. >>> >>> Well, I just wanted to add that I use also: >>> >>> " Prevent .swp creation in current directory >>> set directory=/tmp >> >> Nice hint. >> >> -- Bruce > You guys must be on more reliable systems than me ;-) In the last > couple of weeks I have several times had vim hang on my server, and > rather more times I've lost the network (nothing in the logs, but > seems to be related to 4.0+ kernels - both stable and rc) while > editing my notes using nfs. I'm very friendly with vim's .swp files, > I would not want to put them in /tmp. > > ĸen >
No, I have had crashes. That is the reason I keep saving what I do with vim (actually, gvim) as soon as I can or remember. Point is more having all ,swp in one place. You can create a /tmp-saved with the same permissions as /tmp and use: " Prevent .swp creation in current directory set directory=/tmp-save. I hated having to "find" vim's .swp's all over the place. Even in the svn directories!!! That way, you save a lot of time when recovering from a crash. I also use that directory to keep sources files I'm editing for the book, when it is necessary to reboot for checking if new packages work properly. BTW, I'm now using $ uname -r 4.0.4 and apart from vmplayer, everything else seems to be behaving very well. -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
