/usr/share/doc/kildclient/html/ch13s01.xhtml is in kildclient-doc 3.2.0-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml"><head><title>13.1. Loading Plugins from the Command Line</title><link rel="stylesheet" type="text/css" href="docbook.css"/><link rel="stylesheet" type="text/css" href="kildclient.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"/><link rel="prev" href="chap_plugins.xhtml" title="Chapter 13. Plugins"/><link rel="next" href="ch13s02.xhtml" title="13.2. Getting Information About Plugins"/></head><body><header><div class="navheader"><table style="width: 100%; "><tr><th style="text-align: center; " colspan="3">13.1. Loading Plugins from the Command Line</th></tr><tr><td style="width: 20%; text-align: left; "><a accesskey="p" href="chap_plugins.xhtml">Prev</a> </td><th style="width: 60%; text-align: center; ">Chapter 13. Plugins</th><td style="width: 20%; text-align: right; "> <a accesskey="n" href="ch13s02.xhtml">Next</a></td></tr></table><hr/></div></header><section class="sect1" id="idm2418"><div class="titlepage"><div><div><h2 class="title" style="clear: both">13.1. Loading Plugins from the Command Line</h2></div></div></div><p>It is also possible to load plugins directly from the command
line, for those more comfortable with it and with Perl.</p><p>To load a plugin, the <code class="function">$world->loadplugin</code>
function is used. It must be called with one argument, which can be
either the full path to the file that defines the plugin, or just the
plugin name. But for this to work, the file must be installed in one
of the directories that KildClient looks for plugins. By default, two
locations are searched for: one is the <code class="filename">plugins</code> directory under KildClient's
directory in your HOME path (that is, <code class="filename">~/.kildclient/plugins</code> in UNIX systems).
The other is the <code class="filename">plugins</code>
directory under the directory where KildClient stores some of its
files (generally it is something like <code class="filename">/usr/local/share/kildclient/plugins</code>).</p><p>For example, here is how to load the <code class="literal">keypad</code>
plugin (which is a standard plugin distributed with
KildClient):</p><div class="example" id="idm2430"><div class="example-title">Example 13.1. Loading a plugin</div><div class="example-contents"><pre class="programlisting">
$world->loadplugin('keypad')
</pre></div></div><br class="example-break"/><p>As an additional example, the code below loads a plugin
specifying its full filename:</p><div class="example" id="idm2435"><div class="example-title">Example 13.2. Loading a plugin specifying the full filename</div><div class="example-contents"><pre class="programlisting">
$world->loadplugin('/home/joe/kildclient-plugins/attackplugin.pl')
</pre></div></div><br class="example-break"/><p>Either way, you should see a message saying that the plugin has
been loaded. It is now already working. If the plugin was already
loaded, loading will fail.</p><p>To always load the plugin when you connect to the World, either
use the World Editor as described above, or add the line that loads it
to your script file. See <a class="xref" href="sec_we_automation.xhtml#sec_we_scripting" title="4.5.1. Scripting">Section 4.5.1, “Scripting”</a>.</p><section class="sect2" id="idm2442"><div class="titlepage"><div><div><h3 class="title">13.1.1. Enabling and Disabling Plugins</h3></div></div></div><p>If you want to turn off a plugin temporarily, you can disable
it. Later, when you want it to work again, just reenable it.</p><p>To disable a plugin, use the
<code class="function">$world->displugin</code> function, passing as argument
the name of the plugin. What this function does is disable the
plugin's triggers, aliases, macros and timers. You can still call the
plugin functions directly.</p><p>To enable a plugin again, use the
<code class="function">$world->enaplugin</code> function, passing as argument
the name of the plugin.</p></section></section><footer><div class="navfooter"><hr/><table style="width: 100%; "><tr><td style="width: 40%; text-align: left; "><a accesskey="p" href="chap_plugins.xhtml">Prev</a> </td><td style="width: 20%; text-align: center; "><a accesskey="u" href="chap_plugins.xhtml">Up</a></td><td style="width: 40%; text-align: right; "> <a accesskey="n" href="ch13s02.xhtml">Next</a></td></tr><tr><td style="width: 40%; text-align: left; vertical-align: top; ">Chapter 13. Plugins </td><td style="width: 20%; text-align: center; "><a accesskey="h" href="index.xhtml">Home</a></td><td style="width: 40%; text-align: right; vertical-align: top; "> 13.2. Getting Information About Plugins</td></tr></table></div></footer></body></html>
|