From 6a9e7bb4d349b419816891e85ae8e95c46b9d2f5 Mon Sep 17 00:00:00 2001 From: Berke Viktor Date: Sun, 28 Oct 2012 10:49:44 +0100 Subject: Further doc relocations and conversions --- plugins/fishlim/README | 45 -- plugins/perl/hexchat-perl.html | 1207 ------------------------------------ plugins/perl/hexchat-perldocs.html | 475 -------------- plugins/plugin20.html | 1141 ---------------------------------- plugins/python/hexchat-python.md | 545 ---------------- plugins/tcl/README | 55 -- 6 files changed, 3468 deletions(-) delete mode 100644 plugins/fishlim/README delete mode 100644 plugins/perl/hexchat-perl.html delete mode 100644 plugins/perl/hexchat-perldocs.html delete mode 100644 plugins/plugin20.html delete mode 100644 plugins/python/hexchat-python.md delete mode 100644 plugins/tcl/README (limited to 'plugins') diff --git a/plugins/fishlim/README b/plugins/fishlim/README deleted file mode 100644 index 00d7f682..00000000 --- a/plugins/fishlim/README +++ /dev/null @@ -1,45 +0,0 @@ - - - FiSHLiM - - http://fishlim.kodafritt.se/ - - -FiSHLiM is an XChat plugin for FiSH IRC encryption. It's my attempt at making -a simple, lightweight and secure plugin for this encryption protocol. - -For installation instructions, see the INSTALL file. - - -Features --------- - -Working: - * Sending/receiving messages - * Topic decryption - * Using unecrypted keys / keys without a password from blow.ini - * Pure protocol-level filtering (works with highlighting, nick coloring etc) - * Partially encrypted messages (i.e. prefixed with nickname by a bouncer) - -Not working: - * Key exchange - * Password-protected key storage - * Topic encryption - * Remote exploitation (hopefully!) - * Plaintext content that contain +OK is decrypted twice - - -Commands --------- - -/setkey [nick or #channel] password - - Sets the encryption key for the nick or channel to password. The keys - are stored in the configuration file in ~/.xchat2/blow.ini - - -/delkey nick-or-#channel - - Deletes the given nick or channel from the configuration file. - - diff --git a/plugins/perl/hexchat-perl.html b/plugins/perl/hexchat-perl.html deleted file mode 100644 index 6092047e..00000000 --- a/plugins/perl/hexchat-perl.html +++ /dev/null @@ -1,1207 +0,0 @@ - - - - -X-Chat 2 Perl Interface - - - - - - - - -

- X-Chat 2 Perl Interface -

- - - -

- -

X-Chat 2 Perl Interface
-
-

- -

- - -

X-Chat 2 Perl Interface

Introduction

This is the new Perl interface for X-Chat 2. However, due to changes in -xchat's plugin code you will need xchat 2.0.8 or above to load this. Scripts -written using the old interface will continue to work. If there are any -problems, questions, comments or suggestions please email them to the address -on the bottom of this page.

Constants

Priorities

Xchat::PRI_HIGHEST -
Xchat::PRI_HIGH -
Xchat::PRI_NORM -
Xchat::PRI_LOW -
Xchat::PRI_LOWEST -

Return values

Xchat::EAT_NONE - pass the event along -
Xchat::EAT_XCHAT - don't let xchat see this event -
Xchat::EAT_PLUGIN - don't let other scripts and plugins see this event but xchat will still see it -
Xchat::EAT_ALL - don't let anything else see this event -

Timer and fd hooks

Xchat::KEEP - keep the timer going or hook watching the handle -
Xchat::REMOVE - remove the timer or hook watching the handle -

hook_fd flags

Xchat::FD_READ - invoke the callback when the handle is ready for reading -
Xchat::FD_WRITE - invoke the callback when the handle is ready for writing -
Xchat::FD_EXCEPTION - invoke the callback if an exception occurs -
Xchat::FD_NOTSOCKET - indicate that the handle being hooked is not a socket -

Functions

`Xchat::register( $name, $version, [$description,[$callback]] )`

$name - The name of this script -
$version - This script's version -
$description - A description for this script -
$callback - This is a function that will be called when the is script - unloaded. This can be either a reference to a - function or an anonymous sub reference. -

This is the first thing to call in every script.

`Xchat::hook_server( $message, $callback, [\%options] )`

`Xchat::hook_command( $command, $callback, [\%options] )`

`Xchat::hook_print( $event,$callback, [\%options] )`

`Xchat::hook_timer( $timeout,$callback, [\%options | $data] )`

`Xchat::hook_fd( $handle, $callback, [ \%options ] )`

These functions can be to intercept various events. -hook_server can be used to intercept any incoming message from the IRC server. -hook_command can be used to intercept any command, if the command doesn't currently exist then a new one is created. -hook_print can be used to intercept any of the events listed in Setttings->Advanced->Text Events -hook_timer can be used to create a new timer

$message - server message to hook such as PRIVMSG -

$command - command to intercept, without the leading / -

$event - one of the events listed in Settings->Advanced->Text Events -

$timeout - timeout in milliseconds -

$handle - the I/O handle you want to monitor with hook_fd. This must be something that has a fileno. See perldoc -f fileno or fileno -
$callback - callback function, this is called whenever - the hooked event is trigged, the following are - the conditions that will trigger the different hooks. - This can be either a reference to a - function or an anonymous sub reference. -
\%options - a hash reference containing addional options for the hooks -

Valid keys for \%options:

- - - - - - - -

data	Additional data that is to be associated with the - hook. For timer hooks this value can be provided either as - `Xchat::hook_timer( $timeout, $cb,{data=>$data})` - or `Xchat::hook_timer( $timeout, $cb, $data )`. - However, this means that hook_timer cannot be provided - with a hash reference containing data as a key. example: - my $options = { data => [@arrayOfStuff] }; - Xchat::hook_timer( $timeout, $cb, $options ); - - In this example, the timer's data will be - [@arrayOfStuff] and not { data => [@arrayOfStuff] } - - This key is valid for all of the hook functions. - - Default is undef. -
priority	Sets the priority for the hook. - It can be set to one of the - `Xchat::PRI_*` constants. - - This key only applies to server, command - and print hooks. - - Default is `Xchat::PRI_NORM`. -
help_text	Text displayed for /help $command. - - This key only applies to command hooks. - - Default is "". -
flags	Specify the flags for a fd hook. - - See hook fd flags section for valid values. - - On Windows if the handle is a pipe you specify - Xchat::FD_NOTSOCKET in addition to any other flags you might be using. - - This key only applies to fd hooks. - Default is Xchat::FD_READ -

When callbacks are invoked

Each of the hooks will be triggered at different times depending on the type -of hook.

- - - - - - - - - - - - - -

Hook Type	When the callback will be invoked
server hooks	a `$message` message is - received from the server -
command hooks	the `$command` command is - executed, either by the user or from a script -
print hooks	X-Chat is about to print the message for the - `$event` event -
timer hooks	called every `$timeout` milliseconds - (1000 millisecond is 1 second) - the callback will be executed in the same context where - the hook_timer was called, if the context no longer exists - then it will execute in a random context -
fd hooks	depends on the flags that were passed to hook_fd - See hook_fd flags section. -

The value return from these hook functions can be passed to Xchat::unhook -to remove the hook.

Callback Arguments

All callback functions will receive their arguments in @_ like every -other Perl subroutine.

-Server and command callbacks
-
-$_[0] - array reference containing the IRC message or command and -arguments broken into words
-example:
-/command arg1 arg2 arg3
-$_[0][0] - command
-$_[0][1] - arg1
-$_[0][2] - arg2
-$_[0][3] - arg3
-
-$_[1] - array reference containing the Nth word to the last word
-example:
-/command arg1 arg2 arg3
-$_[1][0] - command arg1 arg2 arg3
-$_[1][1] - arg1 arg2 arg3
-$_[1][2] - arg2 arg3
-$_[1][3] - arg3
-
-$_[2] - the data that was passed to the hook function
-
-Print callbacks
-
-$_[0] - array reference containing the values for the - text event see Settings->Advanced->Text Events
-$_[1] - the data that was passed to the hook function
-
-Timer callbacks
-
-$_[0] - the data that was passed to the hook function
-
fd callbacks
-
-$_[0] - the handle that was passed to hook_fd
-$_[1] - flags indicating why the callback was called
-$_[2] - the data that was passed to the hook function
-

Callback return values

All server, command and print callbacks should return one of -the Xchat::EAT_* constants. -Timer callbacks can return Xchat::REMOVE to remove -the timer or Xchat::KEEP to keep it going

Miscellaneous Hook Related Information

For server hooks, if $message is "RAW LINE" then $cb will be called for -every IRC message than X-Chat receives.

For command hooks if $command is "" then $cb will be called for -messages entered by the user that is not a command.

For print hooks besides those events listed in -Settings->Advanced->Text Events, these additional events can be used.

- - - - - - - - - - - - - - - -

Event	Description
"Open Context"	a new context is created
"Close Context"	a context has been close
"Focus Tab"	when a tab is brought to the front
"Focus Window"	when a top level window is focused or the - main tab window is focused by the window manager -
"DCC Chat Text"	when text from a DCC Chat arrives. - `$_[0]` will have these values - - `$_[0][0]` - Address - `$_[0][1]` - Port - `$_[0][2]` - Nick - `$_[0][3]` - Message -
"Key Press"	used for intercepting key presses - $_[0][0] - key value - $_[0][1] - state bitfield, 1 - shift, 4 - control, 8 - alt - $_[0][2] - string version of the key which might be empty for unprintable keys - $_[0][3] - length of the string in $_[0][2] -

`Xchat::unhook( $hook )`

$hook - the hook that was previously returned by one of the Xchat::hook_* functions -

This function is used to removed a hook previously added with one of -the Xchat::hook_* functions

It returns the data that was passed to the Xchat::hook_* function when -the hook was added

`Xchat::print( $text | \@lines, [$channel,[$server]] )`

$text - the text to print -
\@lines - array reference containing lines of text to be printed - all the elements will be joined together before printing -
$channel - channel or tab with the given name where $text - will be printed -
$server - specifies that the text will be printed in a channel or tab - that is associated with $server -

The first argument can either be a string or an array reference of strings. -Either or both of $channel and $server can be undef.

If called as Xchat::print( $text ), it will always return true. -If called with either the channel or the channel and the server -specified then it will return true if a context is found and -false otherwise. The text will not be printed if the context -is not found. The meaning of setting $channel or $server to -undef is the same as -find_context.

`Xchat::printf( $format, LIST )`

$format - a format string, see "perldoc -f sprintf" for further detail -
LIST - list of values for the format fields -

`Xchat::command( $command | \@commands, [$channel,[$server]] )`

$command - the command to execute, without the leading / -
\@commands - array reference containing a list of commands to execute -
$channel - channel or tab with the given name where $command will be executed -
$server - specifies that the command will be executed in a channel or tab that is associated with $server -

The first argument can either be a string or an array reference of strings. -Either or both of $channel and $server can be undef.

If called as Xchat::command( $command ), it will always return true. -If called with either the channel or the channel and the server -specified then it will return true if a context is found and false -otherwise. The command will not be executed if the context is not found. -The meaning of setting $channel or $server to undef is the same -as find_context.

`Xchat::commandf( $format, LIST )`

$format - a format string, see "perldoc -f sprintf" for further detail -
LIST - list of values for the format fields -

`Xchat::find_context( [$channel, [$server]] )`

$channel - name of a channel -
$server - name of a server -

Either or both of $channel and $server can be undef. Calling -Xchat::find_context() is the same as calling -Xchat::find_context( undef, undef) and -Xchat::find_context( $channel ) is -the same as Xchat::find_context( $channel, undef ).

If $server is undef, find any channel named $channel. -If $channel is undef, find the front most window -or tab named $server.If both $channel and -$server are undef, find the currently focused tab or window.

Return the context found for one of the above situations or undef if such -a context cannot be found.

`Xchat::get_context()`

Returns the current context.

`Xchat::set_context( $context | $channel,[$server] )`

$context - context value as returned from get_context,find_context or one - of the fields in the list of hashrefs returned by list_get -
$channel - name of a channel you want to switch context to -
$server - name of a server you want to switch context to -

See find_context for more details on $channel and $server.

Returns true on success, false on failure

`Xchat::get_info( $id )`

