Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!bloom-beacon!eru!hagbard!sunic!sics.se!ifi.uio.no!enag From: enag@ifi.uio.no (Erik Naggum) Newsgroups: comp.editors Subject: Re: vi and emacs Message-ID: Date: 3 Jun 91 22:27:42 GMT References: <1991Jun1.021505.4043@trl.oz.au> <1991Jun03.151727.9944@chinet.chi.il.us> Sender: enag@ifi.uio.no (Erik Naggum) Organization: Naggum Software, Oslo, Norway Lines: 29 Nntp-Posting-Host: gyda.ifi.uio.no In-Reply-To: les@chinet.chi.il.us's message of 3 Jun 91 15: 17:27 GMT Originator: enag@gyda.ifi.uio.no Leslie Mikesell writes: | | In article <1991Jun1.021505.4043@trl.oz.au> soh@andromeda.trl.OZ.AU (kam hung soh) writes: | >[...] I decided to dump emacs and use vi exclusively. | >It was a horrible experience. No multiple files / views / buffers, no | >cut-and-paste between windows, no auto auto-indent for the code | | You can, of course, run multiple vi's under any windowing system that | allows it, and use the windowing system's cut and paste if you | prefer it to explicit tmp files (I don't, except when one of the | windows is running something that doesn't know how to use files or | the programs in the different windows don't share a common filesystem). | You can also use an external program to auto-indent or whatever else | you need to do. I may be missing something, but I usually use "ay} to save a paragraph in buffer (?) a, switch files*, and do "ap where I want to put it back. There are at least 26 such buffers available. I also use marks a lot, to move around faster. It seems that these features are not well known. * The only thing I hate about switching files is that vi insists on writing out the current file and reading in the new file in its place. Not always what I want. -- Erik Naggum Professional Programmer +47-2-836-863 Naggum Software Electronic Text 0118 OSLO, NORWAY Computer Communications