sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Scott Schwartz <>
Subject: new sam for unix
Date: Thu, 25 May 2000 15:37:07 -0400	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 884 bytes --]

Hi all,
  Rob Pike was kind enough to send me the source for the new
sam, and I've gone through and made the changes necessary to get
it to compile under unix.  I found one bug in the process, so 
I hope everyone else will look things over carefully too.

The changes: 
- replaced anonymous unions with ansi-std ones.
- used a plan9-flavor print library instead of stdio (mostly).
- the sam err file in tmp is now given a unique name, to
   avoid symlink races.  mktemp used where necessary.
- all plumbing is stubbed out.  maybe we can revisit this after the
   next edition of plan 9 is published.

This version appears to work with samterm, but it does exercise what I
think is a problem with the X11 version of that.  If I create a large
file, all lines the same length, and make a global substitution, and
then repeatedly undo and redo, samterm appears to miss some

[-- Attachment #2: sam.tar.gz --]
[-- Type: application/octet-stream, Size: 192512 bytes --]

                 reply	other threads:[~2000-05-26 19:14 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).