rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: rsalz@osf.org
To: rc@hawkwind.utcs.toronto.edu
Subject: Revised editline library
Date: Wed, 17 Jun 1992 16:21:43 -0400	[thread overview]
Message-ID: <9206172021.AA24775@earth.osf.org> (raw)

I've spent some time working on the editline library.
Thanks to Simmy for his help and permission.  The README
is attached.  Source is on ftp.uu.net, ~ftp/tmp/editline.shar.Z;
email me if you can't FTP.  Once I get feedback I'll post it to the
net.

To use it, enable the READLINE #define in rc (not EDITLINE).
	/r$
This is a line-editing library.  It can be linked into almost any
program to provide command-line editing and history recall.

It is call-compatible with the FSF readline library, but it is a
fraction of the size (and offers fewer features).  It does not use
standard I/O.

Configuration is done in the Makefile.  Type "make testit" to get
a small slow shell for testing.

An earlier version was distribution with Byron's rc.  Principal
changes over that version include:
	Faster.
	About 10% smaller.
	Written in K&R C, but ANSI compliant (gcc all warnings)
	Propagates EOF properly; rc trip test now passes
	Doesn't need or use or provide memmove.
	More robust
	Calling sequence changed to be compatible with readline.
	Test program, new manpage, better configuration

Enjoy,
	Rich $alz
	<rsalz@osf.org>

 Copyright 1992 Simmule Turner and Rich Salz.  All rights reserved.

 This software is not subject to any license of the American Telephone
 and Telegraph Company or of the Regents of the University of California.

 Permission is granted to anyone to use this software for any purpose on
 any computer system, and to alter it and redistribute it freely, subject
 to the following restrictions:
 1. The authors are not responsible for the consequences of use of this
    software, no matter how awful, even if they arise from flaws in it.
 2. The origin of this software must not be misrepresented, either by
    explicit claim or by omission.  Since few users ever read sources,
    credits must appear in the documentation.
 3. Altered versions must be plainly marked as such, and must not be
    misrepresented as being the original software.  Since few users
    ever read sources, credits must appear in the documentation.
 4. This notice may not be removed or altered.


                 reply	other threads:[~1992-06-17 20:21 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:
  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=9206172021.AA24775@earth.osf.org \
    --to=rsalz@osf.org \
    --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).