From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from postman.osf.org ([130.105.1.152]) by hawkwind.utcs.toronto.edu with SMTP id <2714>; Wed, 17 Jun 1992 16:21:57 -0400 Received: from earth.osf.org by postman.osf.org (5.64+/OSF 1.0) id AA17935; Wed, 17 Jun 92 16:21:44 -0400 Received: by earth.osf.org (5.64/4.7) id AA24775; Wed, 17 Jun 92 16:21:43 -0400 Date: Wed, 17 Jun 1992 16:21:43 -0400 From: rsalz@osf.org Message-Id: <9206172021.AA24775@earth.osf.org> To: rc@hawkwind.utcs.toronto.edu Subject: Revised editline library 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 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.