documentation/running.sgml

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