File: settings_paths.xml

package info (click to toggle)
pdfedit 0.4.5-1
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 15,220 kB
  • ctags: 17,436
  • sloc: cpp: 156,708; xml: 8,973; makefile: 1,003; sh: 704; ansic: 688; perl: 669; yacc: 589; python: 236; lisp: 51
file content (44 lines) | stat: -rw-r--r-- 1,533 bytes parent folder | download | duplicates (2)
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
<sect1 id="paths_tab">
	<title>Paths tab</title>
	<para>
			<mediaobject>
				<imageobject>
					<imagedata fileref="gui/images/options_paths.png" format="PNG"/>
				</imageobject>
				<textobject>
					<phrase>Paths tab</phrase>
				</textobject>
			</mediaobject>
	You can set paths to various files here. The path is semicolon-separated list of directories,
	each of them can contain environment variablesm, which will be automatically expanded,
	such as <envar>$HOME</envar> (which will
	expand to user's home directory) or <envar>$LANG</envar> (which can expand to name of selected locale)	
	There are also two special variables, <envar>$PDFEDIT_DATA</envar> will expand to directory with
	editor datafiles (<filename>/usr/local/share/pdfedit</filename> by default) and <envar>$PDFEDIT_BIN</envar>
	will expand to directory where the editor binary is located (<filename>/usr/local/bin</filename> by default)
 </para>
 <sect2 id="icon_path">
  <title>Icon path</title>
  <para>
   Paths in which to look for application icons. 
  </para>
 </sect2>
 <sect2 id="script_path">
  <title>Script path</title>
  <para>
   Paths in which to look for script files.
  </para>
 </sect2>
 <sect2 id="startup_scripts">
  <title>Scripts to run on start</title>
  <para>
   List of files which will be run on start.
  </para>
 </sect2>
 <sect2 id="console_log">
 <title>Console log file</title>
  <para>
   Name of file in which all console commands and output will be logged. If empty, logging will be turned off.
  </para>
 </sect2>
</sect1>