sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: pete@minster.york.ac.uk (Pete Fenelon)
To: Werner Lemberg <A7621GAC@helios.edvz.univie.ac.at>
Cc: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: samx2 and sam 3/12/93
Date: Thu, 18 Aug 1994 05:21:39 -0400	[thread overview]
Message-ID: <swordfish.777202293@minster.york.ac.uk> (raw)

>
>What is samx2 and where can I find it ?

Samx2 is a set of patches which give some keyboard customisation facilities
to sam. The author is at uiuc.edu, but I can't remember the ftp site where
the patch lives; if the worst comes to the worst I could mail you a copy. 

>
>Another question: Has anybody ported sam(term) to Linux? After some tries
>I succeeded in porting, but I'm not familiar with UNIX programming, and
>indeed I really don't know exactly what I've done :-)

Yes -- I have done a working port, but there's still one minor problem with
named pipes that means I have to start sam up in a slightly nonstandard way!
I started from the defines for IRIX -- the Silicon Graphics OS is one of the
closest to POSIX and therefore Linux that I've ever come across -- and fixed
it on that basis.

I think the startup bug is probably due to the interaction of some of the
patches I have in my sam; I'll investigate further. Basically, I have to
chuck a carriage return down the named pipe before Sam will do anything...
however, from then on it's perfect!

pete
--
Peter Fenelon - Research Associate - High Integrity Systems Engineering Group,
Dept. of Computer Science, University of York, York, YO1 5DD (+44/0)904 433388



             reply	other threads:[~1994-08-18  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-08-18  9:21 Pete Fenelon [this message]
1994-08-18 10:34 ` Markus Friedl (CIP 92)
1994-08-18 13:01   ` Mark C. Chu-Carroll
  -- strict thread matches above, loose matches on Subject: below --
1994-08-18  6:40 Werner Lemberg
1994-08-18 17:46 ` Norman Ramsey
1994-08-17 14:43 hc05

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=swordfish.777202293@minster.york.ac.uk \
    --to=pete@minster.york.ac.uk \
    --cc=A7621GAC@helios.edvz.univie.ac.at \
    --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).