From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <1239082320.2778.20.camel@katy-laptop> <140e7ec30904070053p20e60905y19a031837edc1931@mail.gmail.com> <3AB58E51F3A5C561C4B065E3@192.168.1.2> <140e7ec30904070731v7365aea2o7753be79bbaab8ea@mail.gmail.com> <13426df10904070809v2c536289vfa8485aabef7f2f0@mail.gmail.com> Date: Tue, 7 Apr 2009 15:57:57 -0400 Message-ID: <3aaafc130904071257h4c7004c2ub7111f09055a9d8c@mail.gmail.com> From: "J.R. Mauro" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] a bit OT, programming style question Topicbox-Message-UUID: d52a3dc2-ead4-11e9-9d60-3106f5b1d025 On Tue, Apr 7, 2009 at 2:21 PM, Eris Discordia w= rote: > I see. But seriously, readline does handle bindings and line editing for > bash. Except it's a function instead of a program and you think it's a ba= d > idea. The man page *does* say it's too big and slow. So does the bash manpage. And getting readline to do anything sane is about as fun as screwing around with a terminfo file. > > --On Tuesday, April 07, 2009 10:31 PM +0800 sqweek wro= te: > >> 2009/4/7 Eris Discordia : >>>>> >>>>> Keyboard >>>>> bindings for example; why couldn't they be handled by a program that >>>>> just does keyboard bindings + line editing, and writes finalized line= s >>>>> to the shell. >>> >>> Like... readline(3)? >> >> =A0No. >> -sqweek >> > > > > --On Tuesday, April 07, 2009 8:09 AM -0700 ron minnich > wrote: > >> On Tue, Apr 7, 2009 at 12:28 AM, Eris Discordia >> wrote: >> >>> >>> Like... readline(3)? >> >> one hopes not. >> >> ron >> > > > > > >