Contribution: draft Unix manual pages for eclipse(1), tkeclipse(1), jeclipse(1) and tktools(1)

From: <john_at_cs.york.ac.uk>
Date: Fri 17 Jan 2003 02:16:44 PM GMT
Message-Id: <E18ZXIh-0000o0-00@minster.cs.york.ac.uk>

('BINARY' encoding is not supported, stored as-is)

`Bug' report for ECLiPSe
------------------------

>The ECLiPSe banner with the version number and configuration
>(unless visible in the script):

5.5_46

>Machine type:

Sun Sparc, PC


>Operating system name and version number:

Solaris 2.8, Slackware Linux 8.1 etc

>If graphics is involved, X version number, X server type and window manager:


>Your .eclipserc and ECLIPSE... environment variables, if used:


>A script which causes the bug to appear, enhanced by comments where
>necessary (start from the ECLiPSe banner unless the option -e is used):

>Comments

Not really a bug, but Unix users are used to having traditional format
manual pages for the available commands, library routines, special
files, file formats etc. I've writted *draft* manual pages roughly in
the style specified by man(7) (i.e. manual page `man' from section 7 of
the Unix manual) on Solaris and Linux and am enclosing them as
attachments to this E-mail - please accept them as contributions to your
project.

A Unix manual page isn't meant fully to document the command (or other
entity) it describes, merely to act as an advert for the full user
manual and any other documentation, and to stand as a quick reference.
Various automatic systems on Unix scan the manual pages to build
documentation indexes etc.

You'll want to correct and improve them, I'm sure.
-- 

John A. Murdie
Experimental Officer (Software)
Department of Computer Science
University of York
England

Received on Fri Jan 17 14:23:29 2003