sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: "Chaotrope" <chaotrope@jps.net>
To: <Jim.Robinson@Stanford.Edu>, "Aharon Robbins" <arnold@gnu.org>
Cc: <sam-fans@hawkwind.utcs.toronto.edu>
Subject: Re: 9term under Linux?
Date: Mon, 1 Feb 1999 19:25:45 -0500	[thread overview]
Message-ID: <199902020026.QAA13600@repop2.jps.net> (raw)

On 99.01.27

> James A. Robinson <Jim.Robinson@Stanford.Edu>

replied to

>  Aharon Robbins <arnold@gnu.org>
> Cc: sam-fans@hawkwind.utcs.toronto.edu

on the

> Subject: Re: 9term under Linux? 

saying
 
> I've got 9term, 9wm, 9menu, wily, sam, and rc working on my 
> system. I really love the interface! =)
> 
> Jim

This plan9 interface that Jim has is exactly what started
me a few months back investigating getting a Linux system even 
tho I swore a number of years ago that I'd no longer spend my 
own money on computer stuff (I've got two closets full of junk 
already!).

I read some articles of Aharon's (Arnold's) in 1995 "Linux Journal"
and had the old R. Pike 'sam' article, and have been 'window shopping'
(where in this case 'window' has nothing to do with Microsoft) with
the intent of maybe putting together some no name x86 system.

So when I read here that Arnold has difficulties, I think, Maybe I'm
over my head, if *HE* has problems, what am I going to run into?! 

Thus far, Debian is the only Linux dist that has p9 emu binaries at
its ftp site (Red Hat has 'sam' only). The NeBSD/FreeBSD people
even have a 'plan9' directory at their ftp sites, just like an
'editors' and  a 'TeX' directory. So I'm leaning toward BSD rather
than Linux just because that indicates to me that these people are
"thinking" along those lines.

So my question is, e.g., Jim, what are you using? Is there a general
consensus on ease of installation, whatever, getting this p9 'look and
feel grafted on top of what version of Unix? Are there known problems
with (obviously) RedHat vs. whatever?

TIA,              - kim

BTW, Aharon/Arnold: I enjoyed your LJ articles enough that I'm
planning to get your AWK book just because I assume it will be well
written also.


             reply	other threads:[~1999-02-02 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-02  0:25 Chaotrope [this message]
1999-02-02  2:01 ` James A. Robinson
  -- strict thread matches above, loose matches on Subject: below --
1999-02-03  7:19 Bengt Kleberg
1999-02-02 20:41 Chris Siebenmann
1999-02-02  6:49 Aharon Robbins
1999-01-28 12:28 Bengt Kleberg
1999-02-02 19:11 ` Mark H. Wilkinson
1999-01-28 11:33 Aharon Robbins
1999-01-28  7:45 Bengt Kleberg
1999-01-26 15:35 Aharon Robbins
1999-01-27 22:24 ` James A. Robinson

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=199902020026.QAA13600@repop2.jps.net \
    --to=chaotrope@jps.net \
    --cc=Jim.Robinson@Stanford.Edu \
    --cc=arnold@gnu.org \
    --cc=sam-fans@hawkwind.utcs.toronto.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).