FVWM: Modules path

From: Peter Kabal <kabal_at_tsp.EE.McGill.CA>
Date: Wed, 9 Oct 1996 12:07:40 -0400 (EDT)

I don't want to hardcode the paths that the system manager has used for
the modules into my .fvwm2rc file. Yet I want to add a path for my
own modules. At the moment, the ModulePath has to have both the system
path and the custom path.

suggestions for future versions:
(1) Modify the syntax of ModulePath (and perhaps other paths) to have a
    trailing ":" signify that the "standard" paths are to be appended. (The
    TeX environment variable TEXINPUTS uses this convention and in addition
    uses the convention that a trailing // on a file name signifies that
    directories and all subdirectories).

    thus:
    ModulePath /home/me/Modules:
    signifies that I want fvwm2 to look in my directory and then in the
    standard Modules directory.

(2) As part of the standard installation, add a few extra Form modules (as
    links). For example, add FvwmForm1, FvwmForm2, FvwmForm3 as aliases for
    FvwmForm. This way, a user can set up different "forms" without having
    to have copies (or links) for the modules. For instance, I use one form
    for a "query/exit X" command, another for "rlogin to remote". My personal
    Modules directory contains only links to FvwmForm, with two different
    names. If the standard directory had a few extra generic links, I would
    not have to have maintain my own modules directory.

Peter Kabal kabal_at_TSP.EE.McGill.CA (514) 398-7130
Department of Electrical Engineering (514) 398-4470 (FAX)
McGill University
3480 University Street Montreal, Quebec Canada H3A 2A7
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed Oct 09 1996 - 11:08:01 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:59 BST