File: ModulePath.xml

package info (click to toggle)
fvwm 1%3A2.7.0-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 15,968 kB
  • sloc: ansic: 145,836; xml: 17,096; perl: 7,237; sh: 5,100; makefile: 1,101; yacc: 688; lex: 187; sed: 11
file content (47 lines) | stat: -rw-r--r-- 1,224 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  "../docbook-xml/docbookx.dtd"
[
<!ENTITY % myents SYSTEM "../fvwm.ent" >
%myents;
]>

<!-- $Id$ -->

<section id='ModulePath'>
<title>ModulePath</title>

<cmdsynopsis>
	<command>ModulePath</command
	><arg choice='plain'
		><replaceable>path</replaceable
	></arg>
</cmdsynopsis>

<para>Specifies a colon separated list of directories in which to search
for modules.  To find a module, fvwm searches each directory in
turn and uses the first file found.  Directory names on the list
do not need trailing slashes.</para>

<para>The
<emphasis remap='B'>ModulePath</emphasis>
may contain environment variables such as
<envar>$HOME</envar> (or <envar>${HOME}</envar>).
Further, a '+' in the
<replaceable>path</replaceable>
is expanded to the previous value of the
<replaceable>path</replaceable>,
allowing easy appending or prepending to the
<replaceable>path</replaceable>.</para>

<para>For example:</para>

<programlisting>
ModulePath ${HOME}/lib/fvwm/modules:+
</programlisting>

<para>The directory containing the standard modules is available via the
environment variable
<envar>$FVWM_MODULEDIR</envar>.</para>

</section>