sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Ed Kubaitis <ejk@uiuc.edu>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: Applying old samx patch to newer sam?
Date: Fri, 24 Mar 2000 07:32:33 -0500	[thread overview]
Message-ID: <38DB6061.3F9125E9@uiuc.edu> (raw)
In-Reply-To: <200003231701.JAA99286@sam.engr.sgi.com>

Hi,

AFAIK, the failed pieces in the samx patch can be ignored. As
I recollect, the failed pieces were applying changes which the
new (circa 1993) libXg provided in a different way/place. I've
been using versions of sam + samx patch since then, building it
most recently a few months ago for Redhat Linux 6.1 and have not
seen any problems.

Ed
--------------------------
Ed Kubaitis (ejk@uiuc.edu)
CCSO - University of Illinois - Urbana-Champaign


Paul Jackson wrote:
> 
> Bengt wrote:
> |> Please note that I am trying to 'maintain' sam-9libs.
> 
> Thank-you and bless you!
> 
> |> I rather not include this [samx] in sam-9libs.
> 
> That's fine - I wasn't expecting sam-9libs to accomodate
> samx.  I acknowledge that samx is "controversial".
> 
> I should have been clearer that I was more looking
> for feedback from other samx users as to  whether
> I should worry about the failed chunk of the patch.
> 
> |> 1 sam is supposed to be mouse driven, not keyboard driven.
> 
> It is common-place for the finest tools to be written
> with a focused vision, and then for users to turn around
> and do the darndest things with them.  Life is good.
> 
> =======================================================================
> I won't rest till it's the best ...        Software Production Engineer
> Paul Jackson (pj@sgi.com; pj@usa.net) 3x1373 http://sam.engr.sgi.com/pj


  reply	other threads:[~2000-03-25  6:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-23 17:03 Paul Jackson
2000-03-24 12:32 ` Ed Kubaitis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-23 10:26 Bengt Kleberg
2000-03-23  3:30 Paul Jackson

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=38DB6061.3F9125E9@uiuc.edu \
    --to=ejk@uiuc.edu \
    --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).