$id - one of the following case sensitive values -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ID	Return value	Associated Command(s)
away	away reason or undef if you are not away	AWAY, BACK
channel	current channel name	SETTAB
charset	character-set used in the current context	CHARSET
event_text <Event Name>	text event format string for <Event name> - Example: - - 1 - - my $channel_msg_format = Xchat::get_info( "event_text Channel Message" ); - - -
host	real hostname of the current server
id	connection id
inputbox	contents of the inputbox	SETTEXT
libdirfs	the system wide directory where xchat will look for plugins. - this string is in the same encoding as the local file system
modes	the current channels modes or undef if not known	MODE
network	current network name or undef, this value is taken from the Network List
nick	current nick	NICK
nickserv	nickserv password for this network or undef, this value is taken from the Network List
server	current server name - (what the server claims to be) undef if not connected -
state_cursor	current inputbox cursor position in characters	SETCURSOR
topic	current channel topic	TOPIC
version	xchat version number
win_status	status of the xchat window, possible values are "active", "hidden" - and "normal"	GUI
win_ptr	native window pointer, GtkWindow * on Unix, HWND on Win32. - On Unix if you have the Glib module installed you can use my $window = Glib::Object->new_from_pointer( Xchat::get_info( "win_ptr" ) ); to get a Gtk2::Window object. - Additionally when you have detached tabs, each of the windows will return a different win_ptr for the different Gtk2::Window objects. - See char_count.pl for a longer example of a script that uses this to show how many characters you currently have in your input box. -
gtkwin_ptr	similar to win_ptr except it will always be a GtkWindow *
xchatdir	xchat config directory encoded in UTF-8 - examples: - /home/user/.xchat2 - C:\Documents and Settings\user\Application Data\X-Chat 2 -
xchatdirfs	same as xchatdir except encoded in the locale file system encoding

This function is used to retrieve certain information about the current -context. If there is an associated command then that command can be used to change the value for a particular ID.

`Xchat::get_prefs( $name )`

$name - name of a X-Chat setting (available through the /set command) -

This function provides a way to retrieve X-Chat's setting information.

Returns undef if there is no setting called called $name.

`Xchat::emit_print( $event, LIST )`

$event - name from the Event column in Settings->Advanced->Text Events -
LIST - this depends on the Description column on the bottom of Settings->Advanced->Text Events -

This functions is used to generate one of the events listed under -Settings->Advanced->Text Events

Note: when using this function you MUST return Xchat::EAT_ALL otherwise you will end up with duplicate events. -One is the original and the second is the one you emit.

Returns true on success, false on failure

`Xchat::send_modes( $target | \@targets, $sign, $mode, [ $modes_per_line ] )`

$target - a single nick to set the mode on -
\@targets - an array reference of the nicks to set the mode on -
$sign - the mode sign, either '+' or '-' -
$mode - the mode character such as 'o' and 'v', this can only be one character long -
$modes_per_line - an optional argument maximum number of modes to send per at once, pass 0 use the current server's maximum (default) -

Send multiple mode changes for the current channel. It may send multiple MODE lines if the request doesn't fit on one.

Example:

use strict;
-use warning;
-use Xchat qw(:all);
-
-hook_command( "MODES", sub {
-   my (undef, $who, $sign, $mode) = @{$_[0]};
-   my @targets = split /,/, $who;
-   if( @targets > 1 ) {
-      send_modes( \@targets, $sign, $mode, 1 );
-   } else {
-      send_modes( $who, $sign, $mode );
-   }
-   return EAT_XCHAT;
-});
-

`Xchat::nickcmp( $nick1, $nick2 )`

$nick1, $nick2 - the two nicks or channel names that are to be compared -

The comparsion is based on the current server. Either a RFC1459 compliant -string compare or plain ascii will be using depending on the server. The -comparison is case insensitive.

Returns a number less than, equal to or greater than zero if -$nick1 is -found respectively, to be less than, to match, or be greater than -$nick2.

`Xchat::get_list( $name )`

$name - name of the list, one of the following: -"channels", "dcc", "ignore", "notify", "users" -

This function will return a list of hash references. The hash references -will have different keys depend on the list. An empty list is returned -if there is no such list.

"channels" - list of channels, querys and their server

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Key	Description
channel	tab name
chantypes	channel types supported by the server, typically "#&"
context	can be used with set_context
flags	Server Bits: - 0 - Connected - 1 - Connecting - 2 - Away - 3 - EndOfMotd(Login complete) - 4 - Has WHOX - 5 - Has IDMSG (FreeNode) - - The following correspond to the /chanopt command - 6 - Hide Join/Part Message (text_hidejoinpart) - 7 - unused (was for color paste) - 8 - Beep on message (alert_beep) - 9 - Blink Tray (alert_tray) - 10 - Blink Task Bar (alert_taskbar) - Example of checking if the current context has Hide Join/Part messages set: - - 1 - 2 - 3 - - if( Xchat::context_info->{flags} & (1 << 6) ) { - Xchat::print( "Hide Join/Part messages is enabled" ); -} - -
id	Unique server ID
lag	lag in milliseconds
maxmodes	Maximum modes per line
network	network name to which this channel belongs
nickprefixes	Nickname prefixes e.g. "+@"
nickmodes	Nickname mode chars e.g. "vo"
queue	number of bytes in the send queue
server	server name to which this channel belongs
type	the type of this context - 1 - server - 2 - channel - 3 - dialog - 4 - notices - 5 - server notices -
users	Number of users in this channel

"dcc" - list of DCC file transfers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Key	Value
address32	address of the remote user(ipv4 address)
cps	bytes per second(speed)
destfile	destination full pathname
file	file name
nick	nick of the person this DCC connection is connected to
port	TCP port number
pos	bytes sent/received
poshigh	bytes sent/received, high order 32 bits
resume	point at which this file was resumed - (zero if it was not resumed) -
resumehigh	point at which this file was resumed, high order 32 bits -
size	file size in bytes low order 32 bits
sizehigh	file size in bytes, high order 32 bits (when the files is > 4GB)
status	DCC Status: - 0 - queued - 1 - active - 2 - failed - 3 - done - 4 - connecting - 5 - aborted -
type	DCC Type: - 0 - send - 1 - receive - 2 - chatrecv - 3 - chatsend -

"ignore" - current ignore list

- - - - - - -

Key	Value
mask	ignore mask. e.g: !@*.aol.com
flags	Bit field of flags. - 0 - private - 1 - notice - 2 - channel - 3 - ctcp - 4 - invite - 5 - unignore - 6 - nosave - 7 - dcc -

"notify" - list of people on notify

- - - - - - - - - - - - - - - - - -

Key	Value
networks	comma separated list of networks where you will be notfified about this user's online/offline status or undef if you will be notificed on every network you are connected to
nick	nickname
flags	0 = is online
on	time when user came online
off	time when user went offline
seen	time when user was last verified still online

the values indexed by on, off and seen can be passed to localtime -and gmtime, see perldoc -f localtime and perldoc -f gmtime for more -detail

"users" - list of users in the current channel

- - - - - - - - - - - - - - - - - - - - - -

Key	Value
away	away status(boolean)
lasttalk	last time a user was seen talking, this is the an epoch time(number of seconds since a certain date, that date depends on the OS)
nick	nick name
host	host name in the form: user@host or undef if not known
prefix	prefix character, .e.g: @ or +
realname	Real name or undef
selected	selected status in the user list, only works when retrieving the user list of the focused tab. You can use the /USELECT command to select the nicks

"networks" - list of networks and the associated settings from network list

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Key

Value

autojoins

An object with the following methods:
- - - - - - - - - - - - - - - - - - - - - - - - - - -

Method	Description
channels()	returns a list of this networks' autojoin channels in list context, a count of the number autojoin channels in scalar context
keys()	returns a list of the keys to go with the channels, the order is the same as the channels, if a channel doesn't have a key, '' will be returned in it's place
pairs()	a combination of channels() and keys(), returns a list of (channels, keys) pairs. This can be assigned to a hash for a mapping from channel to key.
as_hash()	return the pairs as a hash reference
as_string()	the original string that was used to construct this autojoin object, this can be used with the JOIN command to join all the channels in the autojoin list
as_array()	return an array reference of hash references consisting of the keys "channel" and "key"
as_bool()	returns true if the network has autojoins and false otherwise

connect_commands

An array reference containing the connect commands for a network. An empty array if there aren't any

encoding

the encoding for the network

flags

- a hash reference corresponding to the checkboxes in the network edit window - - - - - - - - - - - - - - - - - - - - -

allow_invalid	true if "Accept invalid SSL certificate" is checked
autoconnect	true if "Auto connect to this network at startup" is checked
cycle	true if "Connect to selected server only" is NOT checked
use_global	true if "Use global user information" is checked
use_proxy	true if "Bypass proxy server" is NOT checked
use_ssl	true if "Use SSL for all the servers on this network" is checked

irc_nick1

Corresponds with the "Nick name" field in the network edit window

irc_nick2

Corresponds with the "Second choice" field in the network edit window

irc_real_name

Corresponds with the "Real name" field in the network edit window

irc_user_name

Corresponds with the "User name" field in the network edit window

network

Name of the network

nickserv_password

Corresponds with the "Nickserv password" field in the network edit window

selected

Index into the list of servers in the "servers" key, this is used if the "cycle" flag is false

server_password

Corresponds with the "Server password" field in the network edit window

servers

An array reference of hash references with a "host" and "port" key. If a port is not specified then 6667 will be used.

`Xchat::user_info( [$nick] )`

$nick - the nick to look for, if this is not given your own nick will be - used as default -

This function is mainly intended to be used as a shortcut for when you need -to retrieve some information about only one user in a channel. Otherwise it -is better to use get_list. -If $nick is found a hash reference containing the same keys as those in the -"users" list of get_list is returned otherwise undef is returned. -Since it relies on get_list this function can only be used in a -channel context.

`Xchat::context_info( [$context] )`

$context - context returned from get_context, find_context and get_list, this is the context that you want infomation about. If this is omitted, it will default to current context. -

This function will return the information normally retrieved with get_info, except this is for the context that is passed in. The information will be returned in the form of a hash. The keys of the hash are the $id you would normally supply to get_info as well as all the keys that are valid for the items in the "channels" list from get_list. Use of this function is more efficient than calling get_list( "channels" ) and searching through the result.

Example:

use strict;
-use warnings;
-use Xchat qw(:all); # imports all the functions documented on this page
-
-register( "User Count", "0.1",
-   "Print out the number of users on the current channel" );
-hook_command( "UCOUNT", \&display_count );
-sub display_count {
-   prnt "There are " . context_info()->{users} . " users in this channel.";
-   return EAT_XCHAT;
-}
-

`Xchat::strip_code( $string )`

$string - string to remove codes from -

This function will remove bold, color, beep, reset, reverse and underline codes from $string. It will also remove ANSI escape codes which might get used by certain terminal based clients. If it is called in void context $string will be modified otherwise a modified copy of $string is returned.

Examples

Asynchronous DNS resolution with hook_fd

use strict;
-use warnings;
-use Xchat qw(:all);
-use Net::DNS;
-   
-hook_command( "BGDNS", sub {
-   my $host = $_[0][1];
-   my $resolver = Net::DNS::Resolver->new;
-   my $sock = $resolver->bgsend( $host );
-   
-   hook_fd( $sock, sub {
-      my $ready_sock = $_[0];
-      my $packet = $resolver->bgread( $ready_sock );
-      
-      if( $packet->authority && (my @answers = $packet->answer ) ) {
-         
-         if( @answers ) {
-            prnt "$host:";
-            my $padding = " " x (length( $host ) + 2);
-            for my $answer ( @answers ) {
-               prnt $padding . $answer->rdatastr . ' ' . $answer->type;
-            }
-         }
-      } else {
-         prnt "Unable to resolve $host";
-      }
-      
-      return REMOVE;
-   },
-   {
-      flags => FD_READ,
-   });
-   
-   return EAT_XCHAT;
-});
-

- -

Contact Information

Contact Lian Wan Situ at <atmcmnky [at] yahoo.com> for questions, comments and -corrections about this page or the Perl plugin itself. You can also find me -in #xchat on FreeNode under the nick Khisanth.

- - -

- X-Chat 2 Perl Interface -

- - - - diff --git a/plugins/perl/hexchat-perldocs.html b/plugins/perl/hexchat-perldocs.html deleted file mode 100644 index 10d8f314..00000000 --- a/plugins/perl/hexchat-perldocs.html +++ /dev/null @@ -1,475 +0,0 @@ -XChat - IRC (chat) client for UNIX - - - -

This interface is deprecated

- - - - - -

-
Xchat Perl Docs
- - -
- - -
- -Introduction -
-
- -
-
Good Hello!
-
The purpose of this page is to give people some quick documentation on the -things that they will encounter when they try to code scripts for X-Chat. -It is not meant to be a comprehensive programming tutorial, -by any means. If that's what you're looking for, then you can just keep on -looking.
-
If you're going to do any scripting with X-Chat at all, you will -need to know perl. It also won't hurt to have had experience writing tcl for -eggdrops or ircII scripts. Otherwise you're going to have to be very careful -to avoid creating conditions which could flood you offline or do other -not-so-optimal things. ;) Thankfully, it shouldn't take most intelligent -people more than a week (month on the outside) enough perl to do some nice -things in it. -Perl is a very flexible language.
-
You should probably also go read (or at least skim over and then carefully -bookmark this copy of the thing that defines how IRC works: RFC 1459. -Other documents that scripters might find useful would be this -nice list of server -numerics, and this list of changes -for Hybrid 6 which is something everyone on EFNet should read. In fact, I -strongly suggest saving copies of these documents to your local -hard drive, because you will be back to look at them again soon.
-
One last thing... While you may hear that RFC 1459 isn't being followed very -well, and this is partly true, do your absolute best to stick with RFC-compliant -behaviours anyway because otherwise there's a good chance that your script will -never interoperate properly with others, or at least just piss off a lot of other -people. Pay special attention to section 2.2 of the RFC.
-
- - -
-Standard Disclaimer - -
-This documentation is provided on an "as-is" basis and comes with no warranty of accuracy or usefulness, either expressed or implied. It is subject to change without any notice, and may contain omissions or errors which could cause your genitalia to shrivel and fall off, or spontaneously combust. If you have any further questions,
please feel free to seek professional help. -
- - -
- - -
- -About Handlers -
-
- -
-There are [currently] four basic ways to make things call the subroutines you write for X-Chat and they are: -
message handlers - Triggered by messagse sent from the IRC server to your client
-
command handlers - triggered by / commands typed in by the user at the keyboard
-
timeout handlers - triggered by gtk+
-
print handlers - triggered just before xchat calls its built in print handlers for events
-
- - -
- - -
- -About Exit Codes -
-
- -
-These are very important. Every time you set up a handler, it takes precedent over the built-in functions and commands of X-Chat. That is, whatever thing which triggered your subroutine will go to your code before it goes to X-Chat to be dealt with. In this way you can replace almost every built-in function that the client has with your own routines. The thing to remember is that if your code exits by hitting the end of your subroutine, or by a plain 'return' statement, processing of the event will go on to whatever other things have set up hooks for the event, and then (provided nothing else exits with a return value of 1) to X-Chat itself. There is only one problem with this, (which is solved by the brokering handler that I'll explain that later) and that is that you cannot really control what order the custom routines get called. Normally they will execute in order of which ones were installed first, but a single script has no real way of knowing this. Beware. -
- - -
- - -
- -About @_ -
-
- -
-If you've never heard of @_ before, then you've obviously not coded in perl. When a message handler triggers, the raw line from the IRC server is passed to the subroutine you specify in @_. When a command handler is triggered, only the arguments are passed to the routine through @_ and they are not broken into a list, but left as one long string. You'll have to parse those yourself with split. (I advise using s/\s+/ /g to collapse the blank space to single space first.) When a timer handler is triggered, I *think* absolutely nothing is passed in @_, but it's not like anything terrifically important could be passed along anyway. Be especially careful when setting up message handlers for mode changes, since the modes are not broken up into individual events like they are with eggdrop. The upside of this is that X-Chat has no mode hooks of it's own, so you don't have to worry about it too much. (This is not the case with the brokering handler, however.) -
- - -
- - -
- -About Context -
-
- -
-There are some really nice things about coding for X-Chat, and the biggest one is that it's fairly good about determining the proper context for things. If a server sends something that triggers a message handler, then you can be sure that unless you specify otherwise, that your IRC::print or IRC::command function call will go back to that server and that server alone. If you really really need to know what the current context is, use the IRC::get_info function as detailed below. -
- -
- - -
- - -
- -script initialization commands -
-
- - -
- - -
- -IRC::register(scriptname, version, shutdownroutine, unused); -
-
- -
-
This is the first function your script should call, example:
-
IRC::register ("my script", "1.0", "", "");
-
The "shutdownroutine" arg is a function that will be called when X-Chat shuts down, so you get a chance to save config files etc. You can omit this arg, it is optional. The "unused" arg is reserved for future use, for now just provide "". This function also returns X-Chat's version number.
-
- - -
- - -
- -Handler initialization commands -
-
- - -
- - -
- -IRC::add_message_handler(message, subroutine_name); -
-
- -
-
This function allows you to set up hooks to subroutines so that when a particular message arrives from the IRC server that you are connected to, it can be passed to a subroutine to be dealt with appropriately. The message argument is essentially the second solid token from the raw line sent by the IRC server, and X-Chat doesn't know that some numeric messages have associated text messages, so for now set up a handler for both if you want to be sure odd servers don't screw up your expectations. (Read: fear IRCNet.) The entire line sent by the IRC server will be passed to your subroutine in @_. For the completely uninitiated, messages are things like 'PRIVMSG', 'NOTICE', '372', etc.
-
- - -
- - -
- -IRC::add_command_handler(command, subroutine_name); -
-
- -
-
This function allows you to set up hooks for actual commands that the user can type into the text window. The arguments are passed to the subroutine via @_, and arrive as a single string. @_ will be null if no arguments are supplied. It's recommended that you be sure and collapse the excess whitespace with s/\s+/ /g before attempting to chop the line up with split. As mentioned earlier, exiting with an undefined return value will allow the command to be parsed by other handlers, while using a return value of 1 will signal the program that no further parsing needs to be done with this command.
-
- - -
- - -
- -IRC::add_timeout_handler(interval, subroutine_name); -
-
- -
-
This function allows you to set up hooks for subroutines to be called at a particular interval. The interval is measured in milliseconds, so don't use a particularly small value unless you wish to drive the CPU load through the roof. 1000ms = 1 second. No values will be passed to the routine via @_ and return values don't affect anything either.
-
- - -
- - -
- -IRC::add_print_handler(message, subroutine_name); -
-
- -
-
This function allows you to catch the system messages (those who generally start by three stars) and to execute a function each time an event appear. The events are those you can see in "Settings->Edit Events Texts". message is the name of the event (you can find it in the Edit Events box, "Events" column) , subroutine_name is the name of the function that will get messages. Be carrful: all the arguments are sent to function in $_[0] separated by spaces.
-
- - -
- - -
- -Output commands -
-
- - -
- - -
- -IRC::print(text); -
-
- -
-This is a very simple routine. All it does is put the contents of the text string to the current window. The current window will be whichever window a command was typed into when called from a command handler, or in whichever window the message command is appropriate to if it is called from within a message handler. As with any perl program, newlines are not assumed, so don't forget to end the line with \n if you don't want things to look screwey. -
- - -
- - -
- -IRC::print_with_channel( text, channelname, servername ); -
-
- -
-This routine does the same thing as IRC::Print does, except it allows you to direct the output to a specific window. It returns 1 on success, 0 on fail. -
- - -
- - -
- -IRC::command(text); -
-
- -
-This routine allows you to execute commands in the current context. The text string containing the command will be parsed by everything that would normally parse a command, including your own command handlers, so be careful. Newlines are assumed, thankfully. -
- - -
- - -
- -IRC::command_with_server(text, servername); -
-
- -
-This routine allows you to specify the context of the server for which the command will be executed. It's not particularly useful unless you're managing a connection manually, yet the command still exists for it's usefulness in doing things like managing a bnc connection, etc. Newlines are assumed here as well. -
- - -
- - -
- -IRC::send_raw(text); -
-
- -
-This routine is very useful in that it allows you to send a string directly to the IRC server you are connected to. It is assumed that the server will be the one you first connected to if there is no clear context for the command, otherwise it will go to whatever server triggered the message handler or command handler window. You must specify newlines here always or you can be guaranteed that strange things will happen. The text message you specify should be a proper RAW IRC message, so don't play with it if you don't know how to do these. Additionally, while newlines are also not assumed here as with the IRC::print function, the RFC specifies that newlines are a CR+LF pair, even if most servers will accept a mere newline. It's best to play it safe and use \r\n instead of just \n. -
- - -
- - -
- -Information retrieval commands -
-
- - -
- - -
- -IRC::get_info(integer); -
-
- -
-This function returns a bit of selected information depending on what the value of the integer is. -Here's a list of the currently supported values: -
0 - xchat version
-
1 - your nickname
-
2 - channel
-
3 - server
-
4 - xchatdir
-
5 - away status
-
6 - network name
-
7 - server hostname
-
8 - channel topic
-
If you are requesting information that isn't available in the current context, then it will return null.
-
Any numbers other than the above will return an error message.
-
- - -
- - -
- -IRC::get_prefs(var); -
-
- -
-This command lets you read the preferences that are set in the xchat configuration file. Just look at the xchat.conf dir to see what variables are available to use with this command. Returns the value of the variable requested or "Unknown Variable" if the variable isn't available. -
- - -
- - -
- -IRC::user_info( nickname ); -
-
- -
-Returns a flat list of information on the nickname specified consisting of... nickname, nick host, and whether they have op or voice in the current context. -
- - -
- - -
- -IRC::channel_list( ); -
-
- -
-This command returns a flat list which contains the current channel, server, and nickname for all channels the client is currently in. You'll have to break the list up into groups of three yourself. No arguments are necessary, or used [currently]. -
- - -
- - -
- -IRC::server_list( ); -
-
- -
-This command returns a flat list of servers. (Note, it is incompatible with xchat 1.8 in that it also returns a list of servers you are NOT connected to as well.) -
- - -
- - -
- -IRC::user_list(channel, server); -
-
- -
-
Works very much like the dcc_list command below, except that is returns information about the users on the channel provided as first argument. The second argument is the server and is optional.
-
NOTE: If a user has both op and voice, only the op flag will be set to 1 by this command in xchat2.
-
- - -
- - -
- -IRC::user_list_short(channel, server); -
-
- -
-
A simpler version of IRC::user_list that returns pairs of nick & user@host suitable for assigning to a hash.
-
NOTE: If a user has both op and voice, only the op flag will be set to 1 by this command in xchat2.
-
- - -
- - -
- -IRC::dcc_list( ); -
-
- -
-This command does essentially the same thing as channel_list, giving you the details of each DCC connection currently in progress. I have no idea exactly what is returned because I haven't had a chance to poke at this one much, but suffice it to say that it's a flat list, and the first time you play with it the meaning of the returned values should be pretty obvious. -
- - -
- - -
- -IRC::ignore_list( ); -
-
- -
-This command returns a flat list of the contents of your ignore list. You'll have to play with it a little as I have not had a chance to yet. Works basically the same as the other list commands. -
- - -
- - -
- -Unimplemented commands that were available in xchat 1.8.x -
-
- -
-add_user_list , sub_user_list , clear_user_list, notify_list were available in xchat 1.8.x but are not implemented in xchat 2 at this time. -
- -

-This document originally written by Dagmar d'Surreal on March 26th, 1998 for xchat 1.4
-Updated on July 30th, 1999 by Peter Zelezny
-Updated on May 16th, 2003 by DaNumber8 to comply with the perl plugin for xchat2 version 2.0.3 - diff --git a/plugins/plugin20.html b/plugins/plugin20.html deleted file mode 100644 index e17f3346..00000000 --- a/plugins/plugin20.html +++ /dev/null @@ -1,1141 +0,0 @@ - - - -HexChat 2 Plugin Interface - - - - -

HexChat 2 Plugin Interface

- - -plugin20.html revision 2.9.1 -
Latest version of this document is available at: https://github.com/hexchat/hexchat/wiki/Plugins - -

1. Documentation:

-1.0 Introduction -
1.1 Sample plugin -
1.2 What is word and word_eol? -
1.3 Lists and fields -
1.4 Plugins on Windows (Win32) -
1.5 Controlling the GUI -
1.5.1 Basic Control -
1.5.2 Custom Menu Items -
1.5.3 System Tray -
1.6 Handling UTF-8/Unicode strings -

- -

2. Function reference:

-xchat_hook_command -
xchat_hook_fd -
xchat_hook_print -
xchat_hook_server -
xchat_hook_timer -
xchat_unhook -
-
xchat_command -
xchat_commandf -
xchat_print -
xchat_printf -
xchat_emit_print -
xchat_send_modes -
-
xchat_find_context -
xchat_get_context -
xchat_get_info -
xchat_get_prefs -
xchat_set_context -
-
xchat_nickcmp -
xchat_strip -
xchat_free -
-
xchat_pluginpref_set_str -
xchat_pluginpref_get_str -
xchat_pluginpref_set_int -
xchat_pluginpref_get_int -
xchat_pluginpref_delete -
xchat_pluginpref_list -
-
xchat_list_get -
xchat_list_free -
xchat_list_fields (not documented yet) -
xchat_list_next -
xchat_list_str -
xchat_list_int -
xchat_list_time -
-
xchat_plugingui_add (not documented yet) -
xchat_plugingui_remove (not documented yet) -

- -

Introduction

-Plugins for HexChat are written in C. The interface aims to keep 100% -binary compatability. This means that if you upgrade HexChat, you will -not need to recompile your plugins, they'll continue to work. The -interface doesn't depend on any structures and offsets, so compiler -versions shouldn't have an impact either. The only real requirement of -an HexChat plugin, is that it define a "xchat_plugin_init" symbol. This -is your entry point function, see the example below. You should make -all your global variables and functions static, so that a symbol -is not exported. There is no harm in exporting these symbols, but they -are not necessary and only pollute the name-space. Plugins are compiled as shared objects -(.so files), for example: -

-Most UNIX systems:

-	gcc -Wl,--export-dynamic -Wall -O1 -shared -fPIC myplugin.c -o myplugin.so
-

-MacOSX:

-	gcc -no-cpp-precomp -g -O2 -Wall -bundle -flat_namespace -undefined suppress -o myplugin.so myplugin.c
-

- -See the Windows section on how to compile a plugin -using visual studio. -

-All strings passed to and from plugins are encoded in UTF-8, regardless -of locale. What does this mean? -

- -

Sample plugin

-This simple plugin autoOps anyone who joins a channel you're in. It also -adds a new command /AUTOOPTOGGLE, which can be used to turn the feature ON -or OFF. Every HexChat plugin must define an xchat_plugin_init function, this -is the normal entry point. xchat_plugin_deinit is optional. -
-

-
-#include "xchat-plugin.h"
-
-#define PNAME "AutoOp"
-#define PDESC "Auto Ops anyone that joins"
-#define PVERSION "0.1"
-
-static hexchat_plugin *ph;   /* plugin handle */
-static int enable = 1;
-
-static int join_cb(char *word[], void *userdata)
-{
-   if (enable)
-      /* Op ANYONE who joins */
-      xchat_commandf(ph, "OP %s", word[1]);
-   /* word[1] is the nickname, as in the Settings->Advanced->TextEvents window in xchat */
-
-   return XCHAT_EAT_NONE;  /* don't eat this event, HexChat needs to see it! */
-}
-
-static int autooptoggle_cb(char *word[], char *word_eol[], void *userdata)
-{
-   if (!enable)
-   {
-      enable = 1;
-      xchat_print(ph, "AutoOping now enabled!\n");
-   } else
-   {
-      enable = 0;
-      xchat_print(ph, "AutoOping now disabled!\n");
-   }
-
-   return XCHAT_EAT_ALL;   /* eat this command so HexChat and other plugins can't process it */
-}
-
-void xchat_plugin_get_info(char **name, char **desc, char **version, void **reserved)
-{
-   *name = PNAME;
-   *desc = PDESC;
-   *version = PVERSION;
-}
-
-int xchat_plugin_init(xchat_plugin *plugin_handle,
-                      char **plugin_name,
-                      char **plugin_desc,
-                      char **plugin_version,
-                      char *arg)
-{
-   /* we need to save this for use with any xchat_* functions */
-   ph = plugin_handle;
-
-   /* tell HexChat our info */
-   *plugin_name = PNAME;
-   *plugin_desc = PDESC;
-   *plugin_version = PVERSION;
-
-   xchat_hook_command(ph, "AutoOpToggle", XCHAT_PRI_NORM, autooptoggle_cb, "Usage: AUTOOPTOGGLE, Turns OFF/ON Auto Oping", 0);
-   xchat_hook_print(ph, "Join", XCHAT_PRI_NORM, join_cb, 0);
-
-   xchat_print(ph, "AutoOpPlugin loaded successfully!\n");
-
-   return 1;       /* return 1 for success */
-}
-
-

- -

What's word and word_eol?

- -They are arrays of strings. They contain the parameters the user entered -for the particular command. For example, if you executed: - -

-/command NICK hi there
-
-word[1] is command
-word[2] is NICK
-word[3] is hi
-word[4] is there
-
-word_eol[1] is command NICK hi there
-word_eol[2] is NICK hi there
-word_eol[3] is hi there
-word_eol[4] is there
-

-These arrays are simply provided for your convenience. You are NOT allowed -to alter them. Both arrays are limited to 32 elements (index 31). word[0] and -word_eol[0] are reserved and should not be read. -

-

Lists and Fields

-Lists of information (DCCs, Channels, Userlist etc) can be retreived -with xchat_list_get. All fields are READ ONLY and must be copied if -needed for a long time after calling xchat_list_str. The types of lists and fields available are: -

- -"channels" - list of channels, querys and their servers. -
- - - - - - - - - - - - - - - -
Name Description Type
channel Channel or query name string
chantypes Channel types e.g. "#!&"
(Added in version 2.0.9. Older versions will return NULL) string
context (xchat_context *) pointer. Can be used with xchat_set_context string
flags Server/Channel Bits:
- - - - - - - - - - - - - -
Bit # Value Description
0 1 Connected
1 2 Connecting in Progress
2 4 You are away
3 8 End of MOTD (Login complete)
4 16 Has WHOX (ircu)
5 32 Has IDMSG (FreeNode)
6 64 Hide Join/Part Messages
7 128 unused (was Color Paste in old versions)
8 256 Beep on Message
9 512 Blink Tray
10 1024 Blink Task Bar
-
(Bits 0-5 added in 2.0.9. Bits 6-8 added in 2.6.6. Bit 9 added in 2.8.0. Bit 10 in 2.8.6) int
id Unique server ID
(Added in version 2.0.8. Older versions will return -1) int
lag Lag in milliseconds
(Added in version 2.6.8. Older versions will return -1) int
maxmodes Maximum modes per line
(Added in version 2.0.9. Older versions will return -1) int
network Network name to which this channel belongs
(Added in version 2.0.2. Older versions will return NULL) string
nickprefixes Nickname prefixes e.g. "@+"
(Added in version 2.0.9. Older versions will return NULL) string
nickmodes Nickname mode chars e.g. "ov"
(Added in version 2.0.9. Older versions will return NULL) string
queue Number of bytes in the send-queue
(Added in version 2.6.8. Older versions will return -1) int
server Server name to which this channel belongs string
type Type of context this is: 1-Server 2-Channel 3-Dialog
(Added in version 2.0.2. Older versions will return -1) int
users Number of users in this channel
(Added in version 2.0.8. Older versions will return -1) int
-
- -"dcc" - list of DCC file transfers. Fields: -
- - - - - - - - - - - - - - - -
Name Description Type
address32 Address of the remote user (ipv4 address) int
cps Bytes per second (speed) int
destfile Destination full pathname string
file File name string
nick Nickname of person who the file is from/to string
port TCP port number int
pos Bytes sent/received int
poshigh Bytes sent/received, high order 32 bits int
resume Point at which this file was resumed (or zero if it was not resumed) int
resumehigh Point at which this file was resumed, high order 32 bits int
size File size in bytes, low order 32 bits (cast it to unsigned) int
sizehigh File size in bytes, high order 32 bits int
status DCC Status: 0-Queued 1-Active 2-Failed 3-Done 4-Connecting 5-Aborted int
type DCC Type: 0-Send 1-Receive 2-ChatRecv 3-ChatSend int
-
- -"ignore" - current ignore list. -
- - - -
Name Description Type
mask Ignore mask. .e.g: *!*@*.aol.com string
flags Bit field of flags. 0=Private 1=Notice 2=Channel 3=Ctcp
-4=Invite 5=UnIgnore 6=NoSave 7=DCC int
-
- -"notify" - list of people on notify. -
- - - - - - - -
Name Description Type
networks Networks to which this nick applies. Comma separated. May be NULL. -
(Added in version 2.6.8) string
nick Nickname string
flags Bit field of flags. 0=Is online. int
on Time when user came online. time_t
off Time when user went offline. time_t
seen Time when user the user was last verified still online. time_t
-The entire "notify" list was added in xchat 2.0.8. Fields are -only valid for the context when xchat_list_get() was called -(i.e. you get information about the user ON THAT ONE SERVER ONLY). You -may cycle through the "channels" list to find notify information for every -server. -
- -"users" - list of users in the current channel. -
- - - - - - - - -
Name Description Type
away Away status (boolean)
(Added in version 2.0.6. Older versions will return -1) int
lasttalk Last time the user was seen talking
(Added in version 2.4.2. Older versions will return -1) time_t
nick Nick name string
host Host name in the form: user@host (or NULL if not known). string
prefix Prefix character, .e.g: @ or +. Points to a single char. string
realname Real name or NULL
(Added in version 2.8.6) string
selected Selected status in the user list, only works for retrieving the user list of the focused tab
(Added in version 2.6.1. Older versions will return -1) int
-
- -

- -Example: -
-

-   list = xchat_list_get(ph, "dcc");
-   if(list)
-   {
-      xchat_print(ph, "--- DCC LIST ------------------\n"
-                      "File  To/From   KB/s   Position\n");
-
-      while(xchat_list_next(ph, list))
-      {
-         xchat_printf(ph, "%6s %10s %.2f  %d\n",
-             xchat_list_str(ph, list, "file"),
-             xchat_list_str(ph, list, "nick"),
-             xchat_list_int(ph, list, "cps") / 1024,
-             xchat_list_int(ph, list, "pos"));
-      }
-
-      xchat_list_free(ph, list);
-   }
-

- -
- -

Plugins on Windows (Win32)

-Yes, it can be done. All you need is either -MSVC (Visual Studio) or -MINGW, both these compilers are free to download. -Simply compile your plugin as a DLL. You should have the following files: - -

hexchat-plugin.h - Main Plugin header
plugin.c - Your plugin, you need to write this one :)
plugin.def - A simple text file containing the following:

-EXPORTS
- xchat_plugin_init
- xchat_plugin_deinit
- xchat_plugin_get_info
-

- -
Leave out xchat_plugin_deinit if you don't intend to define that -function. Then, to compile, type this at your command prompt:

-

-MSVC -
cl -O1 -MD -G5 -DWIN32 -c plugin.c
-
link /DLL /out:plugin.dll /SUBSYSTEM:WINDOWS plugin.obj /def:plugin.def /base:0x00d40000 -

-GCC (MINGW) -
gcc -Wall -Os -DWIN32 -c plugin.c
-
dllwrap --def plugin.def --dllname plugin.dll plugin.o

-

-
For a complete example, have a look at the source code of the DNS Plugin, which also contains a Makefile. -

-Caveat: Plugins compiled on Win32 MUST have a -global variable called ph, which is the plugin_handle, much like -in the sample plugin above. -

- -

Controlling the GUI

-A simple way to perform basic GUI functions is to use the /GUI command. -You can execute this command through the input-box, or by calling -xchat_command(ph, "GUI .....");. -

- - - - - - - - - - - -
GUI ATTACH Same function as "Attach Window" in the HexChat menu (new for 2.6.2).
GUI DETACH Same function as "Detach Tab" in the HexChat menu (new for 2.6.2).
GUI APPLY Similar to clicking OK in the settings window. Execute this after /SET to activate GUI changes (new for 2.8.0)
GUI COLOR n Change the tab color of the current context, where n is a number from 0 to 3.
GUI FOCUS Focus the current window or tab.
GUI FLASH Flash the taskbar button. It will flash only if the window isn't focused and will stop when it is focused by the user.
GUI HIDE Hide the main HexChat window completely (this is used by the Systray plugin).
GUI ICONIFY Iconify (minimize to taskbar) the current HexChat window.
GUI MSGBOX text Displays a asynchronous message box with your text (new for 2.4.5).
GUI SHOW Show the main HexChat window (if currently hidden).
-

-Note, the FLASH, ICONIFY and COLOR args were added in xchat 2.0.8, they -will not work with previous versions. -

-Starting from 2.4.5 you can add your own items to the menu bar. The menu command has this syntax: -

-	MENU [-eX] [-i<ICONFILE>] [-k<mod>,<key>] [-m] [-pX] [-rX,group] [-tX] {ADD|DEL} <path> [command] [unselect command]

-For example: -

-	MENU -p5 ADD FServe
-	MENU ADD "FServe/Show File List" "fs list"
-	MENU ADD FServe/-
-	MENU -k4,101 -t1 ADD "FServe/Enabled" "fs on" "fs off"
-	MENU -e0 ADD "FServe/Do Something" "fs action"
-

-In the example above, it would be recommended to execute "MENU DEL FServe" inside your xchat_plugin_deinit function. The special item with name "-" will add a separator line. -

-Parameters and flags: -

- - - - - - - - -
-eX Set enable flag to X. -e0 for disable, -e1 for enable. This lets you create a disabled (shaded) item.
-iFILE Use an icon filename FILE (new for 2.8.0). Not supported for toggles or radio items.
-k<mod>,<key> Specify a keyboard shortcut. "mod" is the modifier which is a bitwise OR of: 1-SHIFT 4-CTRL 8-ALT in decimal. "key" is the key value in decimal, e.g. -k5,101 would specify SHIFT-CTRL-E.
-m Specify that this label should be treated as Pango Markup language. Since forward slash ("/") is already used in menu paths, you should replace closing tags with an ASCII 003 instead e.g.: xchat_command(ph, "MENU -m ADD \"<b>Bold Menu<\003b>\""); (new for 2.6.6).
-pX Specify a menu item's position number. e.g. -p5 will cause the item to be inserted in the 5th place. New for 2.8.0: If the position is a negative number, it will be used as an offset from the bottom/right-most item.
-rX,group Specify a radio menu item, with initial state X and a group name (new for 2.8.0). The group name should be the exact label of another menu item (without the path) that this item will be grouped with. For radio items, only a select command will be executed (no unselect command).
-tX Specify a toggle menu item with an initial state. -t0 for an "unticked" item and -t1 for a "ticked" item.
-

- -If you want to change an item's toggle state or enabled flag, -just ADD an item with exactly the same name and command and specify the -tX -eX parameters you need. -

It's also possible to add items to HexChat's existing menus, for example:
-

	MENU ADD "Settings/Sub Menu"
-	MENU -t0 ADD "Settings/Sub Menu/My Setting" myseton mysetoff
-

-However, internal names and layouts of HexChat's menu may change in the future, so use at own risk. -

-Here is an example of Radio items: -

	MENU ADD "Language"
-	MENU -r1,"English" ADD "Language/English" cmd1
-	MENU -r0,"English" ADD "Language/Spanish" cmd2
-	MENU -r0,"English" ADD "Language/German" cmd3

-
-From 2.8.0, you can also change menus other than the main one (i.e popup menus). Currently they are: -

- - - - - - - - -
Root Name Menu
$TAB Tab menu (right click a channel/query tab or treeview row)
$TRAY System Tray menu
$URL URL link menu
$NICK Userlist nick-name popup menu
$CHAN Menu when clicking a channel in the text area (since 2.8.4)
-

-	Example: MENU -p0 ADD "$TAB/Cycle Channel" cycle
-

- -
-Starting from 2.8.0 you can manipulate HexChat's system tray icon using the /TRAY command: -

- Usage: 
- TRAY -f <timeout> <file1> [<file2>] Flash tray between two icons. Leave off file2 to use default HexChat icon.
- TRAY -f <filename>                  Set tray to a fixed icon.
- TRAY -i <number>                    Flash tray with an internal icon.
-                                     2=Message 5=Highlight 8=Private 11=File
- TRAY -t <text>                      Set the tray tooltip.
- TRAY -b <title> <text>              Set the tray balloon.
-                                     Supported on Windows from 2.8.1 and 2.8.2 on Linux (libnotify required on Linux).
-

-Filenames can be ICO or PNG format. PNG format is supported on Linux/BSD and Windows XP (but requires installation of GDI+ on Windows 2000). Set a timeout of -1 to use HexChat's default. -

- -

Handling UTF-8/Unicode strings

-The HexChat plugin API specifies that strings passed to and from HexChat must be encoded in UTF-8. -

-What does this mean for the plugin programmer? You just have to be a little careful when -passing strings obtained from IRC to system calls. For example, if you're writing a file-server -bot, someone might message you a filename. Can you pass this filename directly to open()? Maybe! -If you're lazy... The correct thing to do is to convert the string to "system locale encoding", -otherwise your plugin will fail on non-ascii characters. -

-Here are examples on how to do this conversion on Unix and Windows. In this example, someone will -CTCP you the message "SHOWFILE <filename>". -

-

-static int ctcp_cb(char *word[], char *word_eol[], void *userdata)
-{
-	if(strcmp(word[1], "SHOWFILE") == 0)
-	{
-		get_file_name(nick, word[2]);
-	}
-
-	return XCHAT_EAT_XCHAT;
-}
-
-static void get_file_name(char *nick, char *fname)
-{
-	char buf[256];
-	FILE *fp;
-
-	/* the fname is in UTF-8, because it came from the HexChat API */
-

#ifdef _WIN32

-	wchar_t wide_name[MAX_PATH];
-
-	/* convert UTF-8 to WIDECHARs (aka UTF-16LE) */
-	if (MultiByteToWideChar(CP_UTF8, 0, fname, -1, wide_name, MAX_PATH) < 1)
-		return;
-
-	/* now we have WIDECHARs, so we can _wopen() or CreateFileW(). */
-	/* _wfopen actually requires NT4, Win2000, XP or newer. */
-	fp = _wfopen(wide_name, "r");
-

#else

-	char *loc_name;
-
-	/* convert UTF-8 to System Encoding */
-	loc_name = g_filename_from_utf8(fname, -1, 0, 0, 0);
-	if(!loc_name)
-		return;
-
-	/* now open using the system's encoding */
-	fp = fopen(loc_name, "r");
-	g_free(loc_name);
-

#endif

-	if (fp)
-	{
-		while (fgets (buf, sizeof(buf), fp))
-		{
-			/* send every line to the user that requested it */
-			xchat_commandf (ph, "QUOTE NOTICE %s :%s", nick, buf);
-		}
-		fclose (fp);
-	}
-}
-

- - - -

- -

Functions

- -

xchat_hook_command()

-Prototype: xchat_hook *xchat_hook_command(xchat_plugin *ph, const char *name, int pri, xchat_cmd_cb *callb, const char *help_text, void *userdata); -
-
Description: Adds a new /command. This allows your program to -handle commands entered at the input box. To capture text without a "/" at -the start (non-commands), you may hook a special name of "". i.e xchat_hook_command(ph, "", ...);. -
-Starting from version 2.6.8, commands hooked that begin with a period ('.') will be hidden in /HELP and /HELP -l. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
name: Name of the command (without the forward slash). -
pri: Priority of this command. Use XCHAT_PRI_NORM. -
callb: Callback function. This will be called when the user executes the given command name. -
help_text: String of text to display when the user executes /help for this command. May be NULL if you're lazy. -
userdata: Pointer passed to the callback function.

-Returns: Pointer to the hook. Can be passed to xchat_unhook. -
-
Example: -

-static int onotice_cb(char *word[], char *word_eol[], void *userdata)
-{
-	if(word_eol[2][0] == 0)
-	{
-		xchat_printf(ph, "Second arg must be the message!\n");
-		return XCHAT_EAT_ALL;
-	}
-
-	xchat_commandf(ph, "NOTICE @%s :%s", xchat_get_info(ph, "channel"), word_eol[2]);
-	return XCHAT_EAT_ALL;
-}
-
-xchat_hook_command(ph, "ONOTICE", XCHAT_PRI_NORM, onotice_cb,
-                   "Usage: ONOTICE <message> Sends a notice to all ops", NULL);
-

-
- -

xchat_hook_fd()

-Prototype: xchat_hook *xchat_hook_fd(xchat_plugin *ph, int fd, int flags, xchat_fd_cb *callb, void *userdata); -
-
Description: Hooks a socket or file descriptor. WIN32: Passing a pipe from MSVCR71, MSVCR80 or other variations is not supported at this time. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
fd: The file descriptor or socket. -
flags: One or more of XCHAT_FD_READ, XCHAT_FD_WRITE, XCHAT_FD_EXCEPTION, XCHAT_FD_NOTSOCKET. Use bitwise OR to combine them. -XCHAT_FD_NOTSOCKET tells HexChat that the provided fd is not a socket, but a "MSVCRT.DLL" pipe. -
callb: Callback function. This will be called when the socket is available for reading/writing or exception (depending on your chosen flags) -
userdata: Pointer passed to the callback function.

-Returns: Pointer to the hook. Can be passed to xchat_unhook. -

- -

xchat_hook_print()

-Prototype: xchat_hook *xchat_hook_print(xchat_plugin *ph, const char *name, int pri, xchat_print_cb *callb, void *userdata); -
-
Description: Registers a function to trap any print events. -The event names may be any available in the "Advanced > Text Events" window. -There are also some extra "special" events you may hook using this function. -Currently they are:

-"Open Context" - Called when a new xchat_context is created. -
"Close Context" - Called when a xchat_context pointer is closed. -
"Focus Tab" - Called when a tab is brought to front. -
"Focus Window" - Called a toplevel window is focused, or the main -tab-window is focused by the window manager. -
"DCC Chat Text" - Called when some text from a DCC Chat arrives. It provides these elements in the word[] array:
word[1] Address -
word[2] Port -
word[3] Nick -
word[4] The Message -
-"Key Press" - Called when some keys are pressed in the input-box (since 2.4.2). It provides these elements in the word[] array:
word[1] Key Value -
word[2] State Bitfield (shift, capslock, alt) -
word[3] String version of the key -
word[4] Length of the string (may be 0 for unprintable keys) -
-

-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
name: Name of the print event (as in Edit Event Texts Window). -
pri: Priority of this command. Use XCHAT_PRI_NORM. -
callb: Callback function. This will be called when this event name is printed. -
userdata: Pointer passed to the callback function.

-Returns: Pointer to the hook. Can be passed to xchat_unhook. -
-
Example: -

-static int youpart_cb(char *word[], void *userdata)
-{
-	xchat_printf(ph, "You have left channel %s\n", word[3]);
-	return XCHAT_EAT_XCHAT;	/* dont let HexChat do its normal printing */
-}
-
-xchat_hook_print(ph, "You Part", XCHAT_PRI_NORM, youpart_cb, NULL);
-

-
- -

xchat_hook_server()

-Prototype: xchat_hook *xchat_hook_server(xchat_plugin *ph, const char *name, int pri, xchat_serv_cb *callb, void *userdata); -
-
Description: Registers a function to be called when a certain server event occurs. You can -use this to trap PRIVMSG, NOTICE, PART, a server numeric etc... If you want to -hook every line that comes from the IRC server, you may use the special name of "RAW LINE". -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
name: Name of the server event. -
pri: Priority of this command. Use XCHAT_PRI_NORM. -
callb: Callback function. This will be called when this event is received from the server. -
userdata: Pointer passed to the callback function.

-Returns: Pointer to the hook. Can be passed to xchat_unhook. -
-
Example: -

-static int kick_cb(char *word[], char *word_eol[], void *userdata)
-{
-	xchat_printf(ph, "%s was kicked from %s (reason=%s)\n", word[4], word[3], word_eol[5]);
-	return XCHAT_EAT_NONE;	/* don't eat this event, let other plugins and HexChat see it too */
-}
-
-xchat_hook_server(ph, "KICK", XCHAT_PRI_NORM, kick_cb, NULL);
-

-
- -

xchat_hook_timer()

-Prototype: xchat_hook *xchat_hook_timer(xchat_plugin *ph, int timeout, xchat_timer_cb *callb, void *userdata); -
-
Description: Registers a function to be called every "timeout" milliseconds. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
timeout: Timeout in milliseconds (1000 is 1 second). -
callb: Callback function. This will be called every "timeout" milliseconds. -
userdata: Pointer passed to the callback function.

-Returns: Pointer to the hook. Can be passed to xchat_unhook. -
-
Example: -

-static xchat_hook *myhook;
-
-static int stop_cb(char *word[], char *word_eol[], void *userdata)
-{
-	if(myhook != NULL)
-	{
-		xchat_unhook(ph, myhook);
-		myhook = NULL;
-		xchat_print(ph, "Timeout removed!\n");
-	}
-
-	return XCHAT_EAT_ALL;
-}
-
-static int timeout_cb(void *userdata)
-{
-	xchat_print(ph, "Annoying message every 5 seconds! Type /STOP to stop it.\n");
-	return 1;	/* return 1 to keep the timeout going */
-}
-
-myhook = xchat_hook_timer(ph, 5000, timeout_cb, NULL);
-xchat_hook_command(ph, "STOP", XCHAT_PRI_NORM, stop_cb, NULL, NULL);
-

- -

xchat_unhook()

-Prototype: void *xchat_unhook(xchat_plugin *ph, xchat_hook *hook); -
-
Description: Unhooks any hook registered with xchat_hook_print/server/timer/command. When plugins are unloaded, all of its hooks are automatically -removed, so you don't need to call this within your xchat_plugin_deinit() function. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
hook: Pointer to the hook, as returned by xchat_hook_*. -

-Returns: The userdata you originally gave to xchat_hook_*. -

- -

xchat_command()

-Prototype: void xchat_command(xchat_plugin *ph, const char *command); -
-
Description: Executes a command as if it were typed in HexChat's input box. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
command: Command to execute, without the forward slash "/". -

-

- -

xchat_commandf()

-Prototype: void xchat_commandf(xchat_plugin *ph, const char *format, ...); -
-
Description: Executes a command as if it were typed in HexChat's input box and provides string formating like printf. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
format: The format string. -

-

- -

xchat_print()

-Prototype: void xchat_print(xchat_plugin *ph, const char *text); -
-
Description: Prints some text to the current tab/window. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
text: Text to print. May contain mIRC color codes. -

-

- -

xchat_printf()

-Prototype: void xchat_printf(xchat_plugin *ph, const char *format, ...); -
-
Description: Prints some text to the current tab/window and provides formating like printf. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
format: The format string. -

-

- -

xchat_emit_print()

-Prototype: int xchat_emit_print(xchat_plugin *ph, const char *event_name, ...); -
-
Description: Generates a print event. This can be any -event found in the Preferences > Advanced > Text Events window. The vararg parameter list -MUST always be NULL terminated. Special care should be taken when calling this function -inside a print callback (from xchat_hook_print), as not to cause endless recursion. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
event_name: Text event to print. -

-

-Returns: 1-Success 0-Failure. -

-Example: -

-xchat_emit_print(ph, "Channel Message", "John", "Hi there", "@", NULL);
-

-

- -

xchat_send_modes() (new for 2.0.9)

-Prototype: void xchat_send_modes (xchat_plugin *ph, const char *targets[], int ntargets, int modes_per_line, char sign, char mode) -
-
Description: Sends a number of channel mode changes to the current channel. For example, you can Op a whole -group of people in one go. It may send multiple MODE lines if the request doesn't fit on one. Pass 0 for -modes_per_line to use the current server's maximum possible. This function should only be called while -in a channel context. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
targets: Array of targets (strings). The names of people whom the action will be performed on. -
ntargets: Number of elements in the array given. -
modes_per_line: Maximum modes to send per line. -
sign: Mode sign, '-' or '+'. -
mode: Mode char, e.g. 'o' for Ops.
-

-Example: (Ops the three names given) -

-const char *names_to_Op[] = {"John", "Jack", "Jill"};
-xchat_send_modes(ph, names_to_Op, 3, 0, '+', 'o');
-

-

- -

xchat_find_context()

-Prototype: xchat_context *xchat_find_context(xchat_plugin *ph, const char *servname, const char *channel); -
-
Description: Finds a context based on a channel and servername. If servname is NULL, it finds any channel (or query) by the given name. If channel is NULL, it finds the front-most tab/window of the given servname. If NULL is given for both arguments, the currently focused tab/window will be returned.
-Changed in 2.6.1. If servname is NULL, it finds the channel (or query) by the given name in the same server group as the current context. If that doesn't exists then find any by the given name. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
servname: Servername or NULL. -
channel: Channelname or NULL. -
-

-Returns: Context pointer (for use with xchat_set_context) or NULL. -

- -

xchat_get_context()

-Prototype: xchat_context *xchat_get_context(xchat_plugin *ph); -
-
Description: Returns the current context for your plugin. You can use this later with xchat_set_context. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
-

-Returns: Context pointer (for use with xchat_set_context). -

- -

xchat_get_info()

-Prototype: const char *xchat_get_info(xchat_plugin *ph, const char *id); -
-
Description: Returns information based on your current context. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
id: ID of the information you want. Currently supported IDs are (case sensitive): -
- - - - - - - - - - - - - - - - - - - - -
away away reason or NULL if you are not away.
channel current channel name.
charset character-set used in the current context (since 2.4.2).
event_text <name> text event format string for name (since 2.8.2).
gtkwin_ptr (GtkWindow *) (since 2.8.9).
host real hostname of the server you connected to.
inputbox the input-box contents, what the user has typed (since 2.4.1).
libdirfs library directory. e.g. /usr/lib/xchat. The same directory used for auto-loading plugins (since 2.4.0).This string isn't necessarily UTF-8, but local file system encoding.
modes channel modes, if known, or NULL (since 2.8.1).
network current network name or NULL.
nick your current nick name.
nickserv nickserv password for this network or NULL (since 2.4.3).
server current server name (what the server claims to be). NULL if you are not connected.
topic current channel topic.
version xchat version number.
win_ptr native window pointer. Unix: (GtkWindow *) Win32: HWND (since 2.6.0).
win_status window status: "active", "hidden" or "normal" (since 2.0.9).
xchatdir xchat config directory, e.g.: /home/user/.xchat2 This string is encoded in UTF-8, which means you _should_ convert it to "locale" encoding before using functions like open() or OpenFile(). For best Unicode support on Linux, convert this string using g_filename_from_utf8 and on Windows convert this string to UTF-16LE (wide) and use OpenFileW() etc.
xchatdirfs xchat config directory, e.g.: /home/user/.xchat2 (since 2.0.9).This string is encoded in local file system encoding, making it ideal for direct use with functions like open() or OpenFile(). For real Unicode support on Windows, it's best not to use HexChatdirfs, but HexChatdir instead.
-
-

-Returns: A string of the requested information, or NULL. This string must -not be freed and must be copied if needed after the call to xchat_get_info. -

- -

xchat_get_prefs()

-Prototype: int xchat_get_prefs(xchat_plugin *ph, const char *name, const char **string, int *integer); -
-
Description: Provides xchat's setting information (that which is available through the /set command). -A few extra bits of information are available that don't appear in the /set list, currently they are: -
-

- - - -
state_cursor Current input-box cursor position (characters, not bytes). Since 2.4.2.
id Unique server id. Since 2.6.1.
-

-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
name: Setting name required. -
string: Pointer-pointer which to set. -
integer: Pointer to an integer to set, if setting is a Boolean or Integer type. -

-Returns: 0-Failed 1-Returned a string 2-Returned an Integer 3-Returned a Boolean. -

Example: -

-{
-	int i;
-	const char *str;
-
-	if (xchat_get_prefs (ph, "irc_nick1", &str, &i) == 1)
-	{
-		xchat_printf (ph, "Current nickname setting: %s\n", str);
-	}
-}

-

- - -

xchat_set_context()

-Prototype: int xchat_set_context(xchat_plugin *ph, xchat_context *ctx); -
-
Description: Changes your current context to the one given. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
ctx: Context to change to (obtained with xchat_get_context or xchat_find_context). -
-

-Returns: 1 for success, 0 for failure. -

- -

xchat_nickcmp()

-Prototype: int xchat_nickcmp(xchat_plugin *ph, const char *s1, const char *s2); -
-
Description: Performs a nick name comparision, based on the current server connection. This might be a RFC1459 compliant string compare, or -plain ascii (in the case of DALNet). Use this to compare channels and nicknames. The function works the same way as strcasecmp. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
s1: String to compare. -
s2: String to compare s1 to. -
-

-Quote from RFC1459: -

- Because of IRC's scandanavian origin, the characters {}| are - considered to be the lower case equivalents of the characters []\, - respectively. This is a critical issue when determining the - equivalence of two nicknames. -

-Returns: - An integer - less than, equal to, or greater than zero if s1 is found, - respectively, to be less than, to match, or be greater than s2. -

- -

xchat_strip() (new for 2.4.2)

-Prototype: char *xchat_strip(xchat_plugin *ph, const char *str, int len, int flags); -
-
Description: Strips mIRC color codes and/or text attributes (bold, underlined etc) from the given string and returns a newly allocated string. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
str: String to strip. -
len: Length of the string (or -1 for NULL terminated). -
flags: Bit-field of flags: 0-Strip mIRC colors, 1-Strip text attributes. -
-

-Returns: -A newly allocated string or NULL for failure. You must free this string with xchat_free. -

Example: -

-{
-	char *new_text;
-
-	/* strip both colors and attributes by using the 0 and 1 bits (1 BITWISE-OR 2) */
-	new_text = xchat_strip(ph, "\00312Blue\003 \002Bold!\002", -1, 1 | 2);
-
-	if(new_text)
-	{
-		/* new_text should now contain only "Blue Bold!" */
-		xchat_printf(ph, "%s\n", new_text);
-		xchat_free(ph, new_text);
-	}
-}

- -

- -

xchat_free() (new for 2.4.2)

-Prototype: void xchat_free(xchat_plugin *ph, void *ptr); -
-
Description: Frees a string returned by xchat_* functions. Currently only used to free strings from xchat_strip. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
ptr: Pointer to free. -
-

- -

- -

xchat_pluginpref_set_str() (new for 2.9.0)

-Prototype: int xchat_pluginpref_set_str (xchat_plugin *ph, const char *var, const char *value); -
-
Description: Saves a plugin-specific setting with string value to a plugin-specific config file. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
var: Name of the setting to save. -
value: String value of the the setting. -
-

-Returns: 1 for success, 0 for failure. -

Example: -

int xchat_plugin_init (xchat_plugin *plugin_handle,
-			char **plugin_name,
-			char **plugin_desc,
-			char **plugin_version,
-			char *arg)
-{
-	ph = plugin_handle;
-	*plugin_name = "Tester Thingie";
-	*plugin_desc = "Testing stuff";
-	*plugin_version = "1.0";
-
-	xchat_pluginpref_set_str (ph, "myvar1", "I want to save this string!");
-	xchat_pluginpref_set_str (ph, "myvar2", "This is important, too.");
-
-	return 1;       /* return 1 for success */
-}

-In the example above, the settings will be saved to the plugin_tester_thingie.conf file, and its content will be: -

myvar1 = I want to save this string!
-myvar2 = This is important, too.

-You should never need to edit this file manually. -

- -

xchat_pluginpref_get_str() (new for 2.9.0)

-Prototype: int xchat_pluginpref_get_str (xchat_plugin *ph, const char *var, char *dest); -
-
Description: Loads a plugin-specific setting with string value from a plugin-specific config file. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
var: Name of the setting to load. -
dest: Array to save the loaded setting's string value to. -
-

-Returns: 1 for success, 0 for failure. -

- -

xchat_pluginpref_set_int() (new for 2.9.0)

-Prototype: int xchat_pluginpref_set_int (xchat_plugin *ph, const char *var, int value); -
-
Description: Saves a plugin-specific setting with decimal value to a plugin-specific config file. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
var: Name of the setting to save. -
value: Decimal value of the the setting. -
-

-Returns: 1 for success, 0 for failure. -

Example: -

static int saveint_cb (char *word[], char *word_eol[], void *user_data)
-{
-	int buffer = atoi (word[2]);
-
-	if (buffer > 0 && buffer < INT_MAX)
-	{
-		if (xchat_pluginpref_set_int (ph, "myint1", buffer))
-		{
-			xchat_printf (ph, "Setting successfully saved!\n");
-		}
-		else
-		{
-			xchat_printf (ph, "Error while saving!\n");
-		}
-	}
-	else
-	{
-		xchat_printf (ph, "Invalid input!\n");
-	}
-
-	return XCHAT_EAT_XCHAT;
-}

-You only need these kind of complex checks if you're saving user input, which can be non-numeric. -

- -

xchat_pluginpref_get_int() (new for 2.9.0)

-Prototype: int xchat_pluginpref_get_int (xchat_plugin *ph, const char *var); -
-
Description: Loads a plugin-specific setting with decimal value from a plugin-specific config file. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
var: Name of the setting to load. -
-

-Returns: The decimal value of the requested setting upon success, -1 for failure. -

- -

xchat_pluginpref_delete() (new for 2.9.0)

-Prototype: int xchat_pluginpref_delete (xchat_plugin *ph, const char *var); -
-
Description: Deletes a plugin-specific setting from a plugin-specific config file. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
var: Name of the setting to delete. -
-

-Returns: 1 for success, 0 for failure. If the given setting didn't exist, it also returns 1, so 1 only indicates that the setting won't exist after the call. -

- -

xchat_pluginpref_list() (new for 2.9.0)

-Prototype: int xchat_pluginpref_list (xchat_plugin *ph, char *dest); -
-
Description: Builds a comma-separated list of the currently saved settings from a plugin-specific config file. -
-
Arguments: -

ph: Plugin handle (as given to xchat_plugin_init). -
dest: Array to save the list to. -
-

-Returns: 1 for success, 0 for failure (nonexistent, empty or inaccessible config file). -

- - - diff --git a/plugins/python/hexchat-python.md b/plugins/python/hexchat-python.md deleted file mode 100644 index bc4c6cdc..00000000 --- a/plugins/python/hexchat-python.md +++ /dev/null @@ -1,545 +0,0 @@ -% HexChat Python Interface - -Features --------- - -Here are some of the features of the python plugin interface: - -- Comprehensive, consistent and straightforward API -- Load, unload, reload, and autoload support -- Per plugin independent interpreter state -- Python interactive console -- Python interactive command execution -- Full thread support -- Stdout and stderr redirected to xchat console -- Dynamic list management -- Nice context treatment -- Plugin preferences - -Commands --------- - -The following commands will be intercepted by the Python Plugin interface module, when it is loaded. - ---------------------------------------------------------------------------------------------------------------------------------------------- -*Command* *Description* ----------------------------------- --------------------------------------------------------------------------------------------------------- -/py load Load module with given filename. - -/py unload Unload module with given filename, or module name. - -/py reload Reload module with given filename, or module name. - -/py list List Python modules loaded. - -/py exec Execute given Python command interactively. For example: - `/py exec import xchat` - `/py exec print xchat.get_info('channel')` - -/py console Open the Python interactive console in a query (>>python<<). - Every message sent will be intercepted by the Python plugin interface, and interpreted interactively. - Notice that the console and /py exec commands live in the same interpreter state. - -/py about Show some information about the Python plugin interface. ----------------------------------------------------------------------------------------------------------------------------------------------- - - -Autoloading modules -------------------- - -If you want some module to be autoloaded together with the Python plugin -interface (which usually loads at startup time), just make sure it has a -`.py` extension and put it in your HexChat directory (~/.config/hexchat/addons, %APPDATA%\\HexChat\\addons). - -Context theory --------------- - -Before starting to explain what the API offers, I'll do a short -introduction about the xchat context concept. Not because it's something -hard to understand, but because you'll understand better the API -explanations if you know what I'm talking about. - -You can think about a context as an xchat channel, server, or query tab. -Each of these tabs, has its own context, and is related to a given -server and channel (queries are a special kind of channel). - -The *current* context is the one where xchat passes control to the -module. For example, when xchat receives a command in a specific -channel, and you have asked xchat to tell you about this event, the -current context will be set to this channel before your module is -called. - -Hello world ------------ - -Here is the traditional *hello world* example. - -~~~~~~~~~~ {.python} - __module_name__ = "helloworld" - __module_version__ = "1.0" - __module_description__ = "Python module example" - - print "Hello world!" -~~~~~~~~~~ - -This module will print "Hello world!" in the xchat console, and sleep -forever until it's unloaded. It's a simple module, but already -introduces some concepts. Notice how the module information is set. This -information is obligatory, and will be shown when listing the loaded -xchat modules. - -xchat module ------------- - -The xchat module is your passport to every xchat functionality offered -by the Python plugin interface. Here's a simple example: - -~~~~~~~~~~ {.python} - import xchat - xchat.prnt("Hi everyone!") -~~~~~~~~~~ - -The following functions are available in the xchat module. - -### Generic functions - -#### xchat.prnt(string) - -This function will print string in the current context. It's mainly -useful as a parameter to pass to some other function, since the usual -print statement will have the same results. You have a usage example -above. - -This function is badly -named because `"print"` is a reserved keyword of the Python language. - -#### xchat.emit_print(event_name, *args) - -This function will generate a *print event* with the given arguments. To -check which events are available, and the number and meaning of -arguments, have a look at the `Settings > Lists > Text Events` window. -Here is one example: - -~~~~~~~~~~ {.python} - xchat.emit_print("Channel Message", "John", "Hi there", "@") -~~~~~~~~~~` - -#### xchat.command(string) - -Execute the given command in the current context. This has the same -results as executing a command in the xchat window, but notice that the -`/` prefix is not used. Here is an example: - -~~~~~~~~~~ {.python} - xchat.command("server irc.openprojects.net") -~~~~~~~~~~ - -#### xchat.nickcmp(s1, s2) - -This function will do an RFC1459 compliant string comparing between `s1` -and `s2`, and is useful to compare channels and nicknames. It returns an -integer less than, equal to, or greater than zero if `s1` is found, -respectively, to be less than, to match, or be greater than `s2`. For -example: - -~~~~~~~~~~ {.python} - if xchat.nickcmp(nick, "mynick") == 0: - print "They are the same!" -~~~~~~~~~~ - -### Information retreiving functions - -#### xchat.get_info(type) - -Retrieve the information specified by the `type` string in the current -context. At the moment of this writing, the following information types -are available to be queried: - ------------------------------------------------------------------------------------------------ -*Type* *Description* --------- ----------------------------------------------------------------------------------- -away Away reason or None if you are not away. - -channels Channel of the current context. - -hostname Real hostname of the server you connected to. - -network Current network name or None. - -nick Your current nick name. - -server Current server name (what the server claims to be) or None if you are not connected. - -topic Current channel topic. - -version hexchat version number. - -xchatdir hexchat config directory e.g.: "~/.config/hexchat". ------------------------------------------------------------------------------------------------- - -Example: - -~~~~~~~~~~ {.python} - if xchat.get_info("server") is None: - xchat.prnt("Not connected!") -~~~~~~~~~~ - -#### xchat.get_prefs(name) - -Retrieve the xchat setting information specified by the `name` string, -as available by the `/set` command. For example: - -~~~~~~~~~~ {.python} - print "Current preferred nick:", xchat.get_prefs("irc_nick1") -~~~~~~~~~~ - -#### xchat.get_list(type) - -With this function you may retrieve a list containing the selected -information from the current context, like a DCC list, a channel list, a -user list, etc. Each list item will have its attributes set dynamically -depending on the information provided by the list type. - -The example below is a rewrite of the example provided with xchat's -plugin API documentation. It prints a list of every DCC transfer -happening at the moment. Notice how similar the interface is to the C -API provided by xchat. - -~~~~~~~~~~ {.python} - list = xchat.get_list("dcc") - if list: - print "--- DCC LIST ------------------" - print "File To/From KB/s Position" - for i in list: - print "%6s %10s %.2f %d" % (i.file, i.nick, i.cps/1024, i.pos) -~~~~~~~~~~ - -Below you will find what each list type has to offer. - -This information was -taken from xchat's plugin documentation. You may find any types not -listed here, if they exist at all, in an updated xchat documentation. -Any list types accepted by xchat should be dynamically accepted by the -Python plugin interface. - -##### channels - -The channels list type gives you access to the channels, queries and -their servers. The folloing attributes are available in each list item: - -------------------------------------------------------------------- -*Type* *Description* -------- ------------------------------------------------------- -channel Channel or query name. - -context A context object, giving access to that channel/server. - -network Network name to which this channel belongs. - -server Server name to which this channel belongs. - -type Type of context (1=Server, 2=Channel, 3=Dialog). -------------------------------------------------------------------- - -##### dcc - -The dcc list type gives you access to a list of DCC file transfers. The -following attributes are available in each list item: - ---------------------------------------------------------------------------------------- -*Type* *Description* ---------- --------------------------------------------------------------------------- -address32 Address of the remote user (ipv4 address, as an int). - -cps Bytes per second (speed). - -destfile Destination full pathname. - -file Filename. - -nick Nickname of person who the file is from/to. - -port TCP port number. - -pos Bytes sent/received. - -resume Point at which this file was resumed (or zero if it was not resumed). - -size File size in bytes. - -status DCC status (queued=0, active=1, failed=2, done=3, connecting=4, aborted=5). - -type DCC type (send=0, receive=1, chatrecv=2, chatsend=3). ---------------------------------------------------------------------------------------- - -##### users - -The users list type gives you access to a list of users in the current -channel. The following attributes are available in each list item: - ----------------------------------------------------------------- -*Type* *Description* ------- -------------------------------------------------------- -nick Nick name. - -host Host name in the form user@host (or None, if not known). - -prefix Prefix character, .e.g: @ or +. Points to a single char. ----------------------------------------------------------------- - -##### ignore - -The ignore list type gives you access to the current ignored list. The -following attributes are available in each list item: - ------------------------------------------------------------------------------------------------------------ -*Type* *Description* ------ --------------------------------------------------------------------------------------------------- -mask Ignore mask (for example, "*!*@*.aol.com"). - -flags Bit field of flags (0=private, 1=notice, 2=channel, 3=ctcp, 4=invite, 5=unignore, 6=nosave, 7=dcc). ------------------------------------------------------------------------------------------------------------ - -### Hook functions - -These functions allow one to hook into xchat events. - -#### Priorities - -When a priority keyword parameter is accepted, it means that this -callback may be hooked with five different priorities: PRI_HIGHEST, -PRI_HIGH, PRI_NORM, PRI_LOW, and PRI_LOWEST. The usage of these -constants, which are available in the xchat module, will define the -order in which your plugin will be called. Most of the time, you won't -want to change its default value (PRI_NORM). - -#### Parameters word and word_eol - -These parameters, when available in a callback, are lists of strings -which contain the parameters the user entered for the particular -command. For example, if you executed: - -> /command NICK Hi there! - -- **word[0]** is `command` -- **word[1]** is `NICK` -- **word[2]** is `Hi` -- **word[3]** is `there!` -- **word_eol[0]** is `command NICK Hi there!` -- **word_eol[1]** is `NICK Hi there!` -- **word_eol[2]** is `Hi there!` -- **word_eol[3]** is `there!` - -#### Parameter userdata - -The parameter userdata, if given, allows you to pass a custom object to -your callback. - -#### Callback return constants (EAT_*) - -When a callback is supposed to return one of the EAT_* macros, it is -able control how xchat will proceed after the callback returns. These -are the available constants, and their meanings: - ---------------------------------------------------------- -*Constant* *Description* ------------ --------------------------------------------- -EAT_PLUGIN Don't let any other plugin receive this event. - -EAT_XCHAT Don't let xchat treat this event as usual. - -EAT_ALL Eat the event completely. - -EAT_NONE Let everything happen as usual. ---------------------------------------------------------- - -Returning `None` is the same as returning `EAT_NONE`. - -#### xchat.hook_command(name, callback, userdata=None, priority=PRI_NORM, help=None) - -This function allows you to hook into the name xchat command. It means -that everytime you type `/name ...`, `callback` will be called. -Parameters `userdata` and `priority` have their meanings explained -above, and the parameter help, if given, allows you to pass a help text -which will be shown when `/help name` is executed. This function returns -a hook handler which may be used in the `xchat.unhook()` function. For -example: - -~~~~~~~~~~ {.python} - def onotice_cb(word, word_eol, userdata): - if len(word) < 2: - print "Second arg must be the message!" - else: - xchat.command("NOTICE @%s %s" % (xchat.get_info("channel"), word_eol[1])) - return xchat.EAT_ALL - - xchat.hook_command("ONOTICE", onotice_cb, help="/ONOTICE Sends a notice to all ops") -~~~~~~~~~~ - -You may return one of `EAT_*` constants in the callback, to control -xchat's behavior, as explained above. - -#### xchat.hook_print(name, callback, userdata=None, priority=PRI_NORM) - -This function allows you to register a callback to trap any print -events. The event names are available in the *Edit Event Texts* window. -Parameters `userdata` and `priority` have their meanings explained -above. This function returns a hook handler which may be used in the -`xchat.unhook()` function. For example: - -~~~~~~~~~~ {.python} - def youpart_cb(word, word_eol, userdata): - print "You have left channel", word[2] - return xchat.EAT_XCHAT # Don't let xchat do its normal printing - - xchat.hook_print("You Part", youpart_cb) -~~~~~~~~~~ - -You may return one of `EAT_*` constants in the callback, to control -xchat's behavior, as explained above. - -#### xchat.hook_server(name, callback, userdata=None, priority=PRI_NORM) - -This function allows you to register a callback to be called when a -certain server event occurs. You can use this to trap `PRIVMSG`, -`NOTICE`, `PART`, a server numeric, etc. Parameters `userdata` and -`priority` have their meanings explained above. This function returns a -hook handler which may be used in the `xchat.unhook()` function. For -example: - -~~~~~~~~~~ {.python} - def kick_cb(word, word_eol, userdata): - print "%s was kicked from %s (%s)" % (word[3], word[2], word_eol[4]) - # Don't eat this event, let other plugins and xchat see it too - return xchat.EAT_NONE - - xchat.hook_server("KICK", kick_cb) -~~~~~~~~~~ - -You may return one of `EAT_*` constants in the callback, to control -xchat's behavior, as explained above. - -#### xchat.hook_timer(timeout, callback, userdata=None) - -This function allows you to register a callback to be called every -timeout milliseconds. Parameters userdata and priority have their -meanings explained above. This function returns a hook handler which may -be used in the `xchat.unhook()` function. For example: - -~~~~~~~~~~ {.python} - myhook = None - - def stop_cb(word, word_eol, userdata): - global myhook - if myhook is not None: - xchat.unhook(myhook) - myhook = None - print "Timeout removed!" - - def timeout_cb(userdata): - print "Annoying message every 5 seconds! Type /STOP to stop it." - return 1 # Keep the timeout going - - myhook = xchat.hook_timer(5000, timeout_cb) - xchat.hook_command("STOP", stop_cb) -~~~~~~~~~~ - -If you return a true value from the callback, the timer will be keeped, -otherwise it is removed. - -#### xchat.hook_unload(timeout, callback, userdata=None) - -This function allows you to register a callback to be called when the -plugin is going to be unloaded. Parameters `userdata` and `priority` -have their meanings explained above. This function returns a hook -handler which may be used in the `xchat.unhook()` function. For example: - -~~~~~~~~~~ {.python} - def unload_cb(userdata): - print "We're being unloaded!" - - xchat.hook_unload(unload_cb) -~~~~~~~~~~ - -#### xchat.unhook(handler) - -Unhooks any hook registered with the hook functions above. - -### Plugin preferences - -You can use pluginpref to easily store and retrieve settings. This was added in the Python plugin version 0.9 - -#### xchat.set_pluginpref(name, value) - -If neccessary creates a .conf file in the HexChat config dir named addon_python.conf and stores the value in it. Returns 1 on success 0 on failure. - -> Note: Until the plugin uses different a conf file per script it's recommened to use 'PluginName-SettingName' to avoid conflicts. - -#### xchat.get_pluginpref(name) - -This will return the value of the variable of that name. If there is none by this name it will return `None`. Numbers are always returned as Integers. - -#### xchat.del_pluginpref(name) - -Deletes specified variable. Returns 1 on success (or never existing), 0 on failure. - -#### xchat.list_pluginpref() - -Returns a list of all currently set preferences. - -### Context handling - -Below you will find information about how to work with contexts. - -#### Context objects - -As explained in the Context theory session above, contexts give access -to a specific channel/query/server tab of xchat. Every function -available in the xchat module will be evaluated in the current context, -which will be specified by xchat itself before passing control to the -module. Sometimes you may want to work in a specific context, and that's -where context objects come into play. - -You may create a context object using the `xchat.get_context()` or -`xchat.find_context()`, functions as explained below, or trough the -`xchat.get_list()` function, as explained in its respective session. - -Each context object offers the following methods: - -------------------------------------------------------------------------------------------------------------------------- -*Methods* *Description* ----------------------------------------- ----------------------------------------------------------------------------- -context.set() Changes the current context to be the one represented by this context object. - -context.prnt(string) Does the same as the xchat.prnt() function, but in the given context. - -context.emit_print(event_name, *args) Does the same as the emit_print() function, but in the given context. - -context.command(string) Does the same as the xchat.command() function, but in the given context. - -context.get_info(type) Does the same as the xchat.get_info() function, but in the given context. - -context.get_list(type) Does the same as the xchat.get_list() function, but in the given context. -------------------------------------------------------------------------------------------------------------------------- - -#### xchat.get_context() - -Returns a context object corresponding the the current context. - -#### xchat.find_context(server=None, channel=None) - -Finds a context based on a channel and servername. If `server` is -`None`, it finds any channel (or query) by the given name. If `channel` -is `None`, it finds the front-most tab/window of the given server. For -example: - -~~~~~~~~~~ {.python} - cnc = xchat.find_context(channel='#conectiva') - cnc.command('whois niemeyer') -~~~~~~~~~~ - -* * * * * - -Original Author: Gustavo Niemeyer [gustavo@niemeyer.net](mailto:gustavo@niemeyer.net) - -For purty html: `pandoc --toc python.md -s --highlight-style haddock -o python.html` diff --git a/plugins/tcl/README b/plugins/tcl/README deleted file mode 100644 index e46635ef..00000000 --- a/plugins/tcl/README +++ /dev/null @@ -1,55 +0,0 @@ -Please read this document before asking questions. - -(1) WHAT IS THE TCL PLUGIN? - - The XChat Tcl Plugin adds the complete Tcl scripting language to the - XChat 1.9.x and 2.x IRC client. The design philosophy behind the tcl - plugin was to give all the power of the C API. yet completely shield - the user from all the complexities of it. It is lightly modeled after - after Xircon; an old windows TCL enabled client with a little bit of - eggdrop functionality to it. - - Features: - * Uses the popular TCL scripting language. - * Familiar to eggdrop bot owners. - * Adds many new XChat specific commands to the Tcl language for - handling of events, user commands, timers, etc. - * It's actually documented! (Hey, what a concept!) - * Works with XChat 1.9.x and 2.x. - * Open source (GPL) - - The supplied documentation for Tcl Plugin commands can be - found in doc/tclplugin.html - - For a comprehensive list of IRC server tokens, see - doc/tokens.txt - - -(2) HOW TO GET TCL PLUGIN - - You can always find the latest version of the Tcl Plugin at: - - http://www.scriptkitties.com/tclplugin - - You must also have Tcl 8.3 or higher installed on your system. - - Tcl can be obtained from: - - http://sourceforge.net/projects/tcl - http://tcl.activestate.com (pre-compiled binaries) - - Tcl Man Pages - - http://tcl.activestate.com/man/ - - Tcl Tutorials: - - http://hegel.ittc.ukans.edu/topics/tcltk/tutorial-noplugin/ - http://jan.netcomp.monash.edu.au/ProgrammingUnix/tcl/tcl_tut.html - http://users.belgacom.net/bruno.champagne/tcl.html - - -(3) QUICK STARTUP - - SEE 'INSTALL' - -- cgit 1.4.1

Name	Description	Type
address32	Address of the remote user (ipv4 address)	int
cps	Bytes per second (speed)	int
destfile	Destination full pathname	string
file	File name	string
nick	Nickname of person who the file is from/to	string
port	TCP port number	int
pos	Bytes sent/received	int
poshigh	Bytes sent/received, high order 32 bits	int
resume	Point at which this file was resumed (or zero if it was not resumed)	int
resumehigh	Point at which this file was resumed, high order 32 bits	int
size	File size in bytes, low order 32 bits (cast it to unsigned)	int
sizehigh	File size in bytes, high order 32 bits	int
status	DCC Status: 0-Queued 1-Active 2-Failed 3-Done 4-Connecting 5-Aborted	int
type	DCC Type: 0-Send 1-Receive 2-ChatRecv 3-ChatSend	int

GUI ATTACH	Same function as "Attach Window" in the HexChat menu (new for 2.6.2).
GUI DETACH	Same function as "Detach Tab" in the HexChat menu (new for 2.6.2).
GUI APPLY	Similar to clicking OK in the settings window. Execute this after /SET to activate GUI changes (new for 2.8.0)
GUI COLOR n	Change the tab color of the current context, where n is a number from 0 to 3.
GUI FOCUS	Focus the current window or tab.
GUI FLASH	Flash the taskbar button. It will flash only if the window isn't focused and will stop when it is focused by the user.
GUI HIDE	Hide the main HexChat window completely (this is used by the Systray plugin).
GUI ICONIFY	Iconify (minimize to taskbar) the current HexChat window.
GUI MSGBOX text	Displays a asynchronous message box with your text (new for 2.4.5).
GUI SHOW	Show the main HexChat window (if currently hidden).

-eX	Set enable flag to X. -e0 for disable, -e1 for enable. This lets you create a disabled (shaded) item.
-iFILE	Use an icon filename FILE (new for 2.8.0). Not supported for toggles or radio items.
-k<mod>,<key>	Specify a keyboard shortcut. "mod" is the modifier which is a bitwise OR of: 1-SHIFT 4-CTRL 8-ALT in decimal. "key" is the key value in decimal, e.g. -k5,101 would specify SHIFT-CTRL-E.
-m	Specify that this label should be treated as Pango Markup language. Since forward slash ("/") is already used in menu paths, you should replace closing tags with an ASCII 003 instead e.g.: xchat_command(ph, "MENU -m ADD \"<b>Bold Menu<\003b>\""); (new for 2.6.6).
-pX	Specify a menu item's position number. e.g. -p5 will cause the item to be inserted in the 5th place. New for 2.8.0: If the position is a negative number, it will be used as an offset from the bottom/right-most item.
-rX,group	Specify a radio menu item, with initial state X and a group name (new for 2.8.0). The group name should be the exact label of another menu item (without the path) that this item will be grouped with. For radio items, only a select command will be executed (no unselect command).
-tX	Specify a toggle menu item with an initial state. -t0 for an "unticked" item and -t1 for a "ticked" item.

Root Name	Menu
$TAB	Tab menu (right click a channel/query tab or treeview row)
$TRAY	System Tray menu
$URL	URL link menu
$NICK	Userlist nick-name popup menu
$CHAN	Menu when clicking a channel in the text area (since 2.8.4)

away	away reason or NULL if you are not away.
channel	current channel name.
charset	character-set used in the current context (since 2.4.2).
event_text <name>	text event format string for name (since 2.8.2).
gtkwin_ptr	(GtkWindow *) (since 2.8.9).
host	real hostname of the server you connected to.
inputbox	the input-box contents, what the user has typed (since 2.4.1).
libdirfs	library directory. e.g. /usr/lib/xchat. The same directory used for auto-loading plugins (since 2.4.0).This string isn't necessarily UTF-8, but local file system encoding.
modes	channel modes, if known, or NULL (since 2.8.1).
network	current network name or NULL.
nick	your current nick name.
nickserv	nickserv password for this network or NULL (since 2.4.3).
server	current server name (what the server claims to be). NULL if you are not connected.
topic	current channel topic.
version	xchat version number.
win_ptr	native window pointer. Unix: (GtkWindow *) Win32: HWND (since 2.6.0).
win_status	window status: "active", "hidden" or "normal" (since 2.0.9).
xchatdir	xchat config directory, e.g.: /home/user/.xchat2 This string is encoded in UTF-8, which means you _should_ convert it to "locale" encoding before using functions like open() or OpenFile(). For best Unicode support on Linux, convert this string using g_filename_from_utf8 and on Windows convert this string to UTF-16LE (wide) and use OpenFileW() etc.
xchatdirfs	xchat config directory, e.g.: /home/user/.xchat2 (since 2.0.9).This string is encoded in local file system encoding, making it ideal for direct use with functions like open() or OpenFile(). For real Unicode support on Windows, it's best not to use HexChatdirfs, but HexChatdir instead.

state_cursor	Current input-box cursor position (characters, not bytes). Since 2.4.2.
id	Unique server id. Since 2.6.1.