From mboxrd@z Thu Jan 1 00:00:00 1970 From: bakul@bitblocks.com (Bakul Shah) Date: Wed, 01 Nov 2017 14:04:20 -0700 Subject: [TUHS] basic tools / Universal Unix In-Reply-To: Your message of "Wed, 01 Nov 2017 14:37:42 -0600." <201711012037.vA1KbgHZ008984@freefriends.org> References: <20171030141645.6F81C18C0E7@mercury.lcs.mit.edu> <20171101140518.98D10212F3@orac.inputplus.co.uk> <201711011642.vA1Gg0bX016908@freefriends.org> <20171101171700.D8E0721937@orac.inputplus.co.uk> <201711011806.vA1I60bL025852@freefriends.org> <0B657714-7E99-4063-9C09-45EC2A9BCD23@bitblocks.com> <201711012037.vA1KbgHZ008984@freefriends.org> Message-ID: <20171101210435.9AE27156E7D7@mail.bitblocks.com> On Wed, 01 Nov 2017 14:37:42 -0600 arnold at skeeve.com wrote: arnold at skeeve.com writes: > Bakul Shah wrote: > > > I think what Ralph wants is something like "LINES=1 vi" > > but without clearing the screen so that commands that > > are cursor relative can work. rlwrap and readline don't > > edit the current line in the file, only the command input. > > OK, that I can understand. It's ages since I played with > readline, but I think you can preload the buffer it works on > (bash does that, no?) so ed + readline could be made to work > that way. Editing that way seem is bass ackwards -- probably more code would needed to interface with readline than just implementing it in ed. As a one line version requires just line movement commands, there is no reason why you can't use full power of vi through a narrow window - such as d} to delete to the end of para and have the next line dispayed. Readline wouldn't help there. And readline weighs in @ 28K LOC to ed's 3.5K (on plan9 it is under 1.6K). > I already have too many side projects on my plate, or I'd try it. :-) Ditto!