Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcarl.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcc3!sdcarl!rusty
From: rusty@sdcarl.UUCP (rusty c. wright)
Newsgroups: net.emacs
Subject: GNU emacs documentation
Message-ID: <186@sdcarl.UUCP>
Date: Sun, 12-May-85 01:48:30 EDT
Article-I.D.: sdcarl.186
Posted: Sun May 12 01:48:30 1985
Date-Received: Mon, 13-May-85 07:49:05 EDT
Reply-To: rusty@sdcarl.UUCP (Rusty Wright)
Organization: Computer Audio Research Lab, UCSD, San Diego, Calif.
Lines: 39

I came upon the following method to make up documentation for emacs
until rms distributes the real stuff.  It appears that there is a
complete description of the emacs commands in the DOCSTR file in the
etc directory.  But the DOCSTR file isn't in a form that you want to
read via "more", "lpr", etc.  I wrote the following little C program
to filter it through:

main() {
	register int	ch;

	while ((ch = getchar()) != EOF) {
		if (ch == 037)
			printf("\n\\subsection*{");
		else
			putchar(ch);
	}
}

Then run it with

	a.out < DOCSTR > doc.tex

(You'll need to add the version number onto the DOCSTR file name.)
Then take the editor and add the closing } to all of the \subsection
lines, add the appropriate \documentstyle..., \begin{document} and
\end{document} lines, and then run it through LaTeX and voila!  There
are a couple of spots that could use a {description} environment.
(Note to troff users: substitute .SH for the \subsection*{.)

The next step is to make a file that has the key bindings/mappings.
For this i used the command

	grep '(define-key' simple.el loaddefs.el > ~/ keys.tex

Unfortunately the keys.tex file will require a fair amount of manual
editing to get it into a useful form though.
-- 
	rusty c. wright
	{ucbvax,ihnp4,akgua,hplabs,sdcsvax}!sdcarl!rusty