in particular those found in docs still keeping old path in modules/config/shells.nix for unkown reason (?)
81 lines
3 KiB
XML
81 lines
3 KiB
XML
<chapter xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink">
|
|
|
|
<title>Configuration in home directory</title>
|
|
|
|
|
|
<!--===============================================================-->
|
|
|
|
<section>
|
|
<title>Compiz Fusion</title>
|
|
<para>
|
|
Compiz Fusion is just a set of plugins for Compiz. Your best interest is to have
|
|
them found both by Compiz and by Compiz Configuration Settings (also in Compiz Fusion
|
|
distribution). By default they look in Compiz installation path and in home directory.
|
|
You do not need to track /nix/store manually - everything is already in
|
|
/run/current-system/sw/share.
|
|
|
|
<orderedlist>
|
|
<listitem><para><filename>$HOME/.compiz/plugins</filename>
|
|
should contain plugins you want to load. All the installed
|
|
plugins are available in
|
|
<filename>/run/current-system/sw/share/compiz-plugins/compiz/</filename>,
|
|
so you can use symlinks to this directory.
|
|
</para></listitem>
|
|
|
|
<listitem><para><filename>$HOME/.compiz/metadata</filename>
|
|
should contain metadata (definition of configuration options) for plugins
|
|
you want to load. All the installed metadata is available in
|
|
<filename>/run/current-system/sw/share/compiz/</filename>,
|
|
so you can use symlinks to this directory.
|
|
</para></listitem>
|
|
|
|
<listitem><para>
|
|
Probably a way to load <literal>GConf</literal> configuration backend by default
|
|
should be found, but if you run <literal>Compiz</literal> with
|
|
<literal>GConf</literal> configuration (default for <literal>X server</literal> job
|
|
for now), you have to link
|
|
<filename>/run/current-system/sw/share/compizconfig/backends/</filename>
|
|
into <filename>$HOME/.compizconfig/backends</filename> directory.
|
|
</para></listitem>
|
|
|
|
</orderedlist>
|
|
|
|
To summarize the above, these are the commands you have to execute
|
|
<command>ln -s /run/current-system/sw/share/compiz/ $HOME/.compiz/metadata</command>
|
|
<command>ln -s /run/current-system/sw/share/compiz-plugins/compiz/ $HOME/.compiz/plugins</command>
|
|
<command>ln -s /run/current-system/sw/share/compizconfig/backends/ $HOME/.compizconfig/backends</command>
|
|
|
|
Now you can launch <literal>ccsm</literal> and configure everything. You should select
|
|
GConf as a backend in the preferences menu of <literal>ccsm</literal>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Pidgin-LaTeX</title>
|
|
<para>
|
|
To have pidgin-latex plugin working after installation, you need the following:
|
|
<orderedlist>
|
|
<listitem><para>
|
|
Symlink <filename>/run/current-system/sw/share/pidgin-latex/pidgin-latex.so</filename>
|
|
to <filename>$HOME/.purple/plugins/pidgin-latex.so</filename>
|
|
</para></listitem>
|
|
<listitem><para>
|
|
Enable smileys. If you do not want to, you can create
|
|
<filename>$HOME/.purple/smileys/empty/theme</filename> with the following contents:
|
|
<programlisting>
|
|
Name=Empty
|
|
Description=No predefined smileys
|
|
Author=Nobody
|
|
</programlisting>
|
|
Enabling this theme will enable smileys, but define none.
|
|
</para></listitem>
|
|
<listitem><para>
|
|
Enable the plugin.
|
|
</para></listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</section>
|
|
|
|
</chapter>
|