🚀 go-pugleaf

Submitted-by: flowers@memstvx1.memst.edu
Posting-number: Volume 4, Issue 21
Archive-name: cswing/patch3_00
Patch-to: cswing: Volume 3, Issue 35-52,93,211-218

C Swing is a file and directory management utility.

These are the patches to upgrade from C Swing v3.6.3 to v3.6.4.

New in v3.6.4: 
         o Upgraded MOST to 3.03FM, as described in the header of its main.c.
           (by Foteos Macrides)

** This version will also appear on the US DECUS Fall VMS Systems SIG tape. **

For those not familiar with C Swing, here's an excerpt from the readme file:

SWING is a VAX/VMS utility for displaying the graphic  representation  of  the
VMS  directory  structure  on any terminal that can support the SMG routines -
that is primarily the VT100, VT200 and VT300 series  of  terminals.  SWING  is
designed  to  make  life  easy for a user who frequently performs directory or
file operations within his or her directories.

SWING displays  the  top  eight  directory  levels  of  the  user's  directory
structure.  If  there are more than eight levels a diamond is displayed in the
right-most column indicating that there are non-displayed directories.

SWING has a two level help facility. Quick  menus  are  available  via  the  ?
option. Standard VMS help is available via the H or HELP (LK201) option.

The C language version of SWING was written by Simon Brown, and maintained  by
him  through  V3.2.  It  has  been  modified  by many people, and is currently
maintained primarily by  Mats Akerberg,  Harry Flowers,  and  Foteos Macrides.
Most  of  the documentation  has been rewritten by Chris Butler.  Although the
online help is good, you should read the manual. The re-write was necessary as
he  did  not  have  a Fortran compiler, and felt that C was a more appropriate
language. Also, colleagues required major enhancements, so  the  software  was
started  from  scratch. The result that you see here consumed something in the
region of 400 to 500 hours of spare time. The software has been placed back in
the public domain.

As always, we're interested in any bug reports/enhancement requests that you
might have (not that we promise to fix/implement them ;-), but chances are
much better if we know about them).