Path: utzoo!attcan!uunet!jarthur!usc!samsung!dali.cs.montana.edu!milton!ogicse!intelhf!agora!parsely!pdxgate!eecs!kirkenda From: kirkenda@eecs.cs.pdx.edu (Steve Kirkendall) Newsgroups: comp.editors Subject: Re: edit multiple files in vi? Summary: remap option, purpose of Elvis Message-ID: <162@pdxgate.UUCP> Date: 26 Sep 90 19:16:53 GMT References: <1990Sep19.133419@ai.mit.edu> <1990Sep24.053330.3024@monu6.cc.monash.edu.au> <1990Sep25.130305.9858@ibmpcug.co.uk> Sender: news@pdxgate.UUCP Reply-To: kirkenda@eecs.UUCP (Steve Kirkendall) Organization: Portland State University, Portland, OR Lines: 52 In article <1990Sep25.130305.9858@ibmpcug.co.uk> dylan@ibmpcug.CO.UK (Matthew Farwell) writes: >In article jansteen@cwi.nl (Jan van der Steen) writes: >>I'm very sorry but when I tested the above macros I wasn't aware that >>I was running elvis the vi clone recently posted to (I think it was) >>comp.sources.misc. >>Unlike vi, elvis *does* allow the user to map vi primitives to keys >>with the same name. > >I don't think this a very good idea. Couple of reasons. > [ examples deleted ] >This sort of behaviour is very nonstandard, and people who use it, when >they migrate to real vi will get very confused when all their macros >don't work. You never know, they might actually have to start learning >how to use vi properly. I agree that people should think twice before using any undocumented differences between vi and elvis. Actually, I'm surprised that :map d "zd even comes close to working. Dylan's correct in saying that it won't work for "dd". Incidently, Elvis currently has no "remap" option; it always acts as though remapping had been turned off, via ":set noremap". The real vi normally has remapping turned on. This is why they acted differently. >3) While im on the subject, why does elvis handle long lines so badly? >ie, it has them off the end of the screen? This causes an awful problem >when you've got a lot of long lines + a reasonably slow machine/line. >(Try editing a file with a lot of lines over 80 chars on a line at 1200 >baud. Then do a lot of 0$'s.) Why can't people who write vi clone write >vi clones? Things are done like they are in vi for good reasons. Practically all of my machines have memory-mapped video -- including the Minix machine that I wrote Elvis for. I haven't run anything at 1200 baud in years. And the "long line on multiple rows" feature of vi is hard to implement well, and I was never particularly fond of it to begin with. In writing Elvis, my goal was to produce something that FELT like vi, not something that LOOKED like vi. I figured my eyes could adjust to any differences a lot easier than my fingers could. I *DO* intend to go back and add the "long line on multiple rows" display style eventually. Other things take priority, though. BTW, I get as many comments in favor of sideways scrolling as I do against it. >Dylan. >-- >Matthew J Farwell | Email: dylan@ibmpcug.co.uk ------------------------------------------------------------------------------- Steve Kirkendall kirkenda@cs.pdx.edu uunet!tektronix!psueea!eecs!kirkenda