9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: Re[2]: Re[2]: [9fans] sam vs acme
Date: Thu, 19 Jul 2001 16:25:55 +0100	[thread overview]
Message-ID: <2256914570@snellwilcox.com> (raw)

Hi,

Fraid its more complex than that.

rc does exist (in the form of rcsh.exe) and sam uses it for running external
commands
eg. ",|tr -d \015" :-). I even have Byrons rc running under cygwin which averts
weird problems I had
with Win16 programs not tidying up on exit and confusing rcsh.exe.

I beleive however that in the implementation of the pipe between sam & samterm
the remote
execution ability got sacrificed.

A student here managed to get an Xfree86 server to run under cygwin and I
compiled sam/samterm/9wm/9term under that for a giggle it works but  is just too
unhygienic

-Steve


____________________Reply Separator____________________
Subject:    Re: Re[2]: [9fans] sam vs acme
Author: 9fans@cse.psu.edu
Date:       19/07/01 16:00

> I only wish the Windows version understood sam -r...

Is it because of a lack of rsh?  Because one of the things I do
with sam is tweak it to use ssh instead. I imagine the same could
be done easily enough with the windows version.

There isn't anything about the underlying structure of sam -r that
would fail under windows right?  From what I remember of the book
Rob co-authored (Practice of Programming) they talk a lot about how
to get around things like endian problems.

Jim





----------------------------------------------------------------------
The contents of this communication are confidential to the normal user of
the email address to which it was sent.  If you have received this email
in error, any use, dissemination, forwarding, printing or copying of this
email is strictly prohibited.  If this is the case, please notify the sender
and delete this message.
----------------------------------------------------------------------



                 reply	other threads:[~2001-07-19 15:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2256914570@snellwilcox.com \
    --to=steve.simon@snellwilcox.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).