sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Alex Danilo <>
Subject: Re: Samx - one more time ...
Date: Tue, 25 Apr 2000 06:59:10 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Paul Jackson) wrote:
>I continue to work in my spare time (slowly) adding features
>to sam+samx.
>I worry that I might be "splintering" sam - creating a fork of
>development off the main stream.  But so far as I can tell, no
>one else is touching the code.

I'm sure there are many people 'touching' the code, it's just that
there is no formalised source project base on the 'sam' distribution,
it's just an 'as-is' release.

From what I've seen, there is a huge reluctance by the developers
(i.e. Rob) to add any 'features'.  This is in line with the original
interface which is mouse for movement, and keyboard for entry only.
It is minimalistic, and is meant to be so - things like auto-indent
were never meant to be in 'sam', it isn't a user-interface ideal.

The released code was supposed to be just that - a release, and if
you want to add stuff to it, then go for it, but it won't be part
of 'sam' proper.  I offered some simple mods to do implement cursor
keys a while ago in the comp.os.plan9 list, but no-one wanted it.

So, what I'm saying is that anything that changes 'sam' from the Lucent
release makes it not sam.  So, if you want to add 'features', that
should be done as some alternate project, like 'samx' which is of
course sam with Xtensions.

>I am seeking to make this work available on SGI's Open Source
>Server, - perhaps within the next month or

I'd honestly consider creating a new project on SourceForge, as
that is (sort-of) vendor-neutral, and it can be maintained after
you leave SGI.

>   4) debug loss of samterm/sam sync.

This, as far as I can see is the only bad bug which exists in the
Lucent release.  If you open a big batch of files, and do something


to nuke carriage returns in all your source files, sam and samterm
get out of sync and barf.  This is a really nasty bug, and the Windows
version created by Sean Quinlan doesn't seem to exhibit it - so I
guess it may have been fixed internally to the Labs, but never made
it out into the public release.

By all means add new features if you wish, but it should be made a
distinct stream of development from that which we know as 'sam'.

Perhaps we could call it son-of-sam:-)

Alex Danilo <>
PO Box 333 Forestville NSW 2087 +61-2-9975-2297

  reply	other threads:[~2000-04-26 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-21  2:08 Paul Jackson
2000-04-25 10:59 ` Alex Danilo [this message]
2000-04-25 12:42 rob pike
2000-04-25 14:38 Bengt Kleberg
2000-04-26 20:25 Paul Jackson
2000-04-26 22:26 Paul Jackson
2000-04-26 22:34 Paul Jackson
2000-04-27  8:04 Bengt Kleberg
2000-04-27 20:17 Russ Cox

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