Date: Sun, 29 Jan 1995 17:42:50 +0900 From: Stephen Turnbull To: djgpp AT sun DOT soe DOT clarkson DOT edu Subject: Wild Crashes? hmmm... >>>>> On Sat, 28 Jan, peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock) said: > 2. when i run info and get to the end of the page by using the > cursor keys, it locks up. Bob> I recommend forgetting the info program and using emacs to read the docs. If you fell emacs is too large, get jed386, it can read the info files just fine. -- Dong Liu ...which can be found at amy.tch.harvard.edu:/pub/jed. Definitely get jed386; some of the info files are big enough to run into memory constraints under real-mode jed, let alone if you're editing other large buffers at the same time. If you are tempted to use jed as an editor (it's rather big to be considered a standalone info reader :), be warned: jed is only approximately GNU-emacs-like, and there are some gotchas that can cause data lossage. In particular, many keybindings that are "kills" under emacs are "deletes" under jed, so they do not get appended to the kill buffer; as far as I can tell the kill buffer in jed is a single buffer, not a ring, so a new kill will flush the previous one. SLang looks like a usable extension language (of course, it's full programming system in itself, but that's not what I want it for). But IMHO it is only faintly C-like (Pascal is a far better approximation to C), and EmacsLISP functions and programming experience do not translate to SLang easily at all. The docs also have a long way to go before they look like the EamcsLISP manual ;-)