Return-Path: owner-linux-activists@Niksula.hut.fi
Return-Path: <owner-linux-activists@Niksula.hut.fi>
Received: from joker.cs.hut.fi by hydra.Helsinki.FI (4.1/SMI-4.1/36)
	id AA07578; Tue, 19 Jan 93 01:59:57 +0200
Received: from joker.cs.hut.fi by niksula.hut.fi id <61942-4>; Tue, 19 Jan 1993 01:58:54 +0200
From: "Linux Activists" <linux-activists@Niksula.hut.fi>
To: "Linux-Activists" <linux-activists@Niksula.hut.fi>
Reply-To: "Linux-Activists" <linux-activists@Niksula.hut.fi>
X-Note1: Remember to put 'X-Mn-Key: DOC' to your mail body or header
Subject: Linux-Activists - Channel DOC digest. 93-0-18-23:5
X-Mn-Key: DOC
Sender: owner-linux-activists@Niksula.hut.fi
Message-Id: <93Jan19.015854eet.61942-4@niksula.hut.fi>
Date: Tue, 19 Jan 1993 01:58:53 +0200
Status: RO
X-Status: 


Topics:
	 Re:  No known channel name given


----------------------------------------------------------------------

From: ashtray@yoyo.cc.monash.edu.au (John Newnham)
Subject: Re:  No known channel name given
Date: Tue, 19 Jan 1993 01:02:47 +0200


mdw says "you can do a search for '{\bf ...}'" to get info on particular
commands.  This sounds like an ideal place for a table/index.  The idea
would be to _avoid_ writing and article "Some common unix commands and
expressions", but to reference the reader to existing writing (which is probably more complete
anyway).  I imagine this would not be too hard in LaTeX?
  - just the $0.02 of someone who has never used any flavour of TeX :-)
ashtray



------------------------------

End of DOC Digest
*****************
-------
