ccm@cs.cmu.edu (Christopher McConnell) (10/16/90)
[ I mis-cross-posted the first of these to gnu.emacs.sources which is meant for sources only. gnu.emacs.sources is not suppose to get announcements of source code. They belong in comp.emacs or gnu.emacs.help. But since the message with errors ended up in gnu.emacs.sources, it's fair to post the correction as well. thanx -len (moderator of gnu.emacs.announce) ] I messed up the pathname. Here is the correct information. Version 3.0 of the EMACS to LISP interface ILISP is now available. If you have gotten ILISP prior to today, you should get the new version. The new version fixes a number of bugs and is much improved in its handling of packages, symbol completion, compiling and initialization. FEATURES: +Support for multiple LISP dialects including Lucid, Allegro and CMU even at the same time. +Dynamically sized pop-up windows that can be buried and scrolled from any window. +Packages are properly handled including the distinction between exported and internal symbols. +Synchronous, asynchronous or batch eval and compile of files, regions, definitions and sexps. +Arglist, documentation, describe, and macroexpand. +Completion of filenames and LISP symbols. +Find source through LISP with tags as a backup. +Edit the callers of a function. +Trace/untrace a function. +Esc-q works properly on paragraphs in comments, strings and code. +Find unbalanced parentheses. +Super brackets. +Handles editing, entering and indenting full LISP expressions. +Next/previous and similar history mechanism compatible with comint. +Handles LISP errors. +Result histories are maintained in the inferior LISP. +Does not create spurious symbols. HOW TO GET IT If you do start using the package, please send mail to ccm@cs.cmu.edu so that I can keep a mailing list of users. Any comments or code are also welcome. You can anonymously ftp the source files from CMU: - Ftp to a.gp.cs.cmu.edu (128.2.242.7) or any other SCS machine. - cd /afs/cs/user/ccm/src/gnu/ilisp/ Don't try to cd to or ls any of the intermediate directories; go straight to the subdirectory. The CMU security mechanisms will block you from accessing any of the other directories while you are doing anonymous accesses. - get ilisp.tar.Z or mget README popper.el comint.el comint-ipc.el ilisp.el ilisp-*.lisp Of course, anyone with AFS access at CMU, Dartmouth, Michigan, MIT, Mt. Xinu or Transarc can just cd to the directory and copy what they want. ONCE YOU HAVE IT: 1) uncompress ilisp.tar.Z; tar xf ilisp.tar 2) Read the start of ilisp/ilisp.el for the site and .emacs information. -- Chris McConnell "Sometimes noise is significant."--William Hewlett
tower@AI.MIT.EDU (Leonard H. Tower Jr.) (10/16/90)
Chris at al. List gnu-emacs-source (aka newsgroup gnu.emacs.sources) is for the posting of actual sources including patches and updates. Please don't announce source there. This is so people can automatically archive the list/newsgroup and and get only source in their archives. Please announce packages in help-gnu-emacs/gnu.emacs.help. Please discuss them there as well. thanx -len (aka *gnu*-request@prep.ai.mit.edu) Here's the charter for gnu-emacs-sources/gnu.emacs.sources again: ---------------------------------------------------------------------- * gnu-emacs-sources-request@prep.ai.mit.edu to subscribe to gnu-emacs-sources ** gnUSENET newsgroup: gnu.emacs.sources ** Gnu Emacs source code to: gnu-emacs-sources@prep.ai.mit.edu This list/newsgroup will be for the posting, by their authors, of lisp and C sources and patches that improve GNU Emacs. Its contents will be reviewed by FSF for inclusion in future releases of GNU Emacs. Please do NOT discuss or request source code here. Use help-gnu-emacs/gnu.emacs.help for those purposes. This allows the automatic archiving of sources posted to this list/newsgroup. Please do NOT post such sources to any other GNU mailing list (e.g help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's up to each poster to decide whether to cross-post to any non-gnUSENET newsgroup (e.g. comp.emacs or vmsnet.sources). Please do NOT announce that you have posted source code to gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep up with sources will read this list/newsgroup. It's up to each poster to decide whether to announce a gnu.emacs.sources article in any non-gnUSENET newsgroup (e.g comp.emacs or comp.sources.d). If source or patches that were previously posted or a simple fix is requested in help-gnu-emacs, please mail it to the requester. Do NOT repost it. If you also want something that is requested, send mail to the requester asking him to forward it to you. This kind of traffic is best handled by e-mail, not by a broadcast medium that reaches thousands of sites. If the source is very long (>10k bytes) send mail offering to send it. This prevents the requester from getting many redundant copies and saves network bandwidth. ---------------------------------------------------------------------- enjoy -len