Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!dri500!slootman
From: slootman@dri.nl (Paul Slootman)
Newsgroups: comp.editors
Subject: Re: You could have anything in vi; now...
Message-ID: <963@dri500.dri.nl>
Date: 26 Mar 91 15:25:27 GMT
References: <#QL#6B@cs.widener.edu>
Organization: DataCount Register Informatici, Wierden, The Netherlands
Lines: 29

In art <#QL#6B@cs.widener.edu> brendan@cs.widener.edu (Brendan Kehoe) writes:
> One question has led to a few others .. your help in this is
>indispensable.
>
>	- is having delete climb up onto the end of the previous line
>	  if you're at the end of the current one a desirable feature?
Only if you're using wrapmargin.
>	- should there be a constant status line? ...
Make it a function of some :set -ting? Same thing goes for many of the
things you're asking. That way more people could be happy: if they
want it, it's possible; else, they don't have to use it.
>	- any suggestions on how to optimize updating the screen?
Don't (by default, anyway). In my experience, that would depend on
curses (unless you're going to reinvent this), and I haven't seen
two implementations of curses that optimize correctly for a given
set of termcap/info entries (the entries are probably broken in some
way, but the current vi's are happy with them...)
>	- what would you have as the 'repeat' character for the last
>	  command? (e.g. doing :; would re-do the last command)
dot? i.e. `:.' repeats...

Just my 5 cents worth (In Holland they've obsoleted the 1 cent coin)

Paul.
-- 
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
: slootman@dri.nl            :          Don't hit the keys so hard, :
: ...!hp4nl!dri500!slootman  :                             it hurts :
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=