Fulist

This information file should have been supplied together with the following
files.

   fulist.c          the C source
   fulist.1          the man page
   fulist.shorthelp  the short help file
   fulist.wishlist   the "todo" list.

Version 2.3 fulist should compile without alteration, but it may help to
change the definition of the SHORTHELP macro towards the top of the file so
that it points to wherever the file "fulist.shorthelp" will be installed.
Fulist will initially look for that file under the same pathname as itself
with ".shorthelp" appended, so simply installing "fulist.shorthelp" (or a
link to it) in the same directory as the "fulist" executable should allow
the program to find it.  This file is needed whenever the "help" command
is used.

The source fulist.c should be compiled as usual for curses applications.
This may vary between systems, but a common command is this.

  cc -O -o fulist fulist.c -lcurses -ltermlib

In order to read the man page, either place it in a directory called
/something/man1 and type "man -M/something fulist" or use "nroff -man"
to format it.

I have compiled fulist 2.3 on: SunOS 4.1.3; Solaris 2.5; Red Hat Linux 5.2;
Digital Unix 4.0; IRIX 6.2.  A few systems generated compiler warnings but
most were silent.  It has been reported that fulist 2.3 has been compiled on
AIX 4.2.1.  Previous versions of fulist have been compiled on HP-UX.  If you
use gcc I find it helps if you don't use the -ansi flag.

On some systems (such as SGI) you may want to specify that "char" data
type is signed rather than unsigned.  This is not essential, but if
unsigned characters are used then the "*?"  error marker may appear as
"*255" instead.  The -fsigned-char flag does this if you are using gcc.
This may generate some harmless compiler warnings.

If you have a choice between System V and BSD curses, then please compile
the program so that the System V curses library is used.  For example, on
SunOS 4, this may be done with either of the following commands.

  /usr/5bin/cc -O -o fulist fulist.c -lcurses -ltermlib
  cc -O -o fulist -I/usr/5include -L/usr/5lib fulist.c -lcurses -ltermlib

The second of these is most useful if you wish to use gcc instead of cc.

If you have an amd(8)-based filesystem which mangles path names then you
might find it useful to define the AMD preprocessor macro.  This is an
experimental feature (and might only be useful within my computing lab).
If AMD is defined then fulist will take pathnames starting with the strings
AMDFS (default value "/amd/fs/") and AMDMNT*/ (default value for AMDMNT
is "/amd/tmp_mnt/") and rewrite them so that they begin with AMDADD/
(default value "/fs").  For example:

  /amd/fs/fred/bin            ->  /fs/fred/bin
  /amd/tmp_mnt/server/joe/bin -> /fs/joe/bin

If you redefine these strings it is helpful (though not compulsory) to
define AMDFOOLEN for each macro AMDFOO to be its length.

Fulist 2.3 is "mostly" POSIX.1 (it's a little hard to tell on Sun systems).
The main differences between operating systems are for allocating ptys.

Ian.Collier@comlab.ox.ac.uk