From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue,  7 Apr 2009 19:21:20 +0100
From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <A297371273CD8D67A21A921E@[192.168.1.2]>
In-Reply-To: <140e7ec30904070731v7365aea2o7753be79bbaab8ea@mail.gmail.com>
	<13426df10904070809v2c536289vfa8485aabef7f2f0@mail.gmail.com>
References: <1239082320.2778.20.camel@katy-laptop>
	<140e7ec30904070053p20e60905y19a031837edc1931@mail.gmail.com>
	<3AB58E51F3A5C561C4B065E3@192.168.1.2>
	<140e7ec30904070731v7365aea2o7753be79bbaab8ea@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [9fans] a bit OT, programming style question
Topicbox-Message-UUID: d4fe2232-ead4-11e9-9d60-3106f5b1d025

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 bad
idea.

--On Tuesday, April 07, 2009 10:31 PM +0800 sqweek <sqweek@gmail.com> wrote:

> 2009/4/7 Eris Discordia <eris.discordia@gmail.com>:
>>>> Keyboard
>>>> bindings for example; why couldn't they be handled by a program that
>>>> just does keyboard bindings + line editing, and writes finalized lines
>>>> to the shell.
>>
>> Like... readline(3)?
>
>  No.
> -sqweek
>



--On Tuesday, April 07, 2009 8:09 AM -0700 ron minnich <rminnich@gmail.com>
wrote:

> On Tue, Apr 7, 2009 at 12:28 AM, Eris Discordia
> <eris.discordia@gmail.com> wrote:
>
>>
>> Like... readline(3)?
>
> one hopes not.
>
> ron
>