9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] samterm: plumb read error: interrupted
Date: Mon, 21 Oct 2002 10:07:20 -0400	[thread overview]
Message-ID: <61efb4dfc998b7c6896012e5059a0400@plan9.bell-labs.com> (raw)

> almost all times after using Sam for editing some file(s) ...
> samterm: plumb read error: interrupted
> and I get shell prompt only after hitting DEL.

all you need to do is remove the print statements
from libplumb and samterm that complain when
the connection dies.

you've got a shell prompt, it's just that some output
has been printed since the prompt.  typing del doesn't
actually kill anything (there's nothing to kill).  typing
enter would get you another prompt too.  or typing
"echo hello world" would get you hello world and
a prompt.

the point is it's harmless.



             reply	other threads:[~2002-10-21 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 14:07 Russ Cox [this message]
2002-10-22  1:30 ` Andrey S. Kukhar
  -- strict thread matches above, loose matches on Subject: below --
2002-10-14 22:28 Andrey S. Kukhar
2002-10-21  9:07 ` Douglas A. Gwyn

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=61efb4dfc998b7c6896012e5059a0400@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).