9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tom Lieber <alltom@gmail.com>
To: Bakul Shah <bakul@bitblocks.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a toy terminal for OS X
Date: Sat, 18 Jan 2014 23:52:59 -0500	[thread overview]
Message-ID: <CAProexs4bmgQMcG7EcCFwGARdsuSWeyc-q1212YFq1scDCL_KA@mail.gmail.com> (raw)
In-Reply-To: <5EF77A72-B98A-44D0-A8B0-72F1F3BA8114@bitblocks.com>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Thank you! openpty() is what I needed.


On Wed, Jan 15, 2014 at 1:41 AM, Bakul Shah <bakul@bitblocks.com> wrote:

> Try the
>
> tty
>
> command. You need to connect the shell to a pseudotty. This should also
> fix the rc echo problem.
>
>
> On Jan 14, 2014, at 4:26 PM, Tom Lieber <alltom@gmail.com> wrote:
>
> It seemed like it could be fun and educational, so I started making a
> 9-like terminal for OS X using the native text widget:
>
>   https://github.com/alltom/coolterm
>
> But there are 2 things I’ve had trouble figuring out on my own:
>
> 1) Why do programs like ‘python’ show a prompt in 9term but not in my
> terminal?
>
> 2) Why does bash write your command to stdout? Why doesn’t rc? I use bash,
> so I made it erase the command you typed when you press enter, but that
> appears to be the wrong thing to do with rc.
>
> There’s other stuff in BUGS.md but I feel more confident about those
> things. :)
>
> --
> Tom Lieber
> http://AllTom.com/ <http://alltom.com/>
> http://infinite-sketchpad.com/
>
>
>


-- 
Tom Lieber
http://AllTom.com/
http://infinite-sketchpad.com/

[-- Attachment #2: Type: text/html, Size: 2758 bytes --]

      reply	other threads:[~2014-01-19  4:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  0:26 Tom Lieber
2014-01-15  6:41 ` Bakul Shah
2014-01-19  4:52   ` Tom Lieber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAProexs4bmgQMcG7EcCFwGARdsuSWeyc-q1212YFq1scDCL_KA@mail.gmail.com \
    --to=alltom@gmail.com \
    --cc=9fans@9fans.net \
    --cc=bakul@bitblocks.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).