4 >The Main Configuration File</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy User Manual"
10 HREF="index.html"><LINK
12 TITLE="Privoxy Configuration"
13 HREF="configuration.html"><LINK
16 HREF="actions-file.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy User Manual</TH
46 HREF="configuration.html"
59 HREF="actions-file.html"
73 >7. The Main Configuration File</A
76 > Again, the main configuration file is named <TT
80 Linux/Unix/BSD and OS/2, and <TT
84 Configuration lines consist of an initial keyword followed by a list of
85 values, all separated by whitespace (any number of spaces or tabs). For
94 >confdir /etc/privoxy</I
100 > Assigns the value <TT
107 > and thus indicates that the configuration
108 directory is named <SPAN
110 >"/etc/privoxy/"</SPAN
113 > All options in the config file except for <TT
120 > are optional. Watch out in the below description
121 for what happens if you leave them unset.</P
123 > The main config file controls all aspects of <SPAN
127 operation that are not location dependent (i.e. they apply universally, no matter
128 where you may be surfing).</P
135 >7.1. Configuration and Log File Locations</A
141 > can (and normally does) use a number of
142 other files for additional configuration, help and logging.
143 This section of the configuration file tells <SPAN
147 where to find those other files. </P
149 > The user running Privoxy, must have read permission for all
150 configuration files, and write permission to any files that would
151 be modified, such as log files.</P
169 >The directory where the other configuration files are located</P
181 >/etc/privoxy (Unix) <I
187 > installation dir (Windows) </P
190 >Effect if unset:</DT
211 > When development goes modular and multi-user, the blocker, filter, and
212 per-user config will be stored in subdirectories of <SPAN
216 For now, the configuration directory structure is flat, except for
219 >confdir/templates</TT
220 >, where the HTML templates for CGI
221 output reside (e.g. <SPAN
247 > The directory where all logging takes place (i.e. where <TT
267 >/var/log/privoxy (Unix) <I
273 > installation dir (Windows) </P
276 >Effect if unset:</DT
306 >7.1.3. actionsfile</A
309 NAME="DEFAULT.ACTION"
312 NAME="STANDARD.ACTION"
327 HREF="actions-file.html"
336 >File name, relative to <TT
355 CLASS="LITERALLAYOUT"
356 > standard # Internal purposes, no editing recommended</P
363 CLASS="LITERALLAYOUT"
364 > default # Main actions file</P
371 CLASS="LITERALLAYOUT"
372 > user # User customizations</P
382 >Effect if unset:</DT
385 > No actions are taken at all. Simple neutral proxying.
395 > lines are permitted, and are in fact recommended!
399 The default values include standard.action, which is used for internal
400 purposes and should be loaded, default.action, which is the
404 > actions file maintained by the developers, and
408 >, where you can make your personal additions.
412 Actions files are where all the per site and per URL configuration is done for
413 ad blocking, cookie management, privacy considerations, etc.
414 There is no point in using <SPAN
418 least one actions file.
430 >7.1.4. filterfile</A
433 NAME="DEFAULT.FILTER"
445 HREF="filter-file.html"
454 >File name, relative to <TT
463 >default.filter (Unix) <I
466 > default.filter.txt (Windows)</P
469 >Effect if unset:</DT
472 > No textual content filtering takes place, i.e. all
476 HREF="actions-file.html#FILTER"
485 actions in the actions files are turned neutral.
493 HREF="filter-file.html"
495 > contains content modification
497 HREF="appendix.html#REGEX"
498 >regular expressions</A
499 >. These rules permit
500 powerful changes on the content of Web pages, e.g., you could disable your favorite
501 JavaScript annoyances, re-write the actual displayed text, or just have some
509 it appears on a Web page.
516 HREF="actions-file.html#FILTER"
525 actions rely on the relevant filter (<TT
531 to be defined in the filter file!
534 > A pre-defined filter file called <TT
538 a bunch of handy filters for common problems is included in the distribution.
539 See the section on the <TT
542 HREF="actions-file.html#FILTER"
569 > The log file to use
576 >File name, relative to <TT
588 > privoxy.log (Windows)</P
591 >Effect if unset:</DT
594 > No log file is used, all log messages go to the console (<TT
604 > The windows version will additionally log to the console.
607 > The logfile is where all logging and error messages are written. The level
608 of detail and number of messages are set with the <TT
612 option (see below). The logfile can be useful for tracking down a problem with
616 > (e.g., it's not blocking an ad you
617 think it should block) but in most cases you probably will never look at it.
620 > Your logfile will grow indefinitely, and you will probably want to
621 periodically remove it. On Unix systems, you can do this with a cron job
625 >). For Red Hat, a <B
629 script has been included.
632 > On SuSE Linux systems, you can place a line like <SPAN
635 +1024k 644 nobody.nogroup"</SPAN
640 the effect that cron.daily will automatically archive, gzip, and empty the
641 log, when it exceeds 1M size.
644 > Any log files must be writable by whatever user <SPAN
648 is being run as (default on UNIX, user id is <SPAN
674 > The file to store intercepted cookies in
681 >File name, relative to <TT
693 > privoxy.jar (Windows)</P
696 >Effect if unset:</DT
699 > Intercepted cookies are not stored at all.
706 > The jarfile may grow to ridiculous sizes over time.
729 > The trust file to use
736 >File name, relative to <TT
747 >Unset (commented out)</I
748 >. When activated: trust (Unix) <I
751 > trust.txt (Windows)</P
754 >Effect if unset:</DT
757 > The whole trust mechanism is turned off.
764 > The trust mechanism is an experimental feature for building white-lists and should
765 be used with care. It is <I
768 > recommended for the casual user.
771 > If you specify a trust file, <SPAN
775 access to sites that are named in the trustfile.
776 You can also mark sites as trusted referrers (with <TT
780 the effect that access to untrusted sites will be granted, if a link from a
781 trusted referrer was used.
782 The link target will then be added to the <SPAN
786 Possible applications include limiting Internet access for children.
792 > operator in the trust file, it may grow considerably over time.
805 >7.2. Local Set-up Documentation</A
808 > If you intend to operate <SPAN
812 than just yourself, it might be a good idea to let them know how to reach
813 you, what you block and why you do that, your policies, etc.
821 >7.2.1. user-manual</A
832 > Location of the <SPAN
842 >A fully qualified URI</P
854 >Effect if unset:</DT
858 HREF="http://www.privoxy.org/user-manual/"
860 >http://www.privoxy.org/<TT
867 will be used, where <TT
882 > The User Manual URI is used for help links from some of the internal CGI pages.
883 The manual itself is normally packaged with the binary distributions, so you probably want
884 to set this to a locally installed copy. For multi-user setups, you could provide a copy on
885 a local webserver for all your users and use the corresponding URL here.
891 > Unix, in local filesystem:
902 >user-manual  file:///usr/share/doc/privoxy-2.9.15/user-manual/</PRE
909 > Any platform, on local webserver (called <SPAN
911 >"local-webserver"</SPAN
923 >user-manual  http://local-webserver/privoxy-user-manual/</PRE
948 > If set, this option should be <I
950 >the first option in the config file</I
952 it is used while the config file is being read.
967 NAME="TRUST-INFO-URL"
968 >7.2.2. trust-info-url</A
979 > A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
992 >Two example URL are provided</P
995 >Effect if unset:</DT
998 > No links are displayed on the "untrusted" error page.
1005 > The value of this option only matters if the experimental trust mechanism has been
1007 HREF="config.html#TRUSTFILE"
1015 > If you use the trust mechanism, it is a good idea to write up some on-line
1016 documentation about your trust policy and to specify the URL(s) here.
1017 Use multiple times for multiple URLs.
1020 > The URL(s) should be added to the trustfile as well, so users don't end up
1021 locked out from the information on why they were locked out in the first place!
1032 NAME="ADMIN-ADDRESS"
1033 >7.2.3. admin-address</A
1038 CLASS="VARIABLELIST"
1044 > An email address to reach the proxy administrator.
1063 >Effect if unset:</DT
1066 > No email address is displayed on error pages and the CGI user interface.
1080 are unset, the whole "Local Privoxy Support" box on all generated pages will
1092 NAME="PROXY-INFO-URL"
1093 >7.2.4. proxy-info-url</A
1098 CLASS="VARIABLELIST"
1104 > A URL to documentation about the local <SPAN
1108 configuration or policies.
1127 >Effect if unset:</DT
1130 > No link to local documentation is displayed on error pages and the CGI user interface.
1144 are unset, the whole "Local Privoxy Support" box on all generated pages will
1148 > This URL shouldn't be blocked ;-)
1164 > These options are mainly useful when tracing a problem.
1165 Note that you might also want to invoke
1173 command line option when debugging.
1186 CLASS="VARIABLELIST"
1192 > Key values that determine what information gets logged to the
1194 HREF="config.html#LOGFILE"
1212 >12289 (i.e.: URLs plus informational and warning messages)</P
1215 >Effect if unset:</DT
1218 > Nothing gets logged.
1225 > The available debug levels are:
1235 CLASS="PROGRAMLISTING"
1236 > debug 1 # show each GET/POST/CONNECT request
1237 debug 2 # show each connection status
1238 debug 4 # show I/O status
1239 debug 8 # show header parsing
1240 debug 16 # log all data into the logfile
1241 debug 32 # debug force feature
1242 debug 64 # debug regular expression filter
1243 debug 128 # debug fast redirects
1244 debug 256 # debug GIF de-animation
1245 debug 512 # Common Log Format
1246 debug 1024 # debug kill pop-ups
1247 debug 4096 # Startup banner and warnings.
1248 debug 8192 # Non-fatal errors</PRE
1255 > To select multiple debug levels, you can either add them or use
1262 > A debug level of 1 is informative because it will show you each request
1265 >1, 4096 and 8192 are highly recommended</I
1267 so that you will notice when things go wrong. The other levels are probably
1268 only of interest if you are hunting down a specific problem. They can produce
1269 a hell of an output (especially 16).
1273 > The reporting of <I
1276 > errors (i.e. ones which crash
1280 >) is always on and cannot be disabled.
1283 > If you want to use CLF (Common Log Format), you should set <SPAN
1290 > and not enable anything else.
1301 NAME="SINGLE-THREADED"
1302 >7.3.2. single-threaded</A
1307 CLASS="VARIABLELIST"
1313 > Whether to run only one server thread
1335 >Effect if unset:</DT
1338 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1339 serve multiple requests simultaneously.
1346 > This option is only there for debug purposes and you should never
1349 >It will drastically reduce performance.</I
1362 NAME="ACCESS-CONTROL"
1363 >7.4. Access Control and Security</A
1366 > This section of the config file controls the security-relevant aspects
1377 NAME="LISTEN-ADDRESS"
1378 >7.4.1. listen-address</A
1383 CLASS="VARIABLELIST"
1389 > The IP address and TCP port on which <SPAN
1393 listen for client requests.
1419 >Effect if unset:</DT
1422 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1423 home users who run <SPAN
1426 > on the same machine as
1434 > You will need to configure your browser(s) to this proxy address and port.
1437 > If you already have another service running on port 8118, or if you want to
1438 serve requests from other machines (e.g. on your local network) as well, you
1439 will need to override the default.
1442 > If you leave out the IP address, <SPAN
1446 bind to all interfaces (addresses) on your machine and may become reachable
1447 from the Internet. In that case, consider using <A
1448 HREF="config.html#ACLS"
1449 >access control lists</A
1450 > (ACL's, see below), and/or
1457 > to untrusted users, you will
1458 also want to turn off the <TT
1461 HREF="config.html#ENABLE-EDIT-ACTIONS"
1462 >enable-edit-actions</A
1468 HREF="config.html#ENABLE-REMOTE-TOGGLE"
1469 >enable-remote-toggle</A
1479 > Suppose you are running <SPAN
1483 a machine which has the address 192.168.0.1 on your local private network
1484 (192.168.0.0) and has another outside connection with a different address.
1485 You want it to serve requests from inside only:
1495 CLASS="PROGRAMLISTING"
1496 > listen-address 192.168.0.1:8118</PRE
1517 CLASS="VARIABLELIST"
1523 > Initial state of "toggle" status
1539 >Effect if unset:</DT
1542 > Act as if toggled on
1549 > If set to 0, <SPAN
1555 >"toggled off"</SPAN
1556 > mode, i.e. behave like a normal, content-neutral
1557 proxy where all ad blocking, filtering, etc are disabled. See
1560 >enable-remote-toggle</TT
1561 > below. This is not really useful
1562 anymore, since toggling is much easier via <A
1563 HREF="http://config.privoxy.org/toggle"
1565 >the web interface</A
1573 > The windows version will only display the toggle icon in the system tray
1574 if this option is present.
1585 NAME="ENABLE-REMOTE-TOGGLE"
1586 >7.4.3. enable-remote-toggle</A
1591 CLASS="VARIABLELIST"
1597 > Whether or not the <A
1598 HREF="http://config.privoxy.org/toggle"
1618 >Effect if unset:</DT
1621 > The web-based toggle feature is disabled.
1628 > When toggled off, <SPAN
1631 > acts like a normal,
1632 content-neutral proxy, i.e. it acts as if none of the actions applied to
1636 > For the time being, access to the toggle feature can <I
1640 controlled separately by <SPAN
1643 > or HTTP authentication,
1644 so that everybody who can access <SPAN
1655 toggle it for all users. So this option is <I
1659 for multi-user environments with untrusted users.
1662 > Note that you must have compiled <SPAN
1666 support for this feature, otherwise this option has no effect.
1677 NAME="ENABLE-EDIT-ACTIONS"
1678 >7.4.4. enable-edit-actions</A
1683 CLASS="VARIABLELIST"
1689 > Whether or not the <A
1690 HREF="http://config.privoxy.org/show-status"
1710 >Effect if unset:</DT
1713 > The web-based actions file editor is disabled.
1720 > For the time being, access to the editor can <I
1724 controlled separately by <SPAN
1727 > or HTTP authentication,
1728 so that everybody who can access <SPAN
1739 modify its configuration for all users. So this option is <I
1743 > for multi-user environments with untrusted users.
1746 > Note that you must have compiled <SPAN
1750 support for this feature, otherwise this option has no effect.
1762 >7.4.5. ACLs: permit-access and deny-access</A
1765 NAME="PERMIT-ACCESS"
1773 CLASS="VARIABLELIST"
1779 > Who can access what.
1821 > are IP addresses in dotted decimal notation or valid
1833 > are subnet masks in CIDR notation, i.e. integer
1834 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1835 destination part are optional.
1848 >Effect if unset:</DT
1851 > Don't restrict access further than implied by <TT
1861 > Access controls are included at the request of ISPs and systems
1862 administrators, and <I
1864 >are not usually needed by individual users</I
1866 For a typical home user, it will normally suffice to ensure that
1870 > only listens on the localhost
1871 (127.0.0.1) or internal (home) network address by means of the
1873 HREF="config.html#LISTEN-ADDRESS"
1882 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
1883 for a firewall or to encourage anyone to defer addressing basic security
1887 > Multiple ACL lines are OK.
1888 If any ACLs are specified, then the <SPAN
1892 talks only to IP addresses that match at least one <TT
1896 and don't match any subsequent <TT
1899 > line. In other words, the
1900 last match wins, with the default being <TT
1909 > is using a forwarder (see <TT
1913 for a particular destination URL, the <TT
1919 that is examined is the address of the forwarder and <I
1923 of the ultimate target. This is necessary because it may be impossible for the local
1927 > to determine the IP address of the
1928 ultimate target (that's often what gateways are used for).
1931 > You should prefer using IP addresses over DNS names, because the address lookups take
1932 time. All DNS names must resolve! You can <I
1935 > use domain patterns
1939 > or partial domain names. If a DNS name resolves to multiple
1940 IP addresses, only the first one is used.
1943 > Denying access to particular sites by ACL may have undesired side effects
1944 if the site in question is hosted on a machine which also hosts other sites.
1951 > Explicitly define the default behavior if no ACL and
1959 is OK. The absence of a <TT
1968 > destination addresses are OK:
1979 > permit-access localhost</PRE
1986 > Allow any host on the same class C subnet as www.privoxy.org access to
1987 nothing but www.example.com:
1998 > permit-access www.privoxy.org/24 www.example.com/32</PRE
2005 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
2006 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
2017 > permit-access 192.168.45.64/26
2018 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2034 >7.4.6. buffer-limit</A
2039 CLASS="VARIABLELIST"
2045 > Maximum size of the buffer for content filtering.
2061 >Effect if unset:</DT
2064 > Use a 4MB (4096 KB) limit.
2071 > For content filtering, i.e. the <TT
2078 > actions, it is necessary that
2082 > buffers the entire document body.
2083 This can be potentially dangerous, since a server could just keep sending
2084 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2088 > When a document buffer size reaches the <TT
2092 flushed to the client unfiltered and no further attempt to
2093 filter the rest of the document is made. Remember that there may be multiple threads
2094 running, which might require up to <TT
2101 >, unless you have enabled <SPAN
2103 >"single-threaded"</SPAN
2121 > This feature allows routing of HTTP requests through a chain of
2123 It can be used to better protect privacy and confidentiality when
2124 accessing specific domains by routing requests to those domains
2125 through an anonymous public proxy (see e.g. <A
2126 HREF="http://www.multiproxy.org/anon_list.htm"
2128 >http://www.multiproxy.org/anon_list.htm</A
2130 Or to use a caching proxy to speed up browsing. Or chaining to a parent
2131 proxy may be necessary because the machine that <SPAN
2135 runs on has no direct Internet access.</P
2137 > Also specified here are SOCKS proxies. <SPAN
2141 supports the SOCKS 4 and SOCKS 4A protocols.</P
2153 CLASS="VARIABLELIST"
2159 > To which parent HTTP proxy specific requests should be routed.
2195 > is a domain name pattern (see the
2196 chapter on domain matching in the <TT
2205 > is the address of the parent HTTP proxy
2206 as an IP addresses in dotted decimal notation or as a valid DNS name (or <SPAN
2212 >"no forwarding"</SPAN
2219 > parameters are TCP ports, i.e. integer
2220 values from 1 to 64535
2233 >Effect if unset:</DT
2236 > Don't use parent HTTP proxies.
2251 >, then requests are not
2252 forwarded to another HTTP proxy but are made directly to the web servers.
2255 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2262 > Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
2273 > forward .* anon-proxy.example.org:8080
2281 > Everything goes to our example ISP's caching proxy, except for requests
2282 to that ISP's sites:
2293 > forward .*. caching-proxy.example-isp.net:8000
2294 forward .example-isp.net .</PRE
2310 >7.5.2. forward-socks4 and forward-socks4a</A
2313 NAME="FORWARD-SOCKS4"
2316 NAME="FORWARD-SOCKS4A"
2321 CLASS="VARIABLELIST"
2327 > Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
2374 > is a domain name pattern (see the
2375 chapter on domain matching in the <TT
2390 are IP addresses in dotted decimal notation or valid DNS names (<TT
2401 >"no HTTP forwarding"</SPAN
2402 >), and the optional
2408 > parameters are TCP ports, i.e. integer values from 1 to 64535
2421 >Effect if unset:</DT
2424 > Don't use SOCKS proxies.
2431 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2434 > The difference between <TT
2439 >forward-socks4a</TT
2441 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2442 server, while in SOCKS 4 it happens locally.
2453 >, then requests are not
2454 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2462 > From the company example.com, direct connections are made to all
2466 > domains, but everything outbound goes through
2467 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2479 > forward-socks4a .*. socks-gw.example.com:1080 www-cache.example-isp.net:8080
2480 forward .example.com .</PRE
2487 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2498 > forward-socks4 .*. socks-gw.example.com:1080 .</PRE
2513 NAME="ADVANCED-FORWARDING-EXAMPLES"
2514 >7.5.3. Advanced Forwarding Examples</A
2517 > If you have links to multiple ISPs that provide various special content
2518 only to their subscribers, you can configure multiple <SPAN
2522 which have connections to the respective ISPs to act as forwarders to each other, so that
2526 > users can see the internal content of all ISPs.</P
2528 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2529 isp-b.net. Both run <SPAN
2533 configuration can look like this:</P
2546 forward .isp-b.net host-b:8118</PRE
2563 forward .isp-a.net host-a:8118</PRE
2569 > Now, your users can set their browser's proxy to use either
2570 host-a or host-b and be able to browse the internal content
2571 of both isp-a and isp-b.</P
2573 > If you intend to chain <SPAN
2580 > locally, then chain as
2583 >browser -> squid -> privoxy</TT
2584 > is the recommended way. </P
2586 > Assuming that <SPAN
2593 run on the same box, your squid configuration could then look like this:</P
2603 > # Define Privoxy as parent proxy (without ICP)
2604 cache_peer 127.0.0.1 parent 8118 7 no-query
2606 # Define ACL for protocol FTP
2609 # Do not forward FTP requests to Privoxy
2610 always_direct allow ftp
2612 # Forward all the rest to Privoxy
2613 never_direct allow all</PRE
2619 > You would then need to change your browser's proxy settings to <SPAN
2622 >'s address and port.
2623 Squid normally uses port 3128. If unsure consult <TT
2638 >7.6. Windows GUI Options</A
2644 > has a number of options specific to the
2645 Windows GUI interface:</P
2647 NAME="ACTIVITY-ANIMATION"
2652 >"activity-animation"</SPAN
2657 > icon will animate when
2661 > is active. To turn off, set to 0.</P
2666 CLASS="LITERALLAYOUT"
2669 >activity-animation 1</I
2671 </P
2681 >"log-messages"</SPAN
2686 > will log messages to the console
2692 CLASS="LITERALLAYOUT"
2697 </P
2702 NAME="LOG-BUFFER-SIZE"
2708 >"log-buffer-size"</SPAN
2709 > is set to 1, the size of the log buffer,
2710 i.e. the amount of memory used for the log messages displayed in the
2711 console window, will be limited to <SPAN
2713 >"log-max-lines"</SPAN
2716 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
2717 eat up all your memory!</P
2722 CLASS="LITERALLAYOUT"
2725 >log-buffer-size 1</I
2727 </P
2732 NAME="LOG-MAX-LINES"
2737 >log-max-lines</SPAN
2738 > is the maximum number of lines held
2739 in the log buffer. See above.</P
2744 CLASS="LITERALLAYOUT"
2747 >log-max-lines 200</I
2749 </P
2754 NAME="LOG-HIGHLIGHT-MESSAGES"
2759 >"log-highlight-messages"</SPAN
2764 > will highlight portions of the log
2765 messages with a bold-faced font:</P
2770 CLASS="LITERALLAYOUT"
2773 >log-highlight-messages 1</I
2775 </P
2780 NAME="LOG-FONT-NAME"
2783 > The font used in the console window:</P
2788 CLASS="LITERALLAYOUT"
2791 >log-font-name Comic Sans MS</I
2793 </P
2798 NAME="LOG-FONT-SIZE"
2801 > Font size used in the console window:</P
2806 CLASS="LITERALLAYOUT"
2811 </P
2816 NAME="SHOW-ON-TASK-BAR"
2822 >"show-on-task-bar"</SPAN
2823 > controls whether or not
2827 > will appear as a button on the Task bar
2833 CLASS="LITERALLAYOUT"
2836 >show-on-task-bar 0</I
2838 </P
2843 NAME="CLOSE-BUTTON-MINIMIZES"
2848 >"close-button-minimizes"</SPAN
2849 > is set to 1, the Windows close
2850 button will minimize <SPAN
2853 > instead of closing
2854 the program (close with the exit option on the File menu).</P
2859 CLASS="LITERALLAYOUT"
2862 >close-button-minimizes 1</I
2864 </P
2874 >"hide-console"</SPAN
2875 > option is specific to the MS-Win console
2879 >. If this option is used,
2883 > will disconnect from and hide the
2889 CLASS="LITERALLAYOUT"
2894 </P
2915 HREF="configuration.html"
2931 HREF="actions-file.html"