sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: (Paul Jackson)
To:, Bengt Kleberg <>
Subject: Re: Samx - one more time ...
Date: Wed, 26 Apr 2000 16:25:47 -0400	[thread overview]
Message-ID: <> (raw)

Bengt wrote:
|> I am (very low-key) maintaining sam as it is, ...

and grateful we are for your work

|> Perhaps we complement each other? I maintain sam as it is,
|> you enhance it?

As I concluded in a private email thread that branched
off this public thread:

    Seems like what I am dreaming of is really
    yet-another-editor, likely using sam+samx as a code base,
    and for its core design element integrating the gui and
    command interface, but undergoing some major surgery, aimed
    entirely at X11 environments.

    Looks like I should choose yet-another-name for such a
    beast, if it ever gets past being my private toy.  I will
    read the license that comes with Sam again, to be sure I
    am fitting comfortably within its terms.

Not sure if I will go down this path or not - if you're
uncomfortable with it, let me know.

I might call it 'tam' -- because 't' comes after 's',
and because I used to work with a fine chap called
Sam Tam.

I won't rest till it's the best ...	   Software Production Engineer
Paul Jackson (; 3x1373

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

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

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