Re: [dev] [st] goals / non-goals for st?

On Fri, Oct 30, 2009 at 5:34 PM, Aled Gest <himselfe_AT_gmail.com> wrote:
> In terms of doing so without consuming a PTY or spawning a child
> process, none that I know of.
>
> Are you suggesting that we shouldn't develop new software because no
> existing software does what we want? I've seen no strict definition
> specifying how a terminal emulator must communicate with other
> processes. Whether it acts like a host process spawning a child and
> communicating through a PTY, or gets spawned as a child process itself
> reading and writing directly through pipes, it's still a terminal
> emulator.

I'm suggesting that if you want two clearly distinct jobs done, and
they share a lot of similar code, you extract the duplicate code into
a library and then write two applications against that library. In
this case, we should wind up with st, which consumes PTYs and emulates
a terminal, and we should wind up with your thing, which still sounds
closer to dzen than a term app.

Loading up application code with disparate functionality isn't any good.

-- 
# Kurt H Maier