|
|
Perl SnippetsOn this page, a bunch of small XChat Perl scripts are provided. Each of these deal with a specific purpose and so shouldn't be lumped all together in one script. Most of these scripts will have been provided in #xchat to answer some user, but provided here in case someone else has a need for them. Simply create a plain text file inside of your XChat profile directory named something.pl, replacing "something" with a word of your choice. Most of these scripts won't include a registration line, so meaningful information will not show up in Window -> Plugins and Scripts.... To have the script registered in that window, start the file out with the following line (changed for each snippet you save as a separate file): Xchat::register('One Line Snippets', '001', 'Miscellaneous small perl snippets for specific tasks'); In the above, One Line Snippets would be the name of the script, and only one XChat script can be named this. XChat will complain at you if you try and load multiple files with this as the script name. 001 is the version number of the script, and can be almost anything you like. The last bit is the Description that will be displayed in the Plugins and Scripts dialog.
Away Action ignoreIf you would like to ignore all channel actions that start with "* user is auto-away", "* user is back", "* user is auto back" and similar, you can use the following one line Perl script to accomplish that: Xchat::hook_print('Channel Action', sub { return Xchat::EAT_ALL if ($_[0][1] =~ /^is (?:auto[ -])?(?:away|back)/i); return Xchat::EAT_NONE; }); Reply nick colorsThe following script was written for a user on #xchat who wanted to distinguish replies addressed at specific users from generic chat messages in the case of large support channels. To do that, we have the following script which will bold and color green a nick if it starts the line in the form of "nickname:" or "nickname,". Xchat::register('Distinguish Reply', '001', 'Place colors around a user if they are being addressed'); Xchat::hook_print('Channel Message', sub { $_[0][1] =~ m/^(\S+)([:,].*)/; return Xchat::EAT_NONE unless ($1 && Xchat::user_info($1)); $_[0][1] = "\cB\cC03$1\cO$2"; Xchat::emit_print('Channel Message', @{$_[0]}); return Xchat::EAT_ALL; }); If you want to change the color from green to something else, change the 03 in the 6th line of the above to the color code of your choice. Ignore joins in a specific channelOne user wanted to ignore channel joins but not parts and quits in a specific channel. That can be accomplished with the following line: Xchat::hook_print('Join', sub { return Xchat::EAT_XCHAT if (lc $_[0][1] eq '#yourspecialchan'); return Xchat::EAT_NONE; }); Flash channel on joinAnother user wanted to flash the system tray icon when someone joins a channel, just as if someone had spoke in the channel. That can be accomplished with the following similar line: Xchat::hook_print('Join', sub { Xchat::command('tray -i 08') if (lc $_[0][1] eq '#yourspecialchan'); return Xchat::EAT_NONE; }); Op users who pm you a keywordIn the following case, this script will op any user if they pm you a specially keyword. While I personally believe it would be better to use chanserv for this purpose, not all networks have a proper services. foreach ('Private Message', 'Private Message to Dialog') { Xchat::hook_print($_, \&checkop); } sub checkop { if ($_[0][1] =~ /^keyword/) { Xchat::command("mode #yourchan +o ".Xchat::strip_code($_[0][0])); } } Ignore all lines that contain a specific wordOne user wanted to ignore all channel lines that included a specific word, in this case, the nick of a user that was already being ignored. The following script will do that, however it will not ignore lines that are either channel actions, or highlights, as it is always nice to see when someone is talking to you. Xchat::hook_print('Channel Message', sub { return Xchat::EAT_ALL if ($_[0][1] =~ /evilnick/i); }); Do not print messages locallyThis line will not be useful for most people. Apparently there are some servers that have a setting where users can tell the server to also send their own channel messages back to themselves. This is a hard concept to explain in one line, but it is used in lag detection. The user types a message in the client and it gets sent to the server. The server then sends the message on to all users in the channel including the client that sent it. In order to not see the initial print out, the following script can be used, which will hide all messages typed directly into a channel or query window. Xchat::hook_command("", sub {if (Xchat::get_info('network') eq "YourNetwork") {Xchat::command("quote PRIVMSG ". Xchat::get_info('channel') ." :".$_[1][0]); return Xchat::EAT_XCHAT;} }); This script must be used in conjunction with a network that is either auto joined, or connected to using /server YourNetwork. If you connect to the server using /server irc.yournetwork.net, the script will not work. Again though, this script will hide messages sent to this network, and so most people will not want this script. Encode a urlThe following code creates a /urlit command which accepts a string which will be encoded for URLs, and then said in the channel. Xchat::hook_command('urlit', sub { $_ = $_[1][1]; s/([^\w'*~!. -])/sprintf '%%%02x', ord $1/eg; tr/ /+/; Xchat::command('say http://www.site.com/q='.$_); return Xchat::EAT_XCHAT; }); Ignoring matching actions from a specific userSome channels have bridges to other networks, such as Jabber. While you may want to see what messages are said from the other side, if you have joins/parts hidden within XChat, you wouldn't want to see the joins from the bridge. If the messages are in the form of: * botname offsiteuser has become available * botname offsiteuser has left You can ignore these using the following script: Xchat::hook_print('Channel Action', sub { return Xchat::EAT_ALL if ($_[0][0] eq 'botname' && $_[0][1] =~ /^\S+ has (?:left|become available)/); }); Disable Freenode's CAPAB (+ and -) featureBy default, if XChat sees a CAPAB token when it connects (such as on FreeNode), XChat tells the server to enable a feature which prefixes each line with a + if the user who said it is identified to services, and a - if they have not. XChat will correctly parse these out (unless you have a poorly written script), but if you are connected to a bouncer with other clients who do not parse this out, they will have their lines prefixed with the + and -. To disable XChat from turning on this server side feature, use the following script: use Xchat qw(:all); hook_server( "005", sub { if($_[1][0] =~ s/CAPAB //) { command("RECV $_[1][0]"); return EAT_ALL} else { return EAT_NONE } } ); You will need to reconnect the bouncer/proxy to the server however, as CAPAB will be enabled until your connection to the IRC server has closed. This script will simply stop XChat from issuing the CAPAB command, if some other client enables the feature, XChat will correctly parse the + and -. Use the tab highlight color for private messagesIf you would like more distinction when a private message is received than just the new message color, you can use the color normally associated with a highlighted message. Xchat::hook_print('Private Message to Dialog', sub { Xchat::command('gui color 3'); return Xchat::EAT_NONE; }); Use ; at the beginning of lines to signify actionIn some environments, ; (semi-colon) at the beginning of a line signifies an action. To use this behavior within xchat, use the following script: Xchat::hook_command("", sub { if ($_[1][0] =~ m/^;(.*)/) { Xchat::command("me $1"); return Xchat::EAT_XCHAT; } }); Display nick in use messages in front tabThis line will cause all Nick Failed messages to show up in the current tab rather than in the server tab. This will only work if the message from the server ends with "Nickname is already in use." however. use Xchat qw (:all); hook_print('Server Text', sub { if ($_[0][0] =~ m/Nickname is already in use\.$/ && find_context != get_context) { set_context(find_context()); emit_print('Server Text', @{$_[0]}); return EAT_ALL; } return EAT_NONE; }); |