From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p funny
Date: Mon, 25 Jan 2010 18:09:01 +0000 [thread overview]
Message-ID: <B12382B2-5CE1-477A-A0BB-6D3E58771FE6@fastmail.fm> (raw)
In-Reply-To: <88586651cd4c3423e5cb74039d6a1b09@ladd.quanstro.net>
On 29 Dec 2009, at 11:53 pm, erik quanstrom wrote:
> i'm getting spurious echo in 9term on average about 2/3 of
> the time. this example sees the spurious echo every time.
> programs like bash that eat cooked input don't seem to suffer
> the same fate.
Yes, on both OS X and Linux. I find I'm most likely to see it when
using non-p9p tools and setting cooked mode from the menu. Using p9p
tools via ssh also seems to trigger it. (i.e. open 9term, ssh to
another machine, and run 9 rc.)
I actually thought it was a feature of cooked mode, I was quite
surprised to see it not manifest when I tested just now.
next prev parent reply other threads:[~2010-01-25 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 23:53 erik quanstrom
2009-12-30 0:54 ` yard-ape
2010-01-25 18:09 ` Ethan Grammatikidis [this message]
[not found] <<4b3aa4b2.GTlBJSrVHvm2j0KJ%yard-ape@telus.net>
2009-12-30 1:01 ` erik quanstrom
2010-01-10 15:40 ` Lorenzo Vegro
2010-01-10 15:46 ` erik quanstrom
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=B12382B2-5CE1-477A-A0BB-6D3E58771FE6@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).