nickcomp
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | nickcomp [2007/02/27 04:57] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | # $EPIC: nickcomp.txt, | ||
+ | ======Synopsis: | ||
+ | [[load]] nickcomp \\ | ||
+ | /set nickcomp ON|OFF|TOGGLE \\ | ||
+ | /set nickcomp_char < | ||
+ | /set nickcomp_len < | ||
+ | /set nickcomp_multi ON|OFF|TOGGLE | ||
+ | |||
+ | ======Description: | ||
+ | This script will automatically complete a partially matching nickname | ||
+ | when you type it in a channel. | ||
+ | person' | ||
+ | by your message. | ||
+ | to specify the non-ambiguous part of a person' | ||
+ | change it for you before sending it off to irc. | ||
+ | |||
+ | If you /set nickcomp ON (the default), then the nickname completion action | ||
+ | is automatically done each time you type to the channel. | ||
+ | auto-completion will be done. | ||
+ | |||
+ | If you /set nickcomp_char : (the default) then the nickname of the person | ||
+ | you are speaking to should be the part before the colon. | ||
+ | another character, change this setting. | ||
+ | |||
+ | If you /set nickcomp_len 3 (the default), then there must be this many | ||
+ | character before the colon to qualify for automatic completion. | ||
+ | are fewer characters, it is not changed. | ||
+ | |||
+ | If you /set nickcomp_multi off (the default) and if the nickname you type | ||
+ | before the colon is ambiguous (expands to multiple nicknames) then the first | ||
+ | nick that matches will be used; if you set it to ON, then it will auto- | ||
+ | complete to ALL the nicknames, separated by commas. | ||
+ | |||
+ | ======History: | ||
+ | This script first appeared in epic5-0.3.1. | ||
+ | |||
nickcomp.txt · Last modified: 2007/02/27 04:57 by 127.0.0.1