sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: matty@cs.su.oz.au (James Matthew Farrow)
To: bekl@dragos.ose.enea.se
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: 9term for Solaris2
Date: Wed, 1 Jun 1994 22:25:15 -0400	[thread overview]
Message-ID: <19940602122515.21383.frobozz@staff.cs.su.oz.au> (raw)

    Date: Tue, 31 May 94 19:34:13 +0200
    From: bekl@dragos.ose.enea.se (Bengt Kleberg)
    Message-Id: <9405311734.AA28226@dragos.enea.se>
    To: matty@cs.su.oz.au
    Subject: 9term for Solaris2
    Content-Length: 349
    
    Greetings,
    
    Since the beginning of this year I have been a happy 9term user. Very
    nice interface and no crashes.
    
    With the advent of Solaris2 on our network I find that sam/samterm provided
    Makefiles for solaris2, but, alas, 9term only has sun (as in sunos4).
    
    Do you know what Makefile that would be 'best' to use for Solaris2?
    
    Best Wishes, Bengt

I've done a bit more work on 9term.  There is a
distribution which some might like to look at available as
ftp://ftp.cs.su.oz.au/matty/unicode/9term.1.5.1.tar.Z This includes a
Makefile for Solaris as well as some improved handling of interrupts
and echo/noecho modes.

If anyone can tell me a way of getting read notification from
inside a stream to a user program I would be grateful.  (John Mackin
suggested poking the bits in the kernel but I'm loathe to try that ;-).
The documentation we have with Solaris is not that helpful.  It seems
to hit that it's possible but it also implies that it's impossible.

					Matty.
--
James Matthew Farrow                    | "For in that moment I beheld the ruin
matty@cs.su.OZ.AU                       | of my existence.  My world fell dark
Basser Department of Computer Science   | and my life became a shallow dream.
Sydney University - FAX: +61 2 692 3838 | `Odi et amo. Excrucior.'" - Tlindah



                 reply	other threads:[~1994-06-02  2:31 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=19940602122515.21383.frobozz@staff.cs.su.oz.au \
    --to=matty@cs.su.oz.au \
    --cc=bekl@dragos.ose.enea.se \
    --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).