documentation/running.sgml

   1   <chapter id="running">
   2     <title>Running Wine</title>
   3
   4     <para>
   5       This chapter will describe all aspects of running Wine, like e.g.
   6       basic Wine invocation, command line parameters of various Wine
   7       support programs etc.
   8     </para>
   9
  10     <para>
  11       This chapter will describe all aspects of running Wine, like e.g.
  12       basic Wine invocation, command line parameters of various Wine
  13       support programs etc.
  14     </para>
  15
  16     <para>
  17
  18     </para>
  19
  20     <sect1 id="basic-usage">
  21       <title>Basic usage: applications and control panel applets</title>
  22       <para>
  23         Assuming you are using a fake Windows installation, you install
  24         applications into Wine in the same way you would in Windows: by
  25         running the installer. You can just accept the defaults for
  26         where to install, most installers will default to "C:\Program
  27         Files", which is fine. If the application installer requests it,
  28         you may find that Wine creates icons on your desktop and in your
  29         app menu. If that happens, you can start the app by clicking on
  30         them.
  31       </para>
  32
  33       <para>
  34         The standard way to uninstall things is for the application to
  35         provide an uninstaller, usually registered with the "Add/Remove
  36         Programs" control panel applet.
  37         To access the Wine equivalent, run the <command>uninstaller</command>
  38         program (it is located in the
  39         <filename>programs/uninstaller/</filename> directory in a Wine
  40         source directory) in a <glossterm>terminal</glossterm>:
  41       </para>
  42
  43       <screen>
  44         <prompt>$</prompt> <userinput>uninstaller</userinput>
  45       </screen>
  46
  47       <para>
  48         Some programs install associated control panel applets, examples
  49         of this would be Internet Explorer and QuickTime. You can access
  50         the Wine control panel by running in a
  51         <glossterm>terminal</glossterm>:
  52       </para>
  53
  54       <screen>
  55          <prompt>$</prompt> <userinput>wine control</userinput>
  56       </screen>
  57
  58       <para>
  59         which will open a window with the installed control panel
  60         applets in it, as in Windows.
  61       </para>
  62
  63       <para>
  64         If the application doesn't install menu or desktop items, you'll
  65         need to run the app from the command line. Remembering where you
  66         installed to, something like:
  67       </para>
  68
  69       <screen>
  70          <prompt>$</prompt> <userinput>wine "c:\program files\appname\appname.exe"</userinput>
  71       </screen>
  72
  73       <para>
  74         will probably do the trick. The path isn't case sensitive, but
  75         remember to include the double quotes.  Some programs don't
  76         always use obvious naming for their directories and EXE files,
  77         so you might have to look inside the program files directory to
  78         see what it put where.
  79       </para>
  80     </sect1>
  81
  82     <sect1 id="running-wine">
  83       <title>How to run Wine</title>
  84       <para>
  85         Wine is a very complicated piece of software with many ways to
  86         adjust how it runs.  With very few exceptions, you can
  87         activate the same set of features through the <link
  88         linkend="config-file">configuration file</link> as you can
  89         with command-line parameters.  In this chapter, we'll briefly
  90         discuss these parameters, and match them up with their
  91         corresponding configuration variables.
  92       </para>
  93
  94       <para>
  95         You can invoke the <command>wine --help</command> command to
  96         get a listing of all Wine's command-line parameters:
  97       </para>
  98       <para>
  99         <screen>
 100 Usage: ./wine [options] program_name [arguments]
 101
 102 Options:
 103    --debugmsg name  Turn debugging-messages on or off
 104    --help,-h        Show this help message
 105    --version,-v     Display the Wine version
 106         </screen>
 107       </para>
 108
 109       <para>
 110         You can specify as many options as you want, if any.
 111         Typically, you will want to have your configuration file set
 112         up with a sensible set of defaults; in this case, you can run
 113         <command>wine</command> without explicitly listing any
 114         options.  In rare cases, you might want to override certain
 115         parameters on the command line.
 116       </para>
 117       <para>
 118         After the options, you should put the name of the file you
 119         want <command>wine</command> to execute.  If the executable is
 120         in the <parameter>Path</parameter> parameter in the
 121         configuration file, you can simply give the executable file
 122         name.  However, if the executable is not in
 123         <parameter>Path</parameter>, you must give the full path to
 124         the executable (in Windows format, not UNIX format!).  For
 125         example, given a <parameter>Path</parameter> of the following:
 126       </para>
 127       <screen>
 128 [wine]
 129 "Path"="c:\\windows;c:\\windows\\system;e:\\;e:\\test;f:\\"
 130       </screen>
 131       <para>
 132         You could run the file
 133         <filename>c:\windows\system\foo.exe</filename> with:
 134       </para>
 135       <screen>
 136 <prompt>$</prompt> <userinput>wine foo.exe</userinput>
 137       </screen>
 138       <para>
 139         However, you would have to run the file
 140         <filename>c:\myapps\foo.exe</filename> with this command:
 141       </para>
 142       <screen>
 143 <prompt>$</prompt> <userinput>wine c:\\myapps\\foo.exe</userinput>
 144       </screen>
 145       <para>
 146       (note the backslash-escaped "\" !)
 147       </para>
 148       <para>
 149         For details on running text mode (CUI) executables, read the
 150         <link linkend="CUI-programs">section</link> below.
 151       </para>
 152     </sect1>
 153
 154     <sect1 id="explorer-like-wine">
 155       <title>Explorer-like graphical Wine environments</title>
 156
 157       <para>
 158         If you don't feel like manually invoking Wine for every program
 159         you want to run and instead want to have an integrated graphical
 160         interface to run your Windows programs in, then installing e.g.
 161         <ulink url="http://www.calmira.org">Calmira</ulink>, a
 162         Win95-Explorer-like shell replacement, would probably be a great
 163         idea. Calmira might still have a few problems running on Wine,
 164         though. Other usable Explorer replacements should be listed here
 165         in the future.
 166       </para>
 167     </sect1>
 168
 169     <sect1 id="command-line-options">
 170       <title>Wine Command Line Options</title>
 171
 172       <sect2 id="config-parameter">
 173         <title>--debugmsg [channels]</title>
 174         <para>
 175           Wine isn't perfect, and many Windows applications still
 176           don't run without bugs under Wine (but then, a lot of programs
 177           don't run without bugs under native Windows either!).  To
 178           make it easier for people to track down the causes behind
 179           each bug, Wine provides a number of <firstterm>debug
 180           channels</firstterm> that you can tap into.
 181         </para>
 182         <para>
 183           Each debug channel, when activated, will trigger logging
 184           messages to be displayed to the console where you invoked
 185           <command>wine</command>.  From there you can redirect the
 186           messages to a file and examine it at your leisure.  But be
 187           forewarned!  Some debug channels can generate incredible
 188           volumes of log messages.  Among the most prolific offenders
 189           are <parameter>relay</parameter> which spits out a log
 190           message every time a win32 function is called,
 191           <parameter>win</parameter> which tracks windows message
 192           passing, and of course <parameter>all</parameter> which is
 193           an alias for every single debug channel that exists.  For a
 194           complex application, your debug logs can easily top 1 MB and
 195           higher.  A <parameter>relay</parameter> trace can often
 196           generate more than 10 MB of log messages, depending on how
 197           long you run the application.  (As described in the
 198           <link linkend = "config-debug-etc">Debug</link>
 199           section of configuring wine you can
 200           modify what the <parameter>relay</parameter> trace reports).
 201           Logging does slow down Wine
 202           quite a bit, so don't use <parameter>--debugmsg</parameter>
 203           unless you really do want log files.
 204         </para>
 205         <para>
 206           Within each debug channel, you can further specify a
 207           <firstterm>message class</firstterm>, to filter out the
 208           different severities of errors.  The four message classes
 209           are:
 210           <simplelist type="inline">
 211             <member><parameter>trace</parameter></member>
 212             <member><parameter>fixme</parameter></member>
 213             <member><parameter>warn</parameter></member>
 214             <member><parameter>err</parameter></member>
 215           </simplelist>.
 216         </para>
 217         <para>
 218           To turn on a debug channel, use the form
 219           <parameter>class+channel</parameter>.  To turn it off, use
 220           <parameter>class-channel</parameter>.  To list more than one
 221           channel in the same <parameter>--debugmsg</parameter>
 222           option, separate them with commas.  For example, to request
 223           <parameter>warn</parameter> class messages in the
 224           <parameter>heap</parameter> debug channel, you could invoke
 225           <command>wine</command> like this:
 226         </para>
 227         <screen>
 228 <prompt>$</prompt> <userinput>wine --debugmsg warn+heap <replaceable>program_name</replaceable></userinput>
 229         </screen>
 230         <para>
 231           If you leave off the message class, <command>wine</command>
 232           will display messages from all four classes for that channel:
 233         </para>
 234         <screen>
 235 <prompt>$</prompt> <userinput>wine --debugmsg +heap <replaceable>program_name</replaceable></userinput>
 236         </screen>
 237         <para>
 238           If you wanted to see log messages for everything except the
 239           relay channel, you might do something like this:
 240         </para>
 241         <screen>
 242 <prompt>$</prompt> <userinput>wine --debugmsg +all,-relay <replaceable>program_name</replaceable></userinput>
 243         </screen>
 244         <para>
 245           Here is a list of the debug channels and classes in Wine.
 246           More channels will be added to (or subtracted from) later
 247           versions.
 248         </para>
 249
 250                 <table frame="none"><title>Debug Channels</title>
 251                 <tgroup cols=5 align="left">
 252                 <tbody>
 253 <row><entry>
 254 all</><entry>accel</><entry>advapi</><entry>animate</><entry>aspi</>
 255 </row><row><entry>
 256 atom</><entry>avifile</><entry> bitblt</><entry> bitmap</><entry> caret</>
 257 </row><row><entry>
 258 cdrom</><entry>class</><entry> clipboard</><entry> clipping</><entry>combo</>
 259 </row><row><entry>
 260 comboex</><entry> comm</><entry>commctrl</><entry>commdlg</><entry> console</>
 261 </row><row><entry>
 262 crtdll</><entry>cursor</><entry>datetime</><entry>dc</><entry> ddeml</>
 263 </row><row><entry>
 264 ddraw</><entry> debug</><entry> debugstr</><entry>delayhlp</><entry>dialog</>
 265 </row><row><entry>
 266 dinput</><entry>dll</><entry> dosfs</><entry>dosmem</><entry>dplay</>
 267 </row><row><entry>
 268 driver</><entry>dsound</><entry>edit</><entry>elfdll</><entry>enhmetafile</>
 269 </row><row><entry>
 270 event</><entry>exec</><entry>file</><entry>fixup</><entry>font</>
 271 </row><row><entry>
 272 gdi</><entry> global</><entry>graphics</><entry> header</><entry>heap</>
 273 </row><row><entry>
 274 hook</><entry>hotkey</><entry>icmp</><entry>icon</><entry>imagehlp</>
 275 </row><row><entry>
 276 imagelist</><entry> imm</><entry>int</><entry>int10</><entry>int16</>
 277 </row><row><entry>
 278 int17</><entry>int19</><entry>int21</><entry>int31</><entry> io</>
 279 </row><row><entry>
 280 ipaddress</><entry>joystick</><entry>key</><entry>keyboard</><entry>loaddll</>
 281 </row><row><entry>
 282 ldt</><entry>listbox</><entry>listview</><entry>local</><entry>mci</>
 283 </row><row><entry>
 284 mcianim</><entry>mciavi</><entry>mcicda</><entry>mcimidi</><entry>mciwave</>
 285 </row><row><entry>
 286 mdi</><entry>menu</><entry>message</><entry>metafile</><entry>midi</>
 287 </row><row><entry>
 288 mmaux</><entry>mmio</><entry>mmsys</><entry>mmtime</><entry>module</>
 289 </row><row><entry>
 290 monthcal</><entry>mpr</><entry>msacm</><entry>msg</><entry>msvideo</>
 291 </row><row><entry>
 292 nativefont</><entry>nonclient</><entry>ntdll</><entry>odbc</><entry>ole</>
 293 </row><row><entry>
 294 opengl</><entry>pager</><entry>palette</><entry>pidl</><entry>print</>
 295 </row><row><entry>
 296 process</><entry>profile</><entry>progress</><entry>prop</><entry>propsheet</>
 297 </row><row><entry>
 298 psapi</><entry>psdrv</><entry>ras</><entry>rebar</><entry>reg</>
 299 </row><row><entry>
 300 region</><entry>relay</><entry>resource</><entry>richedit</><entry>scroll</>
 301 </row><row><entry>
 302 segment</><entry>seh</><entry>selector</><entry>sendmsg</><entry>server</>
 303 </row><row><entry>
 304 setupapi</><entry>setupx</><entry>shell</><entry>snoop</><entry>sound</>
 305 </row><row><entry>
 306 static</><entry>statusbar</><entry>storage</><entry>stress</><entry>string</>
 307 </row><row><entry>
 308 syscolor</><entry>system</><entry>tab</><entry>tape</><entry>tapi</>
 309 </row><row><entry>
 310 task</><entry>text</><entry>thread</><entry>thunk</><entry>timer</>
 311 </row><row><entry>
 312 toolbar</><entry>toolhelp</><entry>tooltips</><entry>trackbar</><entry>treeview</>
 313 </row><row><entry>
 314 ttydrv</><entry>tweak</><entry>typelib</><entry>updown</><entry>ver</>
 315 </row><row><entry>
 316 virtual</><entry>vxd</><entry>wave</><entry>win</><entry>win16drv</>
 317 </row><row><entry>
 318 win32</><entry>winedbg</><entry>wing</><entry>wininet</><entry>winsock</>
 319 </row><row><entry>
 320 winspool</><entry>wnet</><entry>x11</>
 321 </row>
 322                 </tbody>
 323                 </tgroup>
 324                 </table>
 325
 326         <para>
 327           For more details about debug channels, check out the
 328           <ulink url="http://wine.codeweavers.com/docs/wine-devel/">
 329             The Wine Developer's Guide</ulink>.
 330         </para>
 331       </sect2>
 332
 333       <sect2>
 334         <title>--help</title>
 335         <para>
 336           Shows a small command line help page.
 337         </para>
 338       </sect2>
 339
 340       <sect2>
 341         <title>--version</title>
 342         <para>
 343           Shows the Wine version string. Useful to verify your installation.
 344         </para>
 345       </sect2>
 346     </sect1>
 347
 348     <sect1 id="wineserver-command-line-options">
 349       <title>wineserver Command Line Options</title>
 350
 351       <para>
 352         wineserver usually gets started automatically by Wine whenever
 353         the first wine process gets started.
 354         However, wineserver has some useful command line options that
 355         you can add if you start it up manually, e.g. via a user login
 356         script or so.
 357       </para>
 358
 359       <sect2 id="wineserver-config-parameter">
 360         <title>-d&lt;n&gt;</title>
 361         <para>
 362           Sets the debug level for debug output in the terminal that
 363           wineserver got started in at level &lt;n&gt;.
 364           In other words: everything greater than 0 will enable
 365           wineserver specific debugging output (not to confuse with Wine's wineserver logging channel, --debugmsg +server, though!).
 366         </para>
 367       </sect2>
 368
 369       <sect2>
 370         <title>-h</title>
 371         <para>
 372           Display wineserver command line options help message.
 373         </para>
 374       </sect2>
 375
 376       <sect2>
 377         <title>-k[n]</title>
 378         <para>
 379           Kill the current wineserver, optionally with signal n.
 380         </para>
 381       </sect2>
 382
 383       <sect2>
 384         <title>-p[n]</title>
 385         <para>
 386           This parameter makes wineserver persistent, optionally for n
 387           seconds. It will prevent wineserver from shutting down immediately.
 388         </para>
 389         <para>
 390           Usually, wineserver quits almost immediately after the last
 391           wine process using this wineserver terminated.
 392           However, since wineserver loads a lot of things on startup
 393           (such as the whole Windows registry data), its startup might
 394           be so slow that it's very useful to keep it from exiting after
 395           the end of all Wine sessions, by making it persistent.
 396         </para>
 397       </sect2>
 398
 399       <sect2>
 400         <title>-w</title>
 401         <para>
 402           This parameter makes a newly started wineserver wait until the
 403           currently active wineserver instance terminates.
 404         </para>
 405       </sect2>
 406     </sect1>
 407
 408     <sect1 id="environment-variables">
 409       <title>Setting Windows/DOS environment variables</title>
 410       <para>
 411         Your program might require some environment variable to be set
 412         properly in order to run successfully.
 413         In this case you need to set this environment variable in the
 414         Linux shell, since Wine will pass on the entire shell environment
 415         variable settings to the Windows environment variable space.
 416         Example for the bash shell (other shells may have a different syntax
 417         !):
 418         <screen>
 419           export MYENVIRONMENTVAR=myenvironmentvarsetting
 420         </screen>
 421         This will make sure your Windows program can access the
 422         MYENVIRONMENTVAR environment variable once you start your program
 423         using Wine.
 424         If you want to have MYENVIRONMENTVAR set permanently, then you can
 425         place the setting into /etc/profile, or also ~/.bashrc in the case of
 426         bash.
 427       </para>
 428       <para>
 429         Note however that there is an exception to the rule:
 430         If you want to change the PATH environment variable, then of
 431         course you can't modify it that way, since this will alter the
 432         Unix PATH environment setting. Instead, you should set the
 433         WINEPATH environment variable. An alternative way to
 434         indicate the content of the DOS PATH environment variable would
 435         be to change the "path" setting in the wine config file's <link
 436         linkend="config-wine">[wine]</link> section.
 437       </para>
 438
 439     </sect1>
 440
 441     <sect1 id="CUI-programs">
 442       <title>Text mode programs (CUI: Console User Interface)</title>
 443       <para>Text mode programs are program which output is only made
 444         out of text (surprise!). In Windows terminology, they are
 445         called CUI (Console User Interface) executables, by opposition
 446         to GUI (Graphical User Interface) executables. Win32 API
 447         provide a complete set of APIs to handle this situation, which
 448         goes from basic features like text printing, up to high level
 449         functionalities (like full screen editing, color support,
 450         cursor motion, mouse support), going through features like
 451         line editing or raw/cooked input stream support
 452       </para>
 453       <para>
 454         Given the wide scope of features above, and the current usage
 455         in Un*x world, Wine comes out with three different ways for
 456         running a console program (aka a CUI executable):
 457         <itemizedlist>
 458           <listitem>
 459             <para>
 460               bare streams
 461             </para>
 462           </listitem>
 463           <listitem>
 464             <para>
 465               wineconsole with user backend
 466             </para>
 467           </listitem>
 468           <listitem>
 469             <para>
 470               wineconsole with curses backend
 471             </para>
 472           </listitem>
 473         </itemizedlist>
 474       </para>
 475       <para>The names here are a bit obscure. "bare streams" means
 476         that no extra support of wine is provide to map between the
 477         unix console access and Windows console access. The two other
 478         ways require the use of a specific Wine program (wineconsole)
 479         which provide extended facilities. The following table
 480         describes what you can do (and cannot do) with those three
 481         ways.
 482         <table>
 483           <title>Basic differences in consoles</title>
 484           <tgroup cols="4" align="left">
 485             <thead>
 486               <row>
 487                 <entry>Function</entry>
 488                 <entry>Bare streams</entry>
 489                 <entry>Wineconsole &amp; user backend</entry>
 490                 <entry>Wineconsole &amp; curses backend</entry>
 491                 </row>
 492             </thead>
 493             <tbody>
 494               <row>
 495                 <entry>How to run (assuming executable is called foo.exe)</entry>
 496                 <entry><msgtext>
 497 <screen><prompt>$</prompt> <userinput>wine foo.exe</userinput></screen>
 498                   </msgtext></entry>
 499                 <entry><msgtext>
 500 <screen><prompt>$</prompt> <userinput>wineconsole -- --backend=user foo.exe</userinput></screen>
 501                 </msgtext></entry>
 502                 <entry><msgtext>
 503 <screen><prompt>$</prompt> <userinput>wineconsole foo.exe</userinput></screen>
 504                 </msgtext>You can also use --backend=curses as an option</entry>
 505               </row>
 506               <row>
 507                 <entry>Good support for line oriented CUI applications
 508                   (which print information line after line)
 509                   </entry>
 510                 <entry>Yes</entry>
 511                 <entry>Yes</entry>
 512                 <entry>Yes</entry>
 513               </row>
 514               <row>
 515                 <entry>Good support for full screen CUI
 516                   applications (including but not limited to color
 517                   support, mouse support...)</entry>
 518                 <entry>No</entry>
 519                 <entry>Yes</entry>
 520                 <entry>Yes</entry>
 521               </row>
 522               <row>
 523                 <entry>Can be run even if X11 is not running</entry>
 524                 <entry>Yes</entry>
 525                 <entry>No</entry>
 526                 <entry>Yes</entry>
 527               </row>
 528               <row>
 529                 <entry>Implementation</entry>
 530                 <entry>Maps the standard Windows streams to the
 531                   standard Unix streams (stdin/stdout/stderr)
 532                 </entry>
 533                 <entry>
 534                   Wineconsole will create a new Window (hence
 535                   requiring the USER32 DLL is available) where all
 536                   information will be displayed
 537                 </entry>
 538                 <entry>
 539                   Wineconsole will use existing unix console
 540                   (from which the program is run) and with the help of
 541                   the (n)curses library take control of all the terminal
 542                   surface for interacting with the user
 543                 </entry>
 544               </row>
 545               <row>
 546                 <entry>Known limitations</entry>
 547                 <entry></entry>
 548                 <entry></entry>
 549                 <entry>
 550                   Will produce strange behavior if two (or more)
 551                   Windows consoles are used on the same Un*x terminal.
 552                 </entry>
 553               </row>
 554             </tbody>
 555           </tgroup>
 556         </table>
 557       </para>
 558       <sect2 id="CUI-programs-config">
 559         <title>Configuration of CUI executables</title>
 560         <para>
 561           When wineconsole is used, several configuration options are
 562           available. Wine (as Windows do) stores, on a per application
 563           basis, several options in the registry. This let a user, for
 564           example, define the default screen-buffer size he would like
 565           to have for a given application.
 566         </para>
 567         <para>
 568           As of today, only the USER backend allows you to edit those
 569           options (we don't recommend editing by hand the registry
 570           contents). This edition is fired when a user right click in
 571           the console (this popups a menu), where you can either
 572           choose from:
 573           <itemizedlist>
 574             <listitem>
 575               <para>
 576                 Default: this will edit the settings shared by all
 577                 applications which haven't been configured yet. So,
 578                 when an application is first run (on your machine,
 579                 under your account) in wineconsole, wineconsole will
 580                 inherit this default settings for the
 581                 application. Afterwards, the application will have its
 582                 own settings, that you'll be able to modify at your will.
 583               </para>
 584               <para>
 585                 Properties: this will edit the application's
 586                 settings. When you're done, with the edition, you'll
 587                 be prompted whether you want to:
 588                 <orderedlist>
 589                   <listitem>
 590                     <para>
 591                       Keep these modified settings only for this
 592                       session (next time you run the application, you
 593                       will not see the modification you've just made).
 594                     </para>
 595                   </listitem>
 596                   <listitem>
 597                     <para>
 598                       Use the settings for this session and save them
 599                       as well, so that next you run your application,
 600                       you'll use these new settings again.
 601                     </para>
 602                   </listitem>
 603                 </orderedlist>
 604               </para>
 605             </listitem>
 606           </itemizedlist>
 607         </para>
 608         <para>
 609           Here's the list of the items you can configure, and their
 610           meanings:
 611           <table>
 612             <title>Wineconsole configuration options</title>
 613             <tgroup cols="2" align="left">
 614               <thead>
 615                 <row>
 616                   <entry>Configuration option</entry>
 617                   <entry>Meaning</entry>
 618                 </row>
 619               </thead>
 620               <tbody>
 621                 <row>
 622                   <entry>Cursor's size</entry>
 623                   <entry>
 624                     Defines the size of the cursor. Three options are
 625                     available: small (33% of character height), medium
 626                     (66%) and large (100%)
 627                   </entry>
 628                 </row>
 629                 <row>
 630                   <entry>Popup menu</entry>
 631                   <entry>
 632                     It's been said earlier that wineconsole
 633                     configuration popup was triggered using a right
 634                     click in the console's window. However, this can
 635                     be an issue when the application you run inside
 636                     wineconsole expects the right click events to be
 637                     sent to it. By ticking control or shift you select
 638                     additional modifiers on the right click for
 639                     opening the popup. For example, ticking shift will
 640                     send events to the application when you right
 641                     click the window without shift being hold down,
 642                     and open the window when you right-click while
 643                     shift being hold down.
 644                   </entry>
 645                 </row>
 646                 <row>
 647                   <entry>Quick edit</entry>
 648                   <entry>
 649                     This tick box lets you decide whether left-click
 650                     mouse events shall be interpreted as events to be
 651                     sent to the underlying application (tick off) or
 652                     as a selection of rectangular part of the screen
 653                     to be later on copied onto the clipboard (tick on).
 654                   </entry>
 655                 </row>
 656                 <row>
 657                   <entry>History</entry>
 658                   <entry>
 659                     This lets you pick up how many commands you want
 660                     the console to recall. You can also drive whether
 661                     you want, when entering several times the same
 662                     command - potentially intertwined with others -
 663                     whether you want to store all of them (tick off)
 664                     or only the last one (tick on).
 665                   </entry>
 666                 </row>
 667                 <row>
 668                   <entry>Police</entry>
 669                   <entry>
 670                     The Police property sheet allows you to pick the
 671                     default font for the console (font file, size,
 672                     background and foreground color).
 673                   </entry>
 674                 </row>
 675                 <row>
 676                   <entry>Screenbuffer &amp; window size</entry>
 677                   <entry>
 678                     The console as you see it is made of two different
 679                     parts. On one hand there's the screenbuffer which
 680                     contains all the information your application puts
 681                     on the screen, and the window which displays a
 682                     given area of this screen buffer. Note that the
 683                     window is always smaller or of the same size than
 684                     the screen buffer. Having a stricly smaller window
 685                     size will put on scrollbars on the window so that
 686                     you can see the whole screenbuffer's content.
 687                   </entry>
 688                 </row>
 689                 <row>
 690                   <entry>Close on exit</entry>
 691                   <entry>
 692                     If it's ticked, then the wineconsole will exit
 693                     when the application within terminates. Otherwise,
 694                     it'll remain opened until the user manually closes
 695                     it: this allows seeing the latest information of a
 696                     program after it has terminated.
 697                   </entry>
 698                 </row>
 699                 <row>
 700                   <entry>Edition mode</entry>
 701                   <entry>
 702                     <msgtext>
 703                       <para>
 704                         When the user enter commands, he or she can
 705                         choose between several edition modes:
 706                         <itemizedlist>
 707                           <listitem>
 708                             <para>
 709                               Emacs: the same keybindings as under
 710                               emacs are available. For example, Ctrl-A
 711                               will bring the cursor to the beginning
 712                               of the edition line. See your emacs
 713                               manual for the details of the commands.
 714                             </para>
 715                           </listitem>
 716                           <listitem>
 717                             <para>
 718                               Win32: this are the standard Windows
 719                               console key-bindings (mainly using
 720                               arrows).
 721                             </para>
 722                           </listitem>
 723                         </itemizedlist>
 724                       </para>
 725                     </msgtext>
 726                   </entry>
 727                 </row>
 728               </tbody>
 729             </tgroup>
 730           </table>
 731         </para>
 732       </sect2>
 733     </sect1>
 734   </chapter>
 735
 736 <!-- Keep this comment at the end of the file
 737 Local variables:
 738 mode: sgml
 739 sgml-parent-document:("wine-user.sgml" "set" "book" "chapter" "")
 740 End:
 741 -->