rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: 'sam' available from research.att.com!
Date: Wed, 18 Nov 1992 13:16:09 -0500	[thread overview]
Message-ID: <9211181816.AA10576@netapp.netapp.com> (raw)

>For the interested, I have a small set of modifications[...]

I have also hacked sam in a couple of ways:

1) I make command window appear on the left by default. i.e.,
the window is tall&thin, not short&fat. Since most commands
are only a couple of letters long (/foo, x/foo/c/bar, etc.)
it means that you can have a lot more history visible in the
editor than with the short&fat command window. The occasional
long line doesn't bother me.

2) I hacked the selection-positioning code so that that
when the current selection is skipped to, that selection
is in the middle of the screen rather than right at the top.
This makes it a lot easier to take in the context of the
thing you just skipped to. (I dunno, maybe I'm used to it
because vi does it that way.)

3) I fixed an array indexing error in main which causes sam
to dump core when you give it a bad option. (sigh) In general,
I have found that sam likes to dump core all too frequently
under SunOS. Some of the dumps seem to be related to synchronization
problems between sam & samterm: as soon as one goes out of
whack it panics & dumps core.

All these fixes are 1 line fixes, btw, which is nice. Modifying
sam to use, for example, ctags, might be more of a challenge.


             reply	other threads:[~1992-11-18 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-11-18 18:16 Byron Rakitzis [this message]
1992-11-18 18:27 ` Chris Siebenmann
1992-11-18 20:36 ` Byron's comments John Mackin
  -- strict thread matches above, loose matches on Subject: below --
1992-11-18 17:20 'sam' available from research.att.com! Arnold Robbins
1992-11-18 23:29 ` Christopher JS Vance
1992-11-18 17:17 rsalz
1992-11-18 16:31 Arnold Robbins
1992-11-18 17:35 ` Chris Siebenmann

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=9211181816.AA10576@netapp.netapp.com \
    --to=byron@netapp.com \
    --cc=cks@hawkwind.utcs.toronto.edu \
    --cc=rc@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).