brendan@cs.widener.edu (Brendan Kehoe) (03/25/91)
Whelp, the flood's started to slow down a bit (a total of 123
messages since I posted my original message 5 days ago). I can start
addressing some of the stuff people've suggested (around 240 of them).
(At this rate, I need someone to give me a grant so I can dedicate
all of my "other" time to this and forget mundane things like rent.)
First, yup, I am aware of both stevie and elvis. I am using them as
models for the logic for areas that I'm not able to come up with
myself (or it would take weeks to get it working properly). And it
will (hopefully) be compilable on Unix, PC's, and probably VMS.
(Anybody wanna port it elsewhere?)
I'm also checking out TCL for the extension language for it (over 30
requests for something like this). Boy o boy, just what I need,
another language. <grin> I considered Perl, but figured I'd leave that
as a "possibility" for the future. Any arguments in its favor (backed
up with facts) are very welcome.
Oh, the overwhelming winner of any suggestion was to have ~ be a real
operator .. over 60 people asked for that. (I know, I can sell all of
this to some major vendor as a contract study of users' needs. Yeah
yeah that's the ticket....)
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?
- should there be a constant status line? or a more elaborate
result of doing ^G ? how 'bout how each window should be
identified when there's more than one? Is a static status
line necessary then?
- any ideas on an "extended mark" system? e.g. still retain
support for m[0-127], but have another set of marks, to
perhaps bridge across files, or whatever
- what's a comfortable default for the C comment column?
- any "undocumented" features in versions of vi that you've
used? (e.g. the '_' operator [d_ == dd])
- since I'm a real nroff novice, what things would you want in
nroff mode? (I also plan to dig thru the Emacs lisp source
for its nroff major mode.)
- should the command-line history be editable in a buffer? or
just on the command line?
- any rugged tests out there for things being 8-bit clean?
- what features should be present in a query & replace system?
- what are your feelings on what should be mandatory in a
"secure" mode? (e.g. no shell escapes, etc)
- should you be able to edit a macro in a buffer?
- any suggestions on how to optimize updating the screen?
- what would you have as the 'repeat' character for the last
command? (e.g. doing :; would re-do the last command)
- anybody care to describe the added things needed to support
C++ tags? (I don't know the language yet.)
- suggestions on implementing file recovery (including the
ability to save multiple buffers)?
Thanks again!
Brendan
--
Brendan Kehoe - Widener Sun Network Manager - brendan@cs.widener.edu
Widener University in Chester, PA A Bloody Sun-Dec War Zone
Now that we know he has ID, we could give him an account. finger bush@cs....slootman@dri.nl (Paul Slootman) (03/26/91)
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 : =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
peter@ficc.ferranti.com (Peter da Silva) (03/28/91)
In article <963@dri500.dri.nl> slootman@dri.nl (Paul Slootman) writes: > > - 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), Don't use curses for things like editors. Curses doesn't handle scrolling regions (windows) worth a damn. -- Peter da Silva. `-_-' peter@ferranti.com +1 713 274 5180. 'U` "Have you hugged your wolf today?"
einari@rhi.hi.is (Einar Indridason) (03/29/91)
In article <#QL#6B@cs.widener.edu> brendan@cs.widener.edu (Brendan Kehoe) writes: > - any rugged tests out there for things being 8-bit clean? If I can be of any help, I would like to offer my assistance for testing your vi. (That is, the little bit I know about vi.) (What one doesn't do for the 8th bit :-) -- Internet: einari@rhi.hi.is | "Just give me my command line and drag UUCP: ..!mcsun!isgate!rhi!einari | the GUIs to the waste basket!!!!" Surgeon Generals warning: Masking the 8th bit can seriously damage your brain!!
markh@squirrel.LABS.TEK.COM (Mark C. Henderson) (03/31/91)
In article <9PAAVSF@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes:
->> Don't (by default, anyway). In my experience, that would depend on
->> curses (unless you're going to reinvent this),
->
->Don't use curses for things like editors. Curses doesn't handle scrolling
->regions (windows) worth a damn.
->--
->Peter da Silva. `-_-' peter@ferranti.com
->+1 713 274 5180. 'U` "Have you hugged your wolf today?"
My experience is that this is highly dependent on which flavour of
Unix you are using.
Mark
--
Mark C. Henderson, Computer Research Laboratory, Tektronix, Inc.
MS 50-662, P.O. Box 500, Beaverton, OR 97077, U.S.A.
INTERNET: markh@crl.labs.tek.com MCI MAIL: 378-4996
Tel: +1 503 627 6280 Fax: +1 503 627 5502 TELEX: 6503784996MCI UWcarlson@mrxwebo.dg.com (James Carlson) (04/02/91)
Check out Mansfield Software's KEDIT ... you might find a few things that you can add to vi. For example, KEDIT can edit multiple views of the same file, can selectively edit subsets of a file, and can search for lines that do not contain a particular string or pattern (useful for searching for the next uncommented line in tables and in assembly code). -- Disclaimer: My company neither knows nor cares what I say. .//.