konfigurator.docbook

LINUX 下, 以 QT/KDE 写的档案管理员

                <guilabel>Copy to left foreground</guilabel>
              </para>
            </listitem>
            <listitem>
              <para>
                <guilabel>Copy to left background</guilabel>
              </para>
            </listitem>
            <listitem>
              <para>
                <guilabel>Copy to right foreground</guilabel>
              </para>
            </listitem>
            <listitem>
              <para>
                <guilabel>Copy to left background</guilabel>
              </para>
            </listitem>
            <listitem>
              <para>
                <guilabel>Delete foreground</guilabel>
              </para>
            </listitem>
            <listitem>
              <para>
                <guilabel>Delete background</guilabel>
              </para>
            </listitem>
          </itemizedlist>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>Preview</guilabel>
        </term>
        <listitem>
          <para>Here you see a preview of the configured
          colors.</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>Color schemes</guilabel>
        </term>
        <listitem>
          <para>With the 
          <guibutton>Import Color Scheme</guibutton> and 
          <guibutton>Export Color Scheme</guibutton> buttons you can
          load and save a Color Scheme profile. This allows
          &krusader; to use &tcmd;,
          &mc;, foo-commander or your own custom color
          profile. The Color Schemes are stored in 
          <filename>$KDEDIR/share/apps/krusader</filename>, the 
          <filename>foo.color</filename> is a binary file that holds
          the color scheme.</para>
          <tip>
            <para>&mc; and &tcmd; Color
            scheme files are provided. Please 
            <link linkend="help_krusader">upload your favorite
            Color schemes</link> so that they become available for
            the &krusader; community. Thanks!</para>
          </tip>
        </listitem>
      </varlistentry>
    </variablelist>
  </sect1>
  <sect1 id="konfig-general">
    <title>General</title>
    <para>Here you configure the basic operations.</para>
    <!-- OLD
<screenshot>
  <screeninfo>General configuration</screeninfo>
  <mediaobject>
  <imageobject><imagedata fileref="kggeneral.png" format="PNG"/></imageobject>
  <imageobject><imagedata fileref="kggeneral.png" format="EPS"/></imageobject>
  <textobject><phrase>General configuration</phrase></textobject>
  <caption><para>General configuration</para></caption>
  </mediaobject>
</screenshot>
-->
    <!--HTML_PARSING
<figure id="screenshot-kggeneral" float="1">
<title>General configuration</title>
<mediaobject>
<imageobject><imagedata fileref="kggeneral.png"/></imageobject>
<textobject><phrase>General configuration</phrase></textobject>
</mediaobject>
</figure>
HTML_PARSING-->
    <para>The following options determine basic aspects of
    operation: 
    <itemizedlist>
      <listitem>
        <para>
        <guilabel>Delete files/Move to trash</guilabel>: when
        &krusader; deletes files it can either 'really'
        delete them or move them to the trash folder, thereby
        making them available via &kde;'s trash.</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Use mimetype magic</guilabel>: mime type magic is
        a mechanism which allows &krusader; to inspect
        the files in the panels and determine their type even if
        the file has no identifying extension. For example, if you
        take an image file - 'image1.jpg' - and rename it to
        'image1', &krusader; will still know it's an
        image file and work with it accordingly. However, this mode
        of operation is slower (while refreshing the panel, or
        changing directories), so try &krusader; with
        and without mime type magic and decide what is best for
        you.</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Editor</guilabel>: choose what editor will be
        used when editing a file (via F4).</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Default viewer mode</guilabel>: either generic,
        text or hex mode.</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Viewer opens each file in a separate
        window</guilabel>: you can use the browsing tabs for
        navigation.</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Atomic extensions</guilabel>: predefined atomic extensions like <filename>tar.gz</filename> 
        are shown as one part in the <guilabel>Ext Column</guilabel> of the &list-panel-lnk;.</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Terminal</guilabel>: choose which terminal
        emulator will be used when &krusader; opens a
        console window (via F2, or Commands-&gt;Terminal
        menu option).</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Terminal Emulator sends Chdir on a panel
        change</guilabel>: if unchecked, there will be no 
        <command>cd</command> command sent to the Terminal Emulator
        if the panel folder changes.</para>
      </listitem>
      <listitem>
        <para>
        <guilabel>Temp Directory</guilabel>: this option selects
        the base directory for &krusader;'s temporary
        files. The actual files will be created in separate
        directories under the 'Temp directory', so that each user
        running &krusader; will have their own temporary
        subdirectories under the chosen directory. 
        <note>
          <para>You must choose a temporary directory to which all
          users running &krusader; have full
          permissions!</para>
        </note></para>
      </listitem>
    </itemizedlist></para>
  </sect1>
  <sect1 id="konfig-advanced">
    <title>Advanced</title>
    <para>This page handles more advanced issues, so you should
    double-check your actions here: modifying settings here 
    <remark>makes &krusader; a more powerful AND
    dangerous tool.</remark></para>
    <!-- OLD
<screenshot>
  <screeninfo>Advanced configuration</screeninfo>
  <mediaobject>
  <imageobject><imagedata fileref="kgadvanced.png" format="PNG"/></imageobject>
  <imageobject><imagedata fileref="kgadvanced.png" format="EPS"/></imageobject>
  <textobject><phrase>Advanced configuration</phrase></textobject>
  <caption><para>Advanced configuration</para></caption>
  </mediaobject>
</screenshot>
-->
    <!--HTML_PARSING
<figure id="screenshot-kgadvanced" float="1">
<title>Advanced configuration</title>
<mediaobject>
<imageobject><imagedata fileref="kgadvanced.png"/></imageobject>
<textobject><phrase>Advanced configuration</phrase></textobject>
</mediaobject>
</figure>
HTML_PARSING-->
    <para>The page is divided into three parts:</para>
    <variablelist>
      <varlistentry>
        <term>
          <guilabel>General</guilabel>
        </term>
        <listitem>
          <itemizedlist>
            <listitem>
              <para>
              <guilabel>Preserve attributes for local copy/move
              (slower)</guilabel>: If checked,
              &krusader; will try to preserve all
              attributes (time, owner, group) of the local files
              according to the source file depending on your 
              <link linkend="copying">permissions</link>.</para>
            </listitem>
            <listitem>
              <para>
              <guilabel>Automount filesystems</guilabel>: this
              makes &krusader; try to mount a file system
              before entering it. For example, if you click on 
              <filename class="directory">/mnt/cdrom</filename> (and
              <filename class="directory">
              /mnt/cdrom</filename> appears in 
              <filename class="directory">/etc/fstab</filename> as a
              mount point), &krusader; will check if it
              is mounted. If not, it will try and mount it for you
              and then enter, so that you would see the contents of
              your cdrom. Note, however, that &krusader;
              will NOT unmount when exiting 
              <filename class="directory">
              /mnt/cdrom</filename>.</para>
            </listitem>
            <listitem>
              <para>
              <guilabel>Do not use KDE media protocol for the
              Media button (if it is buggy or missing)</guilabel>:
              If checked, &krusader; will not use
              &kde; media protocol for the 
              <link linkend="list_panel">Media button</link>.
              Choose this when the media protocol is buggy (in some
              older &kde; versions) or if you have no
              kdebase package installed on your system.</para>
            </listitem>
            <listitem>
              <para>
              <guilabel>MountMan will not (un)mount the following
              mount points</guilabel>: If you have file systems that
              you do not want to accidentally unmount (or mount)
              then enter a list of mount points separated by commas
              (&eg; 
              <literal>/, /boot, /tmp</literal>) and
              &mountman-lnk; will not try to (un)mount
              them.</para>
            </listitem>
          </itemizedlist>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>Confirmations</guilabel>
        </term>
        <listitem>
          <para>By checking the options in this section,
          &krusader; will ask for confirmation before
          doing a specific action; otherwise, the following actions
          will be done without warning:</para>
          <itemizedlist>
            <listitem>
              <para>deleting non empty directorie(s)</para>
            </listitem>
            <listitem>
              <para>deleting file(s)</para>
            </listitem>
            <listitem>
              <para>copying file(s)</para>
            </listitem>
            <listitem>
              <para>moving file(s)</para>
            </listitem>
          </itemizedlist>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <guilabel>Fine-Tuning</guilabel>
        </term>
        <listitem>
          <itemizedlist>
            <listitem>
              <para>
              <guilabel>Icon Cache Size</guilabel>:
              &krusader; uses an icon cache, so it will not
              have to reload icons that have been used before. Of
              course, as the cache grows bigger, it can store more
              icons and further speed operations, but the memory
              footprint of &krusader; will become
              bigger.</para>
            </listitem>
            <listitem>
              <para>
              <guilabel>Arguments of updatedb</guilabel>: sets
              additional arguments for 
              <command>updatedb</command>, please read the manpages
              for more information.</para>
            </listitem>
          </itemizedlist>
        </listitem>
      </varlistentry>
    </variablelist>
  </sect1>
  <sect1 id="konfig-archives">
    <title>Archives</title>
    <para>This page handles the way &krusader; works
    with archives. In the 
    <guilabel>General</guilabel> section you will see a list of
    archive formats. Some are checked and some are grayed-out. The
    ones that are available (not grayed-out) are supported by
    &krusader;. If you check them, &krusader;
    will handle the archives transparently and let you open them as
    folders; otherwise, &krusader; will attempt to
    invoke an application which opens archives of that type. If a
    certain archive is grayed-out, it means that
    &krusader; could not find the appropriate executables
    in the configured path. The next archives are supported: ace,
    arj, bzip2, deb, gzip, iso, lha, rar, rpm, tar, zip and
    7-zip.</para>
    <!-- OLD
<screenshot>
  <screeninfo>Archives configuration</screeninfo>
  <mediaobject>
  <imageobject><imagedata fileref="kgarchives.png" format="PNG"/></imageobject>
  <imageobject><imagedata fileref="kgarchives.png" format="EPS"/></imageobject>
  <textobject><phrase>Archives configuration</phrase></textobject>
  <caption><para>Archives configuration</para></caption>
  </mediaobject>
</screenshot>
-->
    <!--HTML_PARSING
<figure id="screenshot-kgarchives" float="1">
<title>Archives configuration</title>
<mediaobject>
<imageobject><imagedata fileref="kgarchives.png"/></imageobject>
<textobject><phrase>Archives configuration</phrase></textobject>
</mediaobject>
</figure>
HTML_PARSING-->
    <para>If you have installed a certain archive application (let's
    say 
    <command>arj</command>) and want &krusader; to know
    about it, just click the 
    <guibutton>Auto Configure</guibutton> button.
    &krusader; will search for all supported executables
    and print a report listing the archive formats that can be
    handled. If the operation was successful the new archive should
    be available and checked.</para>
    <note>
      <para>Please install new packagers to your 
      <envar>PATH</envar> (&ie;: 
      <filename>/usr/bin</filename> or 
      <filename>/usr/local/bin</filename> &etc;)</para>
    </note>
    <para>The full path of the packagers is stored in the
    &konfigdependencie-lnk; (&eg; to handle
    ZIP archives, &krusader; needs the 
    <command>unzip</command> and 
    <command>zip</command> executables). It is possible that you need
    to manually configure the mimes to the protocols in the
    &konfigprotocol-lnk;.</para>
    <para>
      <guilabel>Fine-Tuning</guilabel>
      <itemizedlist>
        <listitem>
          <para>
          <guilabel>Allow moving into archives</guilabel>: this
          option allows you to move files into an archive (as
          opposed to just copying into the archive). The down side
          is that if a power failure occurs during the process, the
          files that were moved might already be deleted, but not
          yet packed into the archive. 
          <note>
            <para>If such a thing happens, the file(s) are NOT
            LOST. They were actually moved into a subfolder in
            &krusader;'s 
            <link linkend="konfig-general">temp directory</link>.
            You can search the directory and recover your
            files.</para>