Xref: utzoo comp.editors:2906 comp.unix.misc:1262
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!math.fu-berlin.de!fauern!unido!mikros!mwtech!martin
From: martin@mwtech.UUCP (Martin Weitzel)
Newsgroups: comp.editors,comp.unix.misc
Subject: Re: If you could have anything in vi ...
Message-ID: <1089@mwtech.UUCP>
Date: 6 Apr 91 00:35:35 GMT
References: <1991Mar18.195343.665@cs.widener.edu> <1991Mar20.203643.26406@convex.com>
Reply-To: martin@mwtech.UUCP (Martin Weitzel)
Organization: MIKROS Systemware, Darmstadt/W-Germany
Lines: 21

In article <1991Mar20.203643.26406@convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>
>    editable commands lines with history and completion.

You can have the first (more or less) if you fall into the habbit to

	1) insert your command lines as normal lines of text
	2) delete them into a named buffer
	3) execute this buffer with the '@'-command
	4) undo the changes, paste back and edit the line and go
	   back to step 2 if the command did not what you wanted.

Well, sounds a bit complicated but is much helpful if you know the command
you type is going to get complex, e.g. some sort of substitute with marked
portions of the matching pattern that must be reused in the replacement ...

Of course, history and completion are not covered by this, but if you
are going to "map" the key-strokes for the above steps 2+3 to an F-keys,
you might also consider to append the command line to a history-file ...
-- 
Martin Weitzel, email: martin@mwtech.UUCP, voice: 49-(0)6151-6 56 83