<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.epicsol.org/help/lib/styles/feed.css" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://www.epicsol.org/help/feed.php">
        <title>EPIC5 help in DokuWiki</title>
        <description></description>
        <link>http://www.epicsol.org/help/</link>
        <image rdf:resource="http://www.epicsol.org/help/lib/images/favicon.ico" />
       <dc:date>2008-01-28T16:27:56+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://www.epicsol.org/help/2.8script?rev=1152712800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/abort?rev=1152712800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/about_epic?rev=1152712800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/abs?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/acos?rev=1156125339"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/acosh?rev=1156125339"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/activity?rev=1172682982"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/addset?rev=1171812000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/admin?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/after?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/afterw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/alias?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/alias_command?rev=1186321800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/aliasctl?rev=1186435564"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/allocdump?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/altchan?rev=1174087200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/arglists?rev=1172559028"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/arrays?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ascii?rev=1156886400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/asciiq?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/asin?rev=1156125339"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/asinh?rev=1156125339"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/assign?rev=1192295231"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/atan?rev=1156125339"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/atanh?rev=1156125339"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/atomic_scope?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/autoget?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/autojoin?rev=1173034200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/autoquery?rev=1172344800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/away?rev=1154402112"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/b64decode?rev=1153108800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/b64encode?rev=1153108800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/beep?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/before?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/beforew?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind?rev=1158583800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_altcharset?rev=1157157451"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_backspace?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_backward_character?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_backward_word?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_beginning_of_line?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_blink?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_bold?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_clear_screen?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_cpu_saver?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_delete_character?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_delete_next_word?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_delete_previous_word?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_delete_to_previous_space?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_end_of_line?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_erase_line?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_erase_to_beg_of_line?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_erase_to_end_of_line?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_forward_character?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_forward_word?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_highlight_off?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_next_window?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_nothing?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_parse_command?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_previous_window?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_quit_irc?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_quote_character?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_refresh_inputline?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_refresh_screen?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_refresh_status?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_reset_line?rev=1158663000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_reverse?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_scroll_backward?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_scroll_end?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_scroll_forward?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_scroll_start?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_self_insert?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_send_line?rev=1159748400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_stop_irc?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_swap_last_window?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_swap_next_window?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_swap_previous_window?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_switch_channels?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_switch_query?rev=1157157451"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_toggle_insert_mode?rev=1152720000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_toggle_stop_screen?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_transpose_characters?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_type_text?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_unclear_screen?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_underline?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_unstop_all_windows?rev=1152720000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bind_yank_from_cutbuffer?rev=1152712801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bindctl?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/bless?rev=1153170000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/block?rev=1156882800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/botmode?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/break?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/builtin_expando?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/builtins?rev=1172721000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/call?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cd?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ceil?rev=1153170000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/center?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cexist?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chanmode?rev=1153170000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chanmonitor?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/channel?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/channel_command?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/channel_function?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chanusers?rev=1153170000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chanwin?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chmod?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chngw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chop?rev=1156972800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chops?rev=1153170000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chr?rev=1156886400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/chrq?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cipher?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/clear?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/close?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cofilter?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/command_line?rev=1171939800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/commandqueues?rev=1173162000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/commands_overview?rev=1169630300"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/comment?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/common?rev=1153166400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/compile_opts?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/connect?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/connect_command?rev=1153728000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/connect_function?rev=1153728000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/continue?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/convert?rev=1153728000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/copattern?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/copyright?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/corfilter?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/corpattern?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cos?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cosh?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/count?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/country?rev=1153728000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/cparse?rev=1174842086"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/crypt?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp?rev=1153728000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_action?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_clientinfo?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_echo?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_finger?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_ping?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_time?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_userinfo?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_utc?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ctcp_version?rev=1153771200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/curcmd?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/curpos?rev=1153728000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/currchans?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/data_array?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/data_struct?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dbmctl?rev=1179193800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc?rev=1170458926"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_chat?rev=1170458926"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_close?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_closeall?rev=1154398714"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_get?rev=1157025429"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_list?rev=1153944000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_ports?rev=1179623955"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_raw?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_rename?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_resume?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dcc_send?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dccctl?rev=1179624000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/debug.irc?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/debugging?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/decode?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/defer?rev=1154398714"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/delarray?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/delitem?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/delitems?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/deop?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/describe?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/deuhc?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/die?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/diff?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/disambiguation?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/disconnect?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/do?rev=1153944001"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/dump?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/echo?rev=1154399286"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/edit_topic?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/encode?rev=1154399286"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/encrypt?rev=1157031213"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/encryptparm?rev=1172121600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/environment_variables?rev=1154399286"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/eof?rev=1154399286"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/epic-crypt-gpg-aa?rev=1172120849"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/epic-crypt-gpg?rev=1172120849"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/epic?rev=1154399286"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/etiquette?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/eval?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/exec?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/exec_command?rev=1156972800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/exec_function?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/exit?rev=1153108800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/exp?rev=1153108800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/expando_substitution?rev=1186435564"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/expandos?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/expressions?rev=1192295231"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fe?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fec?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ferror?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fexist?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/files?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/filter?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/finditem?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/finditems?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/findw?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/findws?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fix_arglist?rev=1172341200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/flood_control?rev=1172802724"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/floodinfo?rev=1172947800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/floodprot?rev=1172685000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/floor?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/flush?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fnexist?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/for?rev=1154401155"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/foreach?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/frewind?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fromw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fseek?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fsize?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/fskip?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ftell?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ftime?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ftruncate?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/functioncall?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/functions_overview?rev=1157605729"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/functions_script?rev=1154400332"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/geom?rev=1154402813"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getarrays?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getcap?rev=1166008063"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getcommands?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getenv?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getfunctions?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getgid?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getitem?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getlogin?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getmatches?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getopt?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getpgrp?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getrmatches?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getserial?rev=1171855258"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getset?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getsets?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/gettmatch?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/getuid?rev=1154402550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/glob?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/global?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/globi?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/glossary?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/grep?rev=1171939800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/guh?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/hash_32bit?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/help?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/highlight?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/history?rev=1174087200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/hold_mode?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/hook?rev=1154402989"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/hookctl?rev=1157079000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/hostname?rev=1158664800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/idle?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/if?rev=1180585200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ifindfirst?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ifinditem?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ifinditems?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/igetitem?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/igetmatches?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/igetrmatches?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ignore?rev=1157034000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ignorectl?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/index?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/indextoitem?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/indextoword?rev=1154404068"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/info?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/info_command?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/info_function?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/input?rev=1157109600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/input_char?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/input_handling?rev=1179609176"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/insert?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/insertw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/introduction?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/invite?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/iptolong?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/iptoname?rev=1154404068"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ipv6?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ircii_syntax?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/irclib?rev=1156132200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ircuser?rev=1158664800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isalpha?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isaway?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ischannel?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ischanop?rev=1160761867"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ischanvoice?rev=1154404068"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isconnected?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/iscurchan?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isdigit?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isdisplaying?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isencrypted?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isfilevalid?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ishalfop?rev=1160761867"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/isnumber?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ison?rev=1156966113"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/itemtoindex?rev=1154403642"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/jn?rev=1154404317"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/join?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/joinstr?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/jot?rev=1154404289"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/karll_arrays?rev=1172552257"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/key?rev=1154404511"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/key_bindings?rev=1154404511"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/kick?rev=1154404511"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/kill?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/killpid?rev=1154404511"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/knock?rev=1154404511"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/lastlog?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/lastlog_command?rev=1171939800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/lastlog_function?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/left?rev=1154405583"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/leftpc?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/leftw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/less-pipe?rev=1171738200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/less?rev=1171738200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/levelctl?rev=1171738200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/levels?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/levelwindow?rev=1154405507"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/license?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/line?rev=1156967631"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/links?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/list?rev=1154405233"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/listarray?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/listen?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/load?rev=1157161231"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/loadformats?rev=1172721000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/loadinfo?rev=1154405233"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/local.examp?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/local?rev=1154405233"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/log?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/log10?rev=1154405507"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/log_command?rev=1171513201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/log_function?rev=1156114200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/logctl?rev=1156967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/longtoip?rev=1154405233"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/lusers?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/lval?rev=1186435550"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mail?rev=1173043200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/man?rev=1154409365"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mangle_types?rev=1172344800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/map?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/map_command?rev=1154409365"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/map_script?rev=1173043200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mask?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/match?rev=1154409365"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/matchitem?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/maxlen?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/me?rev=1155950400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mesg?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/meta-compat?rev=1171939800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/metric_time?rev=1154409365"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mid?rev=1154409365"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/midw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mkdir?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mktime?rev=1157044800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mode?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/motd?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/motd_command?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/motd_script?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/msar?rev=1154409365"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/msg?rev=1157079000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/mychannels?rev=1154409509"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/myservers?rev=1156128692"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/names?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/nametoip?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/netsplit?rev=1172121600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/new_user?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/newaway?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/newnick?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/nick?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/nickcomp?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/nochops?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/nohighlight?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/nopaste?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/note?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notice?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notify?rev=1154410621"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notify_command?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notify_function?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notify_script?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notifywindows?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/notw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/numarrays?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/numitems?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/numlines?rev=1154410621"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/numonchannel?rev=1155953084"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/numsort?rev=1153108800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/numwords?rev=1154410382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on?rev=1192295390"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_action?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_channel_lost?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_channel_nick?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_channel_signoff?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_channel_sync?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_connect?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_ctcp?rev=1191860912"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_ctcp_reply?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_ctcp_request?rev=1191860912"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_activity?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_chat?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_connect?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_list?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_lost?rev=1179624000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_offer?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_raw?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_dcc_request?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_disconnect?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_encrypted_notice?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_encrypted_privmsg?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_error?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_exec?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_exec_errors?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_exec_exit?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_exec_prompt?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_exit?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_flood?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_general_notice?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_general_privmsg?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_hook?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_idle?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_input?rev=1155953746"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_invite?rev=1155953746"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_join?rev=1155953746"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_keybinding?rev=1157028799"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_kick?rev=1155953746"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_kill?rev=1155953746"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_list?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_mail?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_mode?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_mode_stripped?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_msg?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_msg_group?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_names?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_new_nickname?rev=1155955362"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_nickname?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_note?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_notice?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_notify_signoff?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_notify_signon?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_numeric?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_odd_server_stuff?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_oper_notice?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_operwall?rev=1157031210"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_part?rev=1156565036"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_pong?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_public?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_public_msg?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_public_notice?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_public_other?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_raw_irc?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_redirect?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_action?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_ctcp?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_dcc_chat?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_msg?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_notice?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_public?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_send_to_server?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_server_established?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_server_lost?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_server_notice?rev=1155955362"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_server_status?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_set?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_signoff?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_silence?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_ssl_server_cert?rev=1155955362"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_status_update?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_switch_channels?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_switch_windows?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_timer?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_topic?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_unknown_command?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_unload?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_wall?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_wallop?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_who?rev=1155955464"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_window?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_window_beforekill?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_window_command?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_window_create?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_window_kill?rev=1155954999"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_window_server?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/on_yell?rev=1155955362"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/onchannel?rev=1155958514"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/open?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/oper?rev=1155958382"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/output-help?rev=1179609176"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/outputinfo?rev=1155958606"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/package?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pad?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/parsekey?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/part?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pass?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/paste?rev=1171939800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pattern?rev=1179193800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/patterns?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pause?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/perl?rev=1153071059"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/perl_command?rev=1154062800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/perl_function?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/perlcall?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/perlxcall?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pf_loader?rev=1179193800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pid?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ping?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pipe?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pipe_function?rev=1155959901"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pipe_script?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pop?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pop_command?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pop_function?rev=1171738200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ppid?rev=1156886400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/prefix?rev=1155960338"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/pretend?rev=1155960338"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/printlen?rev=1155960338"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/programming?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/push?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/push_command?rev=1174668600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/push_function?rev=1174668600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/query?rev=1155960510"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/querywin?rev=1156129518"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/queue?rev=1155960510"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/quit?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/quote?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/quoting_hell?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/qword?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rand?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/random_numbers?rev=1171737223"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/randread?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rbind?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/read?rev=1181017200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/realpath?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/reconnect?rev=1157153317"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/reconnect_command?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/reconnect_script?rev=1172721000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/redirect?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/referring_to_servers?rev=1157157444"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regcomp?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regcomp_cs?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regerror?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regex?rev=1171740000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regexec?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regfree?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/regmatches?rev=1171378200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rehash?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/remw?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/remws?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rename?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/renumber?rev=1172685000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/repeat?rev=1154402112"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/repeat_command?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/repeat_function?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rest?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/restart?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/restw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/return?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/revdcc?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/reverse?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/revw?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rfilter?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/right?rev=1155968522"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rightw?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rindex?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rmatch?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rmatchitem?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rmdir?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rpattern?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rping?rev=1155967649"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/rsubstr?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ruby?rev=1154062800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ruby_command?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ruby_function?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sar?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/save?rev=1171738200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/say?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/scan?rev=1172121600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/screen?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/security?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sedcrypt?rev=1155980147"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/send?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sendline?rev=1159748400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/serial_numbers?rev=1155980147"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/server?rev=1160095114"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/server_description?rev=1164302400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/server_list?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/server_numerics?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/server_state?rev=1158664800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/serverctl?rev=1179193800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/serverwin?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/servlist?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/servports?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set?rev=1173324000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_allow_c1_chars?rev=1155979560"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_always_split_biggest?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_banner?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_banner_expand?rev=1155982946"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_beep?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_channel_name_width?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_client_information?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_clock?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_clock_24hour?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_clock_format?rev=1159743837"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_clock_interval?rev=1155982946"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_cmdchars?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_comment_hack?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_continued_line?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_cpu_saver_after?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_cpu_saver_every?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_current_window_level?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dcc_auto_send_rejects?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dcc_dequote_filenames?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dcc_long_pathnames?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dcc_sliding_window?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dcc_store_path?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dcc_use_gateway_addr?rev=1155982946"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_debug?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_dispatch_unknown_commands?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_display?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_do_notify_immediately?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_floating_point_math?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_floating_point_precision?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_after?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_ignore?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_maskuser?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_rate?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_rate_per?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_users?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_flood_warning?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_hide_private_channels?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_high_bit_escape?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_hold_interval?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_hold_mode?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_hold_slider?rev=1155982633"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_indent?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_input_prompt?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_insert_mode?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_key_interval?rev=1157221669"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_lastlog?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_lastlog_level?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_load_path?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_log?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_log_rewrite?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_logfile?rev=1156082475"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mail?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mail_interval?rev=1156082475"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mail_type?rev=1157031213"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mangle_display?rev=1173760705"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mangle_inbound?rev=1173243000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mangle_logfiles?rev=1173243000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mangle_outbound?rev=1173243000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_metric_time?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mirc_broken_dcc_resume?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_mode_stripper?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_new_server_lastlog_level?rev=1156972801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_no_control_log?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_no_ctcp_flood?rev=1156082475"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_no_fail_disconnect?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_notify?rev=1171855258"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_notify_interval?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_notify_level?rev=1156081883"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_notify_on_termination?rev=1158664801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_notify_userhost_automatic?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_num_of_whowas?rev=1156089480"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_old_math_parser?rev=1156972801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_old_server_lastlog_level?rev=1156972801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_output_rewrite?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_pad_char?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_quit_message?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_random_source?rev=1158637539"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_realname?rev=1171347600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_screen_options?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_scroll_lines?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_scrollback?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_scrollback_ratio?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_shell?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_shell_flags?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_shell_limit?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_show_channel_names?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_show_end_of_msgs?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_show_numerics?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_show_status_all?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_show_who_hopcount?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_away?rev=1156089480"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_channel?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_chanop?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_clock?rev=1156089480"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_cpu_saver?rev=1156089480"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_does_expandos?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_format?rev=1179624000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_format1?rev=1171812000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_format2?rev=1171812000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_halfop?rev=1171855258"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_hold?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_hold_lines?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_insert?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_mail?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_mode?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_nickname?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_no_repeat?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_noswap?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_notify?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_oper?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_overwrite?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_query?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_scrollback?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_server?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_ssl_off?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_ssl_on?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_umode?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_user?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_voice?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_status_window?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_suppress_from_remote_server?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_switch_channels_between_windows?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_term_does_bright_blink?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_translation?rev=1156089600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_translation_path?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_user_information?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_verbose_ctcp?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_word_break?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_wserv_path?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_wserv_type?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_xterm?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/set_xterm_options?rev=1156087121"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/setenv?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/setitem?rev=1156093288"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/setmail?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sha256?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/shift?rev=1156709231"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/shift_command?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/shift_function?rev=1186435564"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/shiftbrace?rev=1156972801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/shook?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/signals?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/silence?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sin?rev=1156094037"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sinh?rev=1156094037"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sleep?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/slowcat?rev=1157480400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/snip?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sort?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/space_character?rev=1156882732"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/special_vars?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/sping?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/splice?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/split?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/squery?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/squit?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/srand?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ssl?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stack?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/standard_loader?rev=1157222017"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/start?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/startupfile?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stat?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stats?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/status_function?rev=1156094037"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/status_line?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stime?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/strftime?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/strip?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stripansi?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stripansicodes?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stripc?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stripcrap?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/strlen?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/strtol?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/stub?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/subpackage?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/substr?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/suppressmotd?rev=1160162400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/switch?rev=1156093025"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/symbolctl?rev=1157079000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tabkey.ce?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tabkey.jm?rev=1173043200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tan?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tanh?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tcl?rev=1154062800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tcl_command?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tcl_function?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tdiff?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tdiff2?rev=1172721000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/text_hilight?rev=1154407800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/time?rev=1154402112"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/time_command?rev=1156096201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/time_function?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/timer?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/timerctl?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tobase?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tolower?rev=1163911807"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/topic?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/toupper?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tow?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/tr?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/trace?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/trunc?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/ttyname?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/twiddle?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/type?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/uhc?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/umask?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/uname?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unclear?rev=1171945200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/uniq?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unless?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unlink?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unload?rev=1156096201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unshift?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unshift_command?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unshift_function?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/unsplit?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/until?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/uping?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/urldecode?rev=1160094954"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/urlencode?rev=1160094954"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/userhost?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/userhost_command?rev=1164302400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/userhost_function?rev=1156972801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/userip?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/usermode?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/usetitem?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/using_perl?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/usleep?rev=1156095433"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/usrip?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/utime?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/utime_function?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/utime_script?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/version?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/version_command?rev=1156096470"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/version_function?rev=1171346745"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/wait?rev=1156966113"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/wallchops?rev=1156096470"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/wallops?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/welcome?rev=1183528200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/what_is_a_word?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/which?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/which_command?rev=1156096470"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/which_function?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/while?rev=1156097277"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/who?rev=1156096470"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/whois?rev=1156096470"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/whowas?rev=1156097565"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/winchan?rev=1172553600"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window?rev=1175120830"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_activity_handling?rev=1171855258"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_add?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_back?rev=1156105324"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_balance?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_beep_always?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_channel?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_clear?rev=1184106000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_create?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_delete?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_describe?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_discon?rev=1158664801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_double?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_echo?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_fixed?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_flush?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_flush_scrollback?rev=1157025430"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_goto?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_grow?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_hide?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_hide_others?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_hold_interval?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_hold_mode?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_hold_slider?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_indent?rev=1157030400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_kill?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_kill_all_hidden?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_kill_others?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_killable?rev=1156972801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_killswap?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_last?rev=1186321801"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_lastlog?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_lastlog_level?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_level?rev=1157034000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_list?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_log?rev=1157221669"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_logfile?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_move?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_move_to?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_name?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_new?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_new_hide?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_next?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_noserv?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_notified?rev=1156966113"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_notify?rev=1156966113"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_notify_level?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_notify_name?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_number?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_pop?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_previous?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_prompt?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_push?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_query?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_rebuild_scrollback?rev=1171855258"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_refnum?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_refnum_or_swap?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_refresh?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_rejoin?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_remove?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_scroll_backward?rev=1156105538"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_scroll_end?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_scroll_forward?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_scroll_start?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_scrolladj?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_scrollback?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_search_back?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_search_forward?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_server?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_show?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_show_all?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_shrink?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_size?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_skip?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_stack?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_status_format?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_status_format1?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_status_format2?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_status_special?rev=1156105538"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_swap?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_swappable?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_topline?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_toplines?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/window_unclear?rev=1171945201"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/windowctl?rev=1157023973"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/word?rev=1172803800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/wordtoindex?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/write?rev=1156098740"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/writeb?rev=1181017200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xdebug?rev=1152593863"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xdebug_command?rev=1164302400"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xdebug_function?rev=1172946000"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xecho?rev=1179193800"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xeval?rev=1156707773"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xform?rev=1181017200"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xquote?rev=1156876398"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/xtype?rev=1156105907"/>
                <rdf:li rdf:resource="http://www.epicsol.org/help/yn?rev=1156105907"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://www.epicsol.org/help/lib/images/favicon.ico">
        <title>EPIC5 help in DokuWiki</title>
        <link>http://www.epicsol.org/help/</link>
        <url>http://www.epicsol.org/help/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://www.epicsol.org/help/2.8script?rev=1152712800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:00+00:00</dc:date>
        <title>2.8script</title>
        <link>http://www.epicsol.org/help/2.8script?rev=1152712800</link>
        <description># $EPIC: 2.8script.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

load 2.8script

This is one of the default script loaded when the client is started; it is loaded from GLOBAL.  It redefines the returned messages from STATS queries and in channel ban lists.  It contains several aliases; those whose names are the same as built-in commands are intended to enhance them.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/abort?rev=1152712800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:00+00:00</dc:date>
        <title>abort</title>
        <link>http://www.epicsol.org/help/abort?rev=1152712800</link>
        <description>abort

This command initiates an orderly abnormal shutdown of EPIC using the  abort(3) C library function, which typically results in a core dump.

This command is intended for debugging purposes.

The abort command first appeared in “plus-9” (post-ircII, pre-EPIC).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/about_epic?rev=1152712800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:00+00:00</dc:date>
        <title>about_epic</title>
        <link>http://www.epicsol.org/help/about_epic?rev=1152712800</link>
        <description>EPIC is 100% backwards compatible with ircII because EPIC is ircII.  EPIC was originally built upon the ircII 2.6 client and has maintained faithfulness to remain current up to the 2.8.2 release.

EPIC is slightly larger than ircII-4.4 (about 40k on this system), but that is mostly because of the multitude of new features, the dual ANSI/K&amp;R compliant function headers, and the large amount of re-written code in an attempt to make ircII faster, more efficient, and more powerful.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/abs?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>abs</title>
        <link>http://www.epicsol.org/help/abs?rev=1152593863</link>
        <description># $EPIC: abs.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$abs(&lt;number&gt;)

Calculates the absolute value of &lt;number&gt;.

The absolute value of the argument, or nothing if no argument is specified.

	*  abs(-3)                returns “3”
	*  abs(5)                 returns “5”
	*  abs(0)                 returns “0”</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/acos?rev=1156125339">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T20:55:39+00:00</dc:date>
        <title>acos</title>
        <link>http://www.epicsol.org/help/acos?rev=1156125339</link>
        <description># $EPIC: acos.txt,v 1.3 2006/08/21 01:55:33 sthalik Exp $ 

$acos(&lt;number&gt;)

	*  Returns the arc cosine of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/acosh?rev=1156125339">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T20:55:39+00:00</dc:date>
        <title>acosh</title>
        <link>http://www.epicsol.org/help/acosh?rev=1156125339</link>
        <description># $EPIC: acosh.txt,v 1.3 2006/08/21 01:55:33 sthalik Exp $ 

$acosh(&lt;number&gt;)

	*  Returns the inverse hyperbolic cosine of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/activity?rev=1172682982">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-28T11:16:22+00:00</dc:date>
        <title>activity</title>
        <link>http://www.epicsol.org/help/activity?rev=1172682982</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/addset?rev=1171812000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-18T09:20:00+00:00</dc:date>
        <title>addset</title>
        <link>http://www.epicsol.org/help/addset?rev=1171812000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/admin?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>admin</title>
        <link>http://www.epicsol.org/help/admin?rev=1152712801</link>
        <description>admin 
  admin &lt;server&gt; 
  admin &lt;nickname&gt; 
 

This command asks a server to give you information about who runs this irc server and how you can contact them (usually by email.)

If you don’t specify any arguments, your local server will be queried. If you specify a remote server, it will be queried instead. If you specify another irc user, that user’s server will be queried.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/after?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>after</title>
        <link>http://www.epicsol.org/help/after?rev=1172803800</link>
        <description># $EPIC: after.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$after([&lt;count&gt;] &lt;char&gt; &lt;text&gt;)

	*  The &lt;count&gt; argument is optional, the default value is 1.  &lt;count&gt; must be some non-zero number to be recognized as a count.  If &lt;count&gt; is 0, it will be taken as the &lt;char&gt; argument, and &lt;count&gt; will default to 1!
	*  If &lt;count&gt; is positive, then the return value of this function is the trailing portion of &lt;text&gt; that is after the &lt;count&gt;th occurrence of any of the characters in &lt;char&gt;.
	*  If &lt;cou…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/afterw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>afterw</title>
        <link>http://www.epicsol.org/help/afterw?rev=1172803800</link>
        <description># $EPIC: afterw.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

$afterw(&lt;word&gt; &lt;pattern list&gt;)

	*  If the &lt;word&gt; argument is omitted this function returns the empty string.
	*  The &lt;pattern list&gt; does not actually need to be a list of wildcard patterns.  A list of literal words will work just fine.
	*  If &lt;word&gt; is not matched by any of the words in &lt;pattern list&gt;, this function returns the empty string.
	*  Otherwise, the function behaves “as if” the following had been performed: &lt;val&gt; = rma…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/alias?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>alias</title>
        <link>http://www.epicsol.org/help/alias?rev=1156876398</link>
        <description>This is a disambiguation page.  Do you mean the alias command or the aliasctl function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/alias_command?rev=1186321800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-05T08:50:00+00:00</dc:date>
        <title>alias_command</title>
        <link>http://www.epicsol.org/help/alias_command?rev=1186321800</link>
        <description>alias 
  alias &lt;alias-name&gt; 
  alias -&lt;alias-name&gt; 
  alias &lt;alias-name&gt; {block} 
  alias &lt;alias-name&gt; (&lt;argument-list&gt;) {block} 
 

Alias creates a macro which can be either used as the command in a  statement, and as a function name.  Just as with any other command or function, an alias receives an argument list.  Each time the alias is  invoked, the arguments are processed according to &lt;argument-list&gt;, and the block is executed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/aliasctl?rev=1186435564">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-06T16:26:04+00:00</dc:date>
        <title>aliasctl</title>
        <link>http://www.epicsol.org/help/aliasctl?rev=1186435564</link>
        <description>#$EPIC: aliasctl.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

$aliasctl(&lt;domain&gt; &lt;operation&gt; &lt;operand&gt; [&lt;rval&gt;]) 
  $aliasctl(&lt;domain&gt; GETPACKAGE &lt;lval&gt;) 
  $aliasctl(&lt;domain&gt; GET &lt;lval&gt;) 
  $aliasctl(&lt;domain&gt; SETPACKAGE &lt;lval&gt; &lt;package-name&gt;) 
  $aliasctl(&lt;domain&gt; SET &lt;lval&gt; &lt;rval&gt;) 
  $aliasctl(&lt;domain&gt; MATCH &lt;word&gt;) 
  $aliasctl(&lt;domain&gt; PMATCH &lt;pattern&gt;) 
  $aliasctl(&lt;domain&gt; EXISTS &lt;lval&gt;)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/allocdump?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>allocdump</title>
        <link>http://www.epicsol.org/help/allocdump?rev=1152593863</link>
        <description>allocdump &lt;filename&gt;

If you #define’d ALLOC_DEBUG in config.h (it is not by default), then  this command will write a log of all of the heap memory that is currently in use.  This is used by developers to check for memory leaks.

The argument is required.  If you not provide an argument, don’t say that I didn’t warn you.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/altchan?rev=1174087200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-16T18:20:00+00:00</dc:date>
        <title>altchan</title>
        <link>http://www.epicsol.org/help/altchan?rev=1174087200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/arglists?rev=1172559028">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-27T00:50:28+00:00</dc:date>
        <title>arglists</title>
        <link>http://www.epicsol.org/help/arglists?rev=1172559028</link>
        <description>Argument lists are an optional way to automatically shift values from $* into local variables.  You can use argument lists in your aliases or your ons.  The fix_arglist function also handles arglists.

Behavior of Argument Lists

When an alias or on is called, the magic variable $* is set with the arguments passed into your code.  Usually the first thing most people do is copy arguments from $* into local variables, such as:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/arrays?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>arrays</title>
        <link>http://www.epicsol.org/help/arrays?rev=1184106000</link>
        <description>EPIC supports a large number of different data types.  Among the least used, and least understood, are Karll’s arrays.  This is mostly due to the lack of publicized documentation for them.  No more.

IrcII has long supported an array type.  These are best identified as hash arrays (or associative arrays, for Perl hackers).  However, Karll’s arrays are different, more in line with the traditional notion of an array.  Due to how EPIC stores information, these arrays are not like normal variabl…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ascii?rev=1156886400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T16:20:00+00:00</dc:date>
        <title>ascii</title>
        <link>http://www.epicsol.org/help/ascii?rev=1156886400</link>
        <description># $EPIC: ascii.txt,v 1.2 2006/08/29 20:58:41 jnelson Exp $ 

$ascii(&lt;character list&gt;)

The ascii function converts a sequence of characters into a word list of codepoints.  Because EPIC only supports latin-1 at this time, all of  the codepoints are 0 to 255 (strictly 1 byte per codepoint).  If in the  future epic supports UTF8 or something like that, codepoints greater than  255 might be returned.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/asciiq?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>asciiq</title>
        <link>http://www.epicsol.org/help/asciiq?rev=1171513201</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/asin?rev=1156125339">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T20:55:39+00:00</dc:date>
        <title>asin</title>
        <link>http://www.epicsol.org/help/asin?rev=1156125339</link>
        <description># $EPIC: asin.txt,v 1.3 2006/08/21 01:55:33 sthalik Exp $ 

$asin(&lt;number&gt;)

	*  Returns the principal value in radians of the arc sine of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/asinh?rev=1156125339">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T20:55:39+00:00</dc:date>
        <title>asinh</title>
        <link>http://www.epicsol.org/help/asinh?rev=1156125339</link>
        <description># $EPIC: asinh.txt,v 1.3 2006/08/21 01:55:33 sthalik Exp $ 

$asinh(&lt;number&gt;)

	*  Returns the inverse hyperbolic sine of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/assign?rev=1192295231">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-13T12:07:11+00:00</dc:date>
        <title>assign</title>
        <link>http://www.epicsol.org/help/assign?rev=1192295231</link>
        <description>assign 
  assign &lt;variable name&gt; 
  assign -&lt;variable name&gt; 
  assign &lt;variable name&gt; &lt;value&gt;

ASSIGN is the general-purpose interface for creating and manipulating variables.  Just about any value can be assigned, whether it be a string or a number.  Internally, ircII-EPIC treats the contents of all variables as strings, though it is smart enough to distinguish between strings and numerical values for mathematical purposes.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/atan?rev=1156125339">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T20:55:39+00:00</dc:date>
        <title>atan</title>
        <link>http://www.epicsol.org/help/atan?rev=1156125339</link>
        <description># $EPIC: atan.txt,v 1.3 2006/08/21 01:55:33 sthalik Exp $ 

$atan(&lt;number&gt;)

	*  Returns the principal value in radians of the arc tangent of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/atanh?rev=1156125339">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T20:55:39+00:00</dc:date>
        <title>atanh</title>
        <link>http://www.epicsol.org/help/atanh?rev=1156125339</link>
        <description># $EPIC: atanh.txt,v 1.3 2006/08/21 01:55:33 sthalik Exp $ 

$atanh(&lt;number&gt;)

	*  Returns the inverse hyperbolic tangent of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/atomic_scope?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>atomic_scope</title>
        <link>http://www.epicsol.org/help/atomic_scope?rev=1171513201</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/autoget?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>autoget</title>
        <link>http://www.epicsol.org/help/autoget?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/autojoin?rev=1173034200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-04T12:50:00+00:00</dc:date>
        <title>autojoin</title>
        <link>http://www.epicsol.org/help/autojoin?rev=1173034200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/autoquery?rev=1172344800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-24T13:20:00+00:00</dc:date>
        <title>autoquery</title>
        <link>http://www.epicsol.org/help/autoquery?rev=1172344800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/away?rev=1154402112">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:15:12+00:00</dc:date>
        <title>away</title>
        <link>http://www.epicsol.org/help/away?rev=1154402112</link>
        <description>away 
  away -all 
  away &lt;away message&gt; 
  away -all &lt;away message&gt; 
 away -- &lt;away message&gt; 
 

You have the option of telling the irc server to send a message to anyone  who tries to contact you (while you are away from your keyboard).  This is your &lt;away message&gt;.  You can use the -all option to set all servers to the same &lt;away message&gt;.  When you return, use the command without any  arguments.  If your &lt;away message&gt; starts with a hyphen, you can prefix it with a double-hyphen so it won’…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/b64decode?rev=1153108800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T23:00:00+00:00</dc:date>
        <title>b64decode</title>
        <link>http://www.epicsol.org/help/b64decode?rev=1153108800</link>
        <description>$b64decode(&lt;stuff&gt;)

Returns the inverse RFC1421 transformation of &lt;stuff&gt;, commonly known  as Base64.  The inverse transformation converts four Base64 digits into  three bytes.

Alas, because ircII only supports C strings, if &lt;stuff&gt; decodes to  binary data (with nuls) it will probably not do what you hope.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/b64encode?rev=1153108800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T23:00:00+00:00</dc:date>
        <title>b64encode</title>
        <link>http://www.epicsol.org/help/b64encode?rev=1153108800</link>
        <description># $EPIC: b64encode.txt,v 1.2 2006/07/17 03:42:24 jnelson Exp $ 

$b64encode(&lt;stuff&gt;)

Returns the RFC1421 transformation of &lt;stuff&gt;, commonly known as Base64. Base64 converts three bytes of input into four Base64 digits.  By definition Base64 digits are safe to send over text-only transmissions.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/beep?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>beep</title>
        <link>http://www.epicsol.org/help/beep?rev=1152593863</link>
        <description>beep

This command makes your terminal emulator beep.  Sometimes it is simpler than ECHOing control-G’s.

This command is strictly local; it does not send beeps to other users.

If SET BEEP is OFF, then this command has no effect.

The beep command first appeared in ircII.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/before?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>before</title>
        <link>http://www.epicsol.org/help/before?rev=1172803800</link>
        <description># $EPIC: before.txt,v 1.2 2006/08/29 18:22:56 sthalik Exp $ 

$before([&lt;count&gt;] &lt;char&gt; &lt;text&gt;)

	*  The &lt;count&gt; argument is optional, the default value is 1.  &lt;count&gt; must be some non-zero number to be recognized as a count.  If &lt;count&gt; is 0, it will be taken as the &lt;char&gt; argument, and &lt;count&gt; will default to 1!
	*  If &lt;count&gt; is positive, then the return value of this function is the initial portion of &lt;text&gt; that is before the &lt;count&gt;th occurrence of any of the characters in &lt;char&gt;.
	*  If &lt;c…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/beforew?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>beforew</title>
        <link>http://www.epicsol.org/help/beforew?rev=1172803800</link>
        <description># $EPIC: beforew.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$beforew(&lt;word&gt; &lt;pattern list&gt;)

	*  If the &lt;word&gt; argument is omitted this function returns the empty string.
	*  The &lt;pattern list&gt; does not actually need to be a list of wildcard patterns.  A list of literal words will work just fine.
	*  If &lt;word&gt; is not matched by any of the words in &lt;pattern list&gt;, this function returns the empty string.
	*  Otherwise, the function behaves “as if” the following had been performed: &lt;val&gt; = r…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind?rev=1158583800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-18T07:50:00+00:00</dc:date>
        <title>bind</title>
        <link>http://www.epicsol.org/help/bind?rev=1158583800</link>
        <description>bind 
  bind -DEFAULTS 
  bind &lt;character_sequence&gt;  
  bind -RECURSIVE &lt;character_sequence&gt; 
  bind &lt;character_sequence&gt; &lt;action&gt; &lt;args&gt; 
  bind -SYMBOLIC &lt;symbolic_name&gt; &lt;action&gt; &lt;args&gt;// 
 

BIND allows you to control how the client behaves when you enter a sequence of one or more keys.  By default, the client binds most of the common key sequences to useful default values.  You may not necessarily need to bind your own key sequences unless you do not like the default values.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_altcharset?rev=1157157451">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-01T19:37:31+00:00</dc:date>
        <title>bind_altcharset</title>
        <link>http://www.epicsol.org/help/bind_altcharset?rev=1157157451</link>
        <description># $EPIC: bind_altcharset.txt,v 1.3 2006/09/02 00:37:24 jnelson Exp $ 

bind &lt;key&gt; altcharset

This keybinding toggles the use of the alternate character set in your  terminal emulator’s font -- if it has one.  On those fonts that do support alternate character sets, one set usually uses latin characters, and the other set uses VGA box drawing characters.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_backspace?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_backspace</title>
        <link>http://www.epicsol.org/help/bind_backspace?rev=1152712801</link>
        <description># $EPIC: bind_backspace.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; backspace

If the input cursor is at the start of the input line, nothing happens. Otherwise, the action is the composite action of &lt;backward_character&gt; and &lt;delete_character&gt;</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_backward_character?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_backward_character</title>
        <link>http://www.epicsol.org/help/bind_backward_character?rev=1152712801</link>
        <description># $EPIC: bind_backward_character.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; backward_character

If the cursor is at the beginning of the input line, nothing happens. Otherwise, the input cursor is moved to the previous character in the  input line.  If you are close enough to the left part of the screen, this action may cause the input line to scroll to the left.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_backward_word?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_backward_word</title>
        <link>http://www.epicsol.org/help/bind_backward_word?rev=1152712801</link>
        <description># $EPIC: bind_backward_word.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; backward_word

This function moves the cursor backward until it reaches the beginning of a word.  If the cursor is currently in the middle of a word, it is shifted to the beginning of that word.  If it is already at the beginning of a word, or on whitespace of any kind, it is moved back to the previous word.  It has no effect if the cursor is at the beginning of the first word.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_beginning_of_line?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>bind_beginning_of_line</title>
        <link>http://www.epicsol.org/help/bind_beginning_of_line?rev=1184106000</link>
        <description># $EPIC: bind_beginning_of_line.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; beginning_of_line

This function moves the cursor to the beginning of the input line. This may be a position not currently visible on screen, due to the way the client wraps long input.  It has no visible effect when the cursor is already at the beginning of the input line.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_blink?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_blink</title>
        <link>http://www.epicsol.org/help/bind_blink?rev=1152712801</link>
        <description># $EPIC: bind_blink.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; blink

This function toggles the current blink setting.  Due to internal limitations of the client, BLINK is displayed as an F on the input line, regardless of the key it is bound to.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_bold?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_bold</title>
        <link>http://www.epicsol.org/help/bind_bold?rev=1152712801</link>
        <description># $EPIC: bind_bold.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; bold

This function toggles the current boldface setting.  Due to internal limitations of the client, BOLD is displayed as a B on the input line, regardless of the key it is bound to.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_clear_screen?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_clear_screen</title>
        <link>http://www.epicsol.org/help/bind_clear_screen?rev=1152712801</link>
        <description># $EPIC: bind_clear_screen.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; clear_screen

This executes the CLEAR command, which updates the current input  window’s scrollable view so nothing is visible in it, and the next line of output will appear on the top line of the window.  If you are in hold mode or scrollback, you will not see any change to the window until you  exit hold mode or scrollback.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_cpu_saver?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>bind_cpu_saver</title>
        <link>http://www.epicsol.org/help/bind_cpu_saver?rev=1152593863</link>
        <description># $EPIC: bind_cpu_saver.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

bind &lt;key&gt; cpu_saver

This keybinding immediately switches the client to CPU saver mode.

Normally, when CPU saver is inactive, the system clock, notify system, and mail checking occur via regular intervals controlled by set CLOCK_INTERVAL, set NOTIFY_INTERVAL, and set MAIL_INTERVAL.  When CPU saver is activated, these sets are ignored, and the interval given by set
CPU_SAVER_EVERY is used instead.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_delete_character?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_delete_character</title>
        <link>http://www.epicsol.org/help/bind_delete_character?rev=1152712801</link>
        <description># $EPIC: bind_delete_character.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; delete_character

This function deletes the character currently under the cursor, then shifts any text to the right of the cursor one space to the left.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_delete_next_word?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_delete_next_word</title>
        <link>http://www.epicsol.org/help/bind_delete_next_word?rev=1152712801</link>
        <description># $EPIC: bind_delete_next_word.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; delete_next_word

This function deletes text on the input line from the position of the cursor forward to the end of the first word found.  If is it in the middle of a word, that word is truncated.  If it is on whitespace, all text and whitespace to the end of the next word are deleted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_delete_previous_word?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_delete_previous_word</title>
        <link>http://www.epicsol.org/help/bind_delete_previous_word?rev=1152712801</link>
        <description># $EPIC: bind_delete_previous_word.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; delete_previous_word

This function deletes text on the input line from the position of the cursor backward to the beginning of the first word found.  If is it in the middle of a word, the beginning of that word is chopped.  If it is on whitespace, all text and whitespace to the beginning of the previous word are deleted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_delete_to_previous_space?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_delete_to_previous_space</title>
        <link>http://www.epicsol.org/help/bind_delete_to_previous_space?rev=1152712801</link>
        <description># $EPIC: bind_delete_to_previous_space.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; delete_to_previous_space

This function deletes everything to the left of the cursor until a space is found.  If the character immediately before the cursor is whitespace of some kind, it does nothing.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_end_of_line?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>bind_end_of_line</title>
        <link>http://www.epicsol.org/help/bind_end_of_line?rev=1184106000</link>
        <description># $EPIC: bind_end_of_line.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; end_of_line

This function moves the cursor to the last character on the input line. This position may not be currently visible, due to the manner in which EPIC handles input line wrapping.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_erase_line?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_erase_line</title>
        <link>http://www.epicsol.org/help/bind_erase_line?rev=1152712801</link>
        <description># $EPIC: bind_erase_line.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; erase_line

This function clears the contents of the input line.  The data cleared is not preserved in the command history.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_erase_to_beg_of_line?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_erase_to_beg_of_line</title>
        <link>http://www.epicsol.org/help/bind_erase_to_beg_of_line?rev=1152712801</link>
        <description># $EPIC: bind_erase_to_beg_of_line.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; erase_to_beg_of_line

This function erases all text from (but not including) the cursor to the beginning of the input line.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_erase_to_end_of_line?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_erase_to_end_of_line</title>
        <link>http://www.epicsol.org/help/bind_erase_to_end_of_line?rev=1152712801</link>
        <description># $EPIC: bind_erase_to_end_of_line.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; erase_to_end_of_line

This function erases all text from (and including) the cursor to the end of the input line.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_forward_character?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_forward_character</title>
        <link>http://www.epicsol.org/help/bind_forward_character?rev=1152712801</link>
        <description># $EPIC: bind_forward_character.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; forward_character

This function causes the cursor to move right by one character.  It has no effect if the cursor is at the end of the input line.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_forward_word?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_forward_word</title>
        <link>http://www.epicsol.org/help/bind_forward_word?rev=1152712801</link>
        <description># $EPIC: bind_forward_word.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; forward_word

This function moves the cursor forward to the beginning of the next word in the input line.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_highlight_off?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_highlight_off</title>
        <link>http://www.epicsol.org/help/bind_highlight_off?rev=1152712801</link>
        <description># $EPIC: bind_highlight_off.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; highlight_off

This function turns off any special highlighting in use prior to this character, including ANSI color escape sequences.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_next_window?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_next_window</title>
        <link>http://www.epicsol.org/help/bind_next_window?rev=1152712801</link>
        <description># $EPIC: bind_next_window.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; next_window

This function causes the client to change the current window to the one immediately below the current one in the window list.  If the current window is the last in the list, the first becomes the current window.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_nothing?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>bind_nothing</title>
        <link>http://www.epicsol.org/help/bind_nothing?rev=1152593863</link>
        <description># $EPIC: bind_nothing.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

bind &lt;key&gt; nothing

This function causes the specified key to do nothing, effectively disabling it.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_parse_command?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_parse_command</title>
        <link>http://www.epicsol.org/help/bind_parse_command?rev=1152712801</link>
        <description># $EPIC: bind_parse_command.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; parse_command &lt;commands&gt;

This function causes the specified command(s) to be executed when the given key is pressed.  If multiple commands are desired, they may be surrounded with curly braces.  Command-line expando variables ($*, $2, $n-m, etc.) are expanded as if there were no arguments given.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_previous_window?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_previous_window</title>
        <link>http://www.epicsol.org/help/bind_previous_window?rev=1152712801</link>
        <description># $EPIC: bind_previous_window.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; previous_window

This function causes the client to change the current window to the one immediately above the current one in the window list.  If the current window is the first in the list, the last becomes the current window.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_quit_irc?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_quit_irc</title>
        <link>http://www.epicsol.org/help/bind_quit_irc?rev=1152712801</link>
        <description># $EPIC: bind_quit_irc.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; quit_irc

This function causes the client to sign off from the irc network.

Thus function has the same effect as the QUIT command, except that a specific QUIT reason cannot be specified.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_quote_character?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>bind_quote_character</title>
        <link>http://www.epicsol.org/help/bind_quote_character?rev=1152593863</link>
        <description># $EPIC: bind_quote_character.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

bind &lt;key&gt; quote_character

This function quotes, or escapes, the next key entered.  It overrides the key’s normal default meaning and forces it to insert itself into the input buffer.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_refresh_inputline?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_refresh_inputline</title>
        <link>http://www.epicsol.org/help/bind_refresh_inputline?rev=1152712801</link>
        <description># $EPIC: bind_refresh_inputline.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; refresh_inputline

This function causes the client to redraw the input line.  It is mostly only useful when another process sends data to the client’s tty, which sometimes corrupts the display of the input line (but not the actual contents).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_refresh_screen?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_refresh_screen</title>
        <link>http://www.epicsol.org/help/bind_refresh_screen?rev=1152712801</link>
        <description># $EPIC: bind_refresh_screen.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; refresh_screen

This function causes the client to redraw the screen line by line.  It is mostly only useful when another process sends data to the client’s tty, which sometimes corrupts the screen display (but not the actual contents).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_refresh_status?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_refresh_status</title>
        <link>http://www.epicsol.org/help/bind_refresh_status?rev=1152712801</link>
        <description># $EPIC: bind_refresh_status.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; refresh_status

This function forces the client to update and redraw the status line to ensure it has the current values.  This is most often necessary if you use set STATUS_DOES_EXPANDOS and you change the value of one of the expandos in the status_format.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_reset_line?rev=1158663000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-19T05:50:00+00:00</dc:date>
        <title>bind_reset_line</title>
        <link>http://www.epicsol.org/help/bind_reset_line?rev=1158663000</link>
        <description># $EPIC: bind_reset_line.txt,v 1.2 2006/09/19 10:48:09 sthalik Exp $ 

bind &lt;key sequence&gt; reset_line &lt;new text&gt;

This binding replaces the current contents of the input line with the  &lt;new text&gt;.  The &lt;new text&gt; is treated as though it were passed through xtype -l.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_reverse?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_reverse</title>
        <link>http://www.epicsol.org/help/bind_reverse?rev=1152712801</link>
        <description># $EPIC: bind_reverse.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; reverse

This function toggles the current reverse video setting.  Due to internal limitations of the client, REVERSE is displayed as a V on the input line, regardless of the key it is bound to.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_scroll_backward?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_scroll_backward</title>
        <link>http://www.epicsol.org/help/bind_scroll_backward?rev=1152712801</link>
        <description># $EPIC: bind_scroll_backward.txt,v 1.2 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; scroll_backward

This executes the WINDOW SCROLL_BACKWARD command.  It moves the scrollback view backward (towards older output).  The amount it moves is determined by SET(4) SCROLLBACK_RATIO as a percentage.  It is usual and customary when you scroll backward for the scrollback view to become the current view, so you should immediately see an effect.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_scroll_end?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_scroll_end</title>
        <link>http://www.epicsol.org/help/bind_scroll_end?rev=1152712801</link>
        <description># $EPIC: bind_scroll_end.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; scroll_end

This function is used to end the lastlog scrollback mode.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_scroll_forward?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>bind_scroll_forward</title>
        <link>http://www.epicsol.org/help/bind_scroll_forward?rev=1156876398</link>
        <description># $EPIC: bind_scroll_forward.txt,v 1.4 2006/08/29 18:22:56 sthalik Exp $ 

bind &lt;key&gt; scroll_forward

This function allows the user to move forward in the client’s lastlog one page at a time.  The percentage of the screen that makes up a page is defined by the set(4) set scrollback_ratio variable.  This is useful for reviewing events as they happened, in a manner easier than LASTLOG provides.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_scroll_start?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_scroll_start</title>
        <link>http://www.epicsol.org/help/bind_scroll_start?rev=1152712801</link>
        <description># $EPIC: bind_scroll_start.txt,v 1.3 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; scroll_start

This function causes the client to enter scrollback mode.  This allows the lastlog buffer to be viewed interactively.  Any server messages received while in scrollback mode are queued, and are not displayed until the client exits scrollback mode.  It is generally a good idea to set HOLD_MODE on while in scrollback mode.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_self_insert?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_self_insert</title>
        <link>http://www.epicsol.org/help/bind_self_insert?rev=1152712801</link>
        <description># $EPIC: bind_self_insert.txt,v 1.3 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; self_insert

This function overrides the key’s default value, causing it to insert itself into the input buffer, instead of doing what it would normally do.  This can be used to intentionally prevent certain control keys from being misused.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_send_line?rev=1159748400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-01T19:20:00+00:00</dc:date>
        <title>bind_send_line</title>
        <link>http://www.epicsol.org/help/bind_send_line?rev=1159748400</link>
        <description># $EPIC: bind_send_line.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; send_line

This function causes the current input buffer to be sent to the current server, in a manner like that of SENDLINE.  To quell any confusion, this is typically the default behavior of the return/enter key.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_stop_irc?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>bind_stop_irc</title>
        <link>http://www.epicsol.org/help/bind_stop_irc?rev=1156876398</link>
        <description># $EPIC: bind_stop_irc.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

bind &lt;key&gt; stop_irc

This command causes the client process to temporarily stop, returning the user to the parent process that started the client (usually the user’s command shell).  This is useful for executing commands that aren’t well suited to EXEC.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_swap_last_window?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_swap_last_window</title>
        <link>http://www.epicsol.org/help/bind_swap_last_window?rev=1152712801</link>
        <description># $EPIC: bind_swap_last_window.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; swap_last_window

This function swaps the current window with the most recently hidden window.  If no windows are hidden, this function has no effect.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_swap_next_window?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_swap_next_window</title>
        <link>http://www.epicsol.org/help/bind_swap_next_window?rev=1152712801</link>
        <description># $EPIC: bind_swap_next_window.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; swap_next_window

This executes the WINDOW NEXT command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_swap_previous_window?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_swap_previous_window</title>
        <link>http://www.epicsol.org/help/bind_swap_previous_window?rev=1152712801</link>
        <description># $EPIC: bind_swap_previous_window.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; swap_previous_window

This executes the WINDOW PREVIOUS command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_switch_channels?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_switch_channels</title>
        <link>http://www.epicsol.org/help/bind_switch_channels?rev=1152712801</link>
        <description># $EPIC: bind_switch_channels.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; switch_channels

This function changes the current channel in the current window.  It can be used to cycle through all channels in the window.  However, it will only switch to channels that are not already being directed to another window.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_switch_query?rev=1157157451">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-01T19:37:31+00:00</dc:date>
        <title>bind_switch_query</title>
        <link>http://www.epicsol.org/help/bind_switch_query?rev=1157157451</link>
        <description># $EPIC: bind_switch_query.txt,v 1.3 2006/09/02 00:37:24 jnelson Exp $ 

bind &lt;key&gt; switch_query

When you have multiple query targets in your query list, you can cycle through them to set the “current” query using this keybinding.  It works on the same princple as switch_channels.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_toggle_insert_mode?rev=1152720000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T11:00:00+00:00</dc:date>
        <title>bind_toggle_insert_mode</title>
        <link>http://www.epicsol.org/help/bind_toggle_insert_mode?rev=1152720000</link>
        <description># $EPIC: bind_toggle_insert_mode.txt,v 1.3 2006/07/12 15:01:19 sthalik Exp $ 

bind &lt;key&gt; toggle_insert_mode

This toggles the client’s default input mode between insert mode and overwrite mode.  In insert mode, text typed in inserted into the input buffer, shifting text following the input to the right, preserving it. In overwrite mode, text typed will overwrite any following text.  The mode is insignificant when there is no text following the cursor.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_toggle_stop_screen?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_toggle_stop_screen</title>
        <link>http://www.epicsol.org/help/bind_toggle_stop_screen?rev=1152712801</link>
        <description># $EPIC: bind_toggle_stop_screen.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; toggle_stop_screen

This executes a WINDOW HOLD_MODE TOGGLE in your current window.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_transpose_characters?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_transpose_characters</title>
        <link>http://www.epicsol.org/help/bind_transpose_characters?rev=1152712801</link>
        <description># $EPIC: bind_transpose_characters.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; transpose_characters

This function swaps the character under the cursor with the character immediately before it.  It has no effect if the cursor is at the end of the input line, or if no characters precede the current one.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_type_text?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_type_text</title>
        <link>http://www.epicsol.org/help/bind_type_text?rev=1152712801</link>
        <description># $EPIC: bind_type_text.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; type_text &lt;text&gt;

This function executes XTYPE -L &lt;text&gt;, which means it adds &lt;text&gt; to the input buffer literally, ignoring all key bindings and treating each character as though it were bound to bind SELF_INSERT.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_unclear_screen?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_unclear_screen</title>
        <link>http://www.epicsol.org/help/bind_unclear_screen?rev=1152712801</link>
        <description># $EPIC: bind_unclear_screen.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; unclear_screen

This function un-clears a /clear command or a /bind &lt;key&gt; clear_screen.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_underline?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_underline</title>
        <link>http://www.epicsol.org/help/bind_underline?rev=1152712801</link>
        <description># $EPIC: bind_underline.txt,v 1.2 2006/07/12 13:26:15 sthalik Exp $ 

bind &lt;key&gt; underline

This function toggles the current underline setting.  Due to internal limitations of the client, UNDERLINE is displayed as a ^V_^V on the input line, regardless of the key it is bound to.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_unstop_all_windows?rev=1152720000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T11:00:00+00:00</dc:date>
        <title>bind_unstop_all_windows</title>
        <link>http://www.epicsol.org/help/bind_unstop_all_windows?rev=1152720000</link>
        <description># $EPIC: bind_unstop_all_windows.txt,v 1.3 2006/07/12 15:01:19 sthalik Exp $ 

bind &lt;key&gt; unstop_all_windows

This executes /WINDOW HOLD_MODE OFF in all windows.  Windows that were stopped with TOGGLE_STOP_SCREEN are restarted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bind_yank_from_cutbuffer?rev=1152712801">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-12T09:00:01+00:00</dc:date>
        <title>bind_yank_from_cutbuffer</title>
        <link>http://www.epicsol.org/help/bind_yank_from_cutbuffer?rev=1152712801</link>
        <description># $EPIC: bind_yank_from_cutbuffer.txt,v 1.3 2006/07/12 13:57:46 sthalik Exp $ 

bind &lt;key&gt; yank_from_cutbuffer

This function restores the last text string deleted from the input buffer with DELETE_NEXT_WORD, DELETE_PREVIOUS_WORD, ERASE_LINE, ERASE_TO_END_OF_LINE, or DELETE_TO_PREVIOUS_SPACE.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bindctl?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>bindctl</title>
        <link>http://www.epicsol.org/help/bindctl?rev=1172803800</link>
        <description># $EPIC: bindctl.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$bindctl(FUNCTION &lt;function&gt; &lt;action&gt; [&lt;args]&gt;) 
  $bindctl(SEQUENCE &lt;sequence&gt; &lt;action&gt; [&lt;args]&gt;) 
  $bindctl(MAP [&lt;sequence&gt;] [&lt;action&gt;])

	*  This function is a low-level interface to the client’s keybindings system.
	*  There are three top-level arguments which can be passed to the function:
		*  FUNCTION: Manipulates the functions which key sequences can be bound to.
		*  SEQUENCE: Manipulates the key sequences themselves.
		*…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/bless?rev=1153170000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T16:00:00+00:00</dc:date>
        <title>bless</title>
        <link>http://www.epicsol.org/help/bless?rev=1153170000</link>
        <description>bless

Ordinarily, the local variables of an atomic scope are only visible to that atomic scope, and cannot be used outside.  Sometimes you need to be able to access an atomic scope’s local variables within another atomic scope.  Two atomic scopes can cooperate at runtime to accomplish this if the enclosing scope does wait and the enclosed scope does bless.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/block?rev=1156882800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T15:20:00+00:00</dc:date>
        <title>block</title>
        <link>http://www.epicsol.org/help/block?rev=1156882800</link>
        <description>A block is a sequence of statements separated by semicolons. A block statement is a block that is optionally surrounded by curly braces. For more details, see ircii syntax.

A block statement containing two statements 
{
	echo one;
	echo two
}</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/botmode?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>botmode</title>
        <link>http://www.epicsol.org/help/botmode?rev=1152593863</link>
        <description>botmode

If you are running epic in “dumb mode” (with the -d command line option), you may use the BOTMODE command to complete the transformation into  a bot, equivalent to using the -b command line option.

You may want to do this if your script needs to interact with the user before launching into a bot mode (for example, asking configuration  questions, or even just telling the user what you’re doing).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/break?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>break</title>
        <link>http://www.epicsol.org/help/break?rev=1156876398</link>
        <description>break

Break, like its C counterpart, breaks out of a loop.
 @loop = 0
 while (0==0) {                      /* endless loop? */
   @loop++
   if (loop==20) break
 }                                   /* loop only made 20 iterations */ 
alias; continue; return; for; while; until</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/builtin_expando?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>builtin_expando</title>
        <link>http://www.epicsol.org/help/builtin_expando?rev=1153166400</link>
        <description># $EPIC: builtin_expando.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$builtin_expando(&lt;expando name&gt;)

	*  If the &lt;expando name&gt; argument is omitted the empty string is returned.
	*  If the inline expando &lt;expando name&gt; does not exist, the empty string is returned.
	*  This function returns the value that would be returned by the “inline expando” $&lt;expando name&gt;.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/builtins?rev=1172721000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-28T21:50:00+00:00</dc:date>
        <title>builtins</title>
        <link>http://www.epicsol.org/help/builtins?rev=1172721000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/call?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>call</title>
        <link>http://www.epicsol.org/help/call?rev=1153166400</link>
        <description>call

CALL produces a gdb/dbx-like stack trace of the alias currently being executed.  It returns a list of the commands currently being executed, tracing back from the current command, to the command that called it, and so forth until the CALL command itself it listed.  A deeply nested alias might have the following alias stack:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cd?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>cd</title>
        <link>http://www.epicsol.org/help/cd?rev=1152593863</link>
        <description>cd 
 cd &lt;path&gt;

The cd command changes the current working directory for the process. If the &lt;path&gt; is given, the current directory is changed to it. If the &lt;path&gt; is not given, the current directory is displayed. If &lt;path&gt; is invalid or cannot be changed to, an error will be displayed, and the current directory will not change.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ceil?rev=1153170000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T16:00:00+00:00</dc:date>
        <title>ceil</title>
        <link>http://www.epicsol.org/help/ceil?rev=1153170000</link>
        <description># $EPIC: ceil.txt,v 1.2 2006/07/17 20:15:25 sthalik Exp $ 

$ceil(&lt;number&gt;)

Calculates the smallest integer that is greater than or equal to &lt;number&gt;

The smallest integer that is greater than or equal to the argument, or nothing if no argument is specified.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/center?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>center</title>
        <link>http://www.epicsol.org/help/center?rev=1153166400</link>
        <description># $EPIC: center.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$center(&lt;width&gt; &lt;text&gt;)

This function returns the input text right-justified in a buffer that is precisely (  / 2) + strlen(text) ) characters wide.  The width must be given, there is no default.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cexist?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>cexist</title>
        <link>http://www.epicsol.org/help/cexist?rev=1153166400</link>
        <description># $EPIC: cexist.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$cexist(&lt;command&gt;)

This function tells wether or not a built-in command exists.

This can be used to emulate a built-in command in older versions of epic that may not support it.
  1   If the built-in command &lt;command&gt; exists      0   If &lt;command&gt; doesn’t exist</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chanmode?rev=1153170000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T16:00:00+00:00</dc:date>
        <title>chanmode</title>
        <link>http://www.epicsol.org/help/chanmode?rev=1153170000</link>
        <description># $EPIC: chanmode.txt,v 1.3 2006/07/17 20:15:25 sthalik Exp $ 

$chanmode(&lt;channel list&gt;)

	*  If the &lt;channel list&gt; argument is omitted, the current channel is used.  THIS MAY NOT BE THE CORRECT CHANNEL IN AN /ON!
	*  &lt;channel list&gt; is taken as a word list (space separated) of channel names.  The asterisk (”*”) is a special channel name that refers to the current window’s current channel.  THIS MAY NOT BE THE CORRECT CHANNEL IN AN /ON!
	*  The return value is a word list of channel modes …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chanmonitor?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>chanmonitor</title>
        <link>http://www.epicsol.org/help/chanmonitor?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/channel?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>channel</title>
        <link>http://www.epicsol.org/help/channel?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the channel command or the channel function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/channel_command?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>channel_command</title>
        <link>http://www.epicsol.org/help/channel_command?rev=1156876398</link>
        <description># $EPIC: channel_command.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

channel 
  channel -invite 
  channel &lt;channel list&gt; 
  channel &lt;channel list&gt; &lt;key list&gt;

Channels are the most important part of IRC.  A “channel” is a place where one or more people can congregate and talk to each other.  Each channel has a name, and there are an almost limitless number of channels available. Channels are shared amongst all of the servers of a network.  Each network has a different set of channels than…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/channel_function?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>channel_function</title>
        <link>http://www.epicsol.org/help/channel_function?rev=1153166400</link>
        <description># $EPIC: channel_function.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$channel(&lt;channel name&gt;)

This function returns some extended information about who’s on a channel. It returns a sorted list of nicknames prepended by two characters. If a &lt;channel name&gt; is not supplied, the current channel will be assumed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chanusers?rev=1153170000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T16:00:00+00:00</dc:date>
        <title>chanusers</title>
        <link>http://www.epicsol.org/help/chanusers?rev=1153170000</link>
        <description># $EPIC: chanusers.txt,v 1.3 2006/07/17 20:15:25 sthalik Exp $ 

$chanusers(&lt;channel&gt;)

	*  This function is a synonym for $onchannel() and is provided for compatibility with ircII.
	*  See the help file for $onchannel() for more particulars.

This function first appeared in ircII-2.6.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chanwin?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>chanwin</title>
        <link>http://www.epicsol.org/help/chanwin?rev=1152593863</link>
        <description># $EPIC: chanwin.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$chanwin(&lt;window refnum/name&gt;|&lt;channel&gt;)

$chanwin() and $winchan() are the same function. 

	*  If no argument given: 
		*  Return the current window’s current channel.

	*  If one argument, and it’s a window refnum:
		*  Return that window’s current channel.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chmod?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>chmod</title>
        <link>http://www.epicsol.org/help/chmod?rev=1172803800</link>
        <description># $EPIC: chmod.txt,v 1.2 2006/07/17 20:15:25 sthalik Exp $ 

$chmod(&lt;file&gt; &lt;mode&gt;)

This function provides an interface to the Unix system call chmod(2).  It applies the given mode to the file specified.  Refer to your Unix system manual for more information (usually “man 2 chmod”).  The mode must be in numeric format.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chngw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>chngw</title>
        <link>http://www.epicsol.org/help/chngw?rev=1172803800</link>
        <description># $EPIC: chngw.txt,v 1.3 2006/09/07 01:18:17 sthalik Exp $ 

$chngw(&lt;index&gt; &lt;word&gt; &lt;word list&gt;)

	*  If the &lt;index&gt; argument is omitted the empty string is returned.
	*  If the &lt;word&gt; argument is omitted the empty string is returned.
	*  If the &lt;index&gt; argument is less than 0 then &lt;word list&gt; is returned.
	*  The return value if &lt;word list&gt; with the &lt;index&gt;th word, counting from zero, changed to &lt;word&gt;.
	*  Historically &lt;word list&gt; does not support double-quoted words. This may change in the fut…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chop?rev=1156972800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-30T16:20:00+00:00</dc:date>
        <title>chop</title>
        <link>http://www.epicsol.org/help/chop?rev=1156972800</link>
        <description># $EPIC: chop.txt,v 1.3 2006/08/30 21:02:47 sthalik Exp $ 

$chop(&lt;num&gt; &lt;text&gt;)

This function chops &lt;num&gt; characters from the end of &lt;text&gt;.

It is an excellent shortcut for $mid() expressions starting at the first character of &lt;text&gt;.

&lt;text&gt; with &lt;num&gt; characters removed from the end</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chops?rev=1153170000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T16:00:00+00:00</dc:date>
        <title>chops</title>
        <link>http://www.epicsol.org/help/chops?rev=1153170000</link>
        <description># $EPIC: chops.txt,v 1.3 2006/07/17 20:15:25 sthalik Exp $ 

$chops(&lt;channel&gt;)

	*  If the &lt;channel&gt; argument is omitted, the current window’s current channel is used.  THIS IS NOT NECCESARILY THE CORRECT CHANNEL IN AN /ON!
	*  If the &lt;channel&gt; argument is the literal star character (``*’‘), the current window’s current channel is used.  THIS IS NOT NECCESARILY THE CORRECT CHANNEL IN AN /ON!
	*  This function returns the channel operators on the specified channel.
	*  You must be on the …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chr?rev=1156886400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T16:20:00+00:00</dc:date>
        <title>chr</title>
        <link>http://www.epicsol.org/help/chr?rev=1156886400</link>
        <description># $EPIC: chr.txt,v 1.2 2006/08/29 20:58:41 jnelson Exp $ 

$chr(&lt;list of codepoints&gt;)

The chr function converts a word list of codepoints into a sequence of  characters.  Because EPIC only supports latin-1 at this time, only the  codepoints 0 to 255 provide defined behavior.  Other codepoints will yield one character per codepoint, but the character is undefined.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/chrq?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>chrq</title>
        <link>http://www.epicsol.org/help/chrq?rev=1160162400</link>
        <description># $EPIC: chrq.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$chrq(&lt;list of codepoints&gt;)

The chrq function is much the same as the chr function, but the result is filtered through ctcp enquoting.  Even if the input string contains binary data (including nuls) the output string is safe for assigning to a variable and sending over irc.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cipher?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>cipher</title>
        <link>http://www.epicsol.org/help/cipher?rev=1153166400</link>
        <description># $EPIC: cipher.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$cipher(&lt;refnum&gt;)

	*  This function returns the value of SSL_get_cipher() for the SSL enabled server connection for server &lt;refnum&gt;.
	*  It probably does nothing useful if &lt;refnum&gt; is not an ssl-enabled server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/clear?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>clear</title>
        <link>http://www.epicsol.org/help/clear?rev=1184106000</link>
        <description># $EPIC: clear.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

clear [-all|-hidden|-visible] [-unhold]

CLEAR clears the current window of all text.  It is useful for wiping a screen that has rendered improperly (such as due to a bad termcap entry) or that contains sensitive information (such as one’s OPER password).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/close?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>close</title>
        <link>http://www.epicsol.org/help/close?rev=1153166400</link>
        <description># $EPIC: close.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$close(&lt;file descriptor&gt;)

This function unbinds the given file descriptor (previously returned by the $open() function) from the underlying file, causing the file to be committed to disk if necessary.  An error is returned if it is passed a file descriptor not produced by an $open() call.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cofilter?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>cofilter</title>
        <link>http://www.epicsol.org/help/cofilter?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/command_line?rev=1171939800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T20:50:00+00:00</dc:date>
        <title>command_line</title>
        <link>http://www.epicsol.org/help/command_line?rev=1171939800</link>
        <description>There are a number of command line options available. The basic command-line syntax is: 
 epic5 [&lt;switches&gt;] [&lt;nickname&gt; [&lt;server list&gt;]]
 The nickname may be at most 30 characters long.  The server list may be a space-delimited list of server descriptions.  Each server name may use the server:port notation if a port other than the default (usually 6667) is desired.  The available switches are as follows:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/commandqueues?rev=1173162000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-06T00:20:00+00:00</dc:date>
        <title>commandqueues</title>
        <link>http://www.epicsol.org/help/commandqueues?rev=1173162000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/commands_overview?rev=1169630300">
        <dc:format>text/html</dc:format>
        <dc:date>2007-01-24T03:18:20+00:00</dc:date>
        <title>commands_overview</title>
        <link>http://www.epicsol.org/help/commands_overview?rev=1169630300</link>
        <description>Commands are the way for interacting with the client. They allow various tasks to be done - interacting with the remote server, changing client’s user interface (including, but not limited to managing windows and changing key bindings), programming the client and much more.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/comment?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>comment</title>
        <link>http://www.epicsol.org/help/comment?rev=1153166400</link>
        <description># $EPIC: comment.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

comment [&lt;anything&gt;]

This is exactly what it says, a comment.  It does nothing.  It is useful in scripts for explaining bits of code, adding disclaimers or copyright notices, etc.

There are also several symbolic comments.  Both the # and : characters may be used to designate comments.  There is no functional difference between any of them.  Additionally, EPIC supports C /* */ multiline comments.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/common?rev=1153166400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-17T15:00:00+00:00</dc:date>
        <title>common</title>
        <link>http://www.epicsol.org/help/common?rev=1153166400</link>
        <description># $EPIC: common.txt,v 1.2 2006/07/17 19:41:50 sthalik Exp $ 

$common(&lt;word list 1&gt; / &lt;word list 2&gt;)

	*  There must be a literal slash character (’/’) that separates the two word lists.  If it is omitted the empty string is returned.
	*  It is not required to have spaces on either side of the slash, but it also does not hurt to have them.
	*  The return value is a word list comprised of the set-intersection of &lt;word list 1&gt; and &lt;word list 2&gt;, that is to say:
	*  The return value is a word l…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/compile_opts?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>compile_opts</title>
        <link>http://www.epicsol.org/help/compile_opts?rev=1156876398</link>
        <description>EPIC supports numerous configuration options that may be selectively included or excluded from the client at compile time.  Since many of these enable or disable certain special features, it is useful to script writers to be able to find out what options are present while the client is running.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/connect?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>connect</title>
        <link>http://www.epicsol.org/help/connect?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the connect command or the connect function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/connect_command?rev=1153728000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T03:00:00+00:00</dc:date>
        <title>connect_command</title>
        <link>http://www.epicsol.org/help/connect_command?rev=1153728000</link>
        <description>connect &lt;new server&gt; [[&lt;port&gt;] &lt;existing server&gt;]

This command is used to connect servers to the irc network.  It must be given at least one argument, the name of a remote server to connect to the network.  If only one server is given, it is connected to the client’s server on the default port.  Alternately, a specific server and port may be specified.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/connect_function?rev=1153728000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T03:00:00+00:00</dc:date>
        <title>connect_function</title>
        <link>http://www.epicsol.org/help/connect_function?rev=1153728000</link>
        <description># $EPIC: connect_function.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

 $connect(&lt;host&gt; &lt;port&gt; [family])

	*  If the &lt;host&gt; argument is omitted the empty string is returned.
	*  If the &lt;port&gt; argument is omitted the empty string is returned.
	*  If the &lt;host&gt; argument does not resolve to a known Internet hostname, an error is output and the empty string is returned.
	*  If a TCP connection to host &lt;host&gt; on port &lt;port&gt; cannot be opened, an error is output and the empty string is returned.
	*  I…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/continue?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>continue</title>
        <link>http://www.epicsol.org/help/continue?rev=1152593863</link>
        <description>continue

Continue ends the current iteration of a do, while, foreach, fe, fec, for .. next, for .. in, and for (...) loop, just as if you had reached the end of the current  iteration normally.

The break and return commands are other ways of ending loops.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/convert?rev=1153728000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T03:00:00+00:00</dc:date>
        <title>convert</title>
        <link>http://www.epicsol.org/help/convert?rev=1153728000</link>
        <description># $EPIC: convert.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

$convert(&lt;ip address|hostname&gt;)

This function does a DNS lookup on the given address.  For an IP address, it attempts to find the corresponding Internet hostname.  For a hostname, it attempts to find the corresponding IP address.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/copattern?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>copattern</title>
        <link>http://www.epicsol.org/help/copattern?rev=1172803800</link>
        <description># $EPIC: copattern.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

$copattern(&lt;pattern&gt; &lt;var1&gt; &lt;var2&gt;)

	*  If the &lt;pattern&gt; argument is omitted the empty string is returned.
	*  If the &lt;var1&gt; argument is omitted the empty string is returned.
	*  If the &lt;var2&gt; argument is omitted the empty string is returned.
	*  &lt;pattern&gt; is taken to be a wildcard pattern
	*  &lt;var1&gt; and &lt;var2&gt; are taken to be lvals (names of ASSIGNs)
	*  &lt;var1&gt; and &lt;var2&gt; should each have the same number of words.
	*  For each se…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/copyright?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>copyright</title>
        <link>http://www.epicsol.org/help/copyright?rev=1152593863</link>
        <description>/*
 * Copyright (c) 1990 Michael Sandroff.
 * Copyright (c) 1991, 1992 Troy Rollo.
 * Copyright (c) 1992-1996 Matthew Green.
 * Copyright 1993, 1997 Jeremy Nelson.
 * Copyright 1994 Jake Khuon.
 * Copyright 1995, 1998 Jeremy Nelson and others (&quot;EPIC Software Labs&quot;).
 * All rights reserved.
 * 
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/corfilter?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>corfilter</title>
        <link>http://www.epicsol.org/help/corfilter?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/corpattern?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>corpattern</title>
        <link>http://www.epicsol.org/help/corpattern?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cos?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>cos</title>
        <link>http://www.epicsol.org/help/cos?rev=1153771200</link>
        <description># $EPIC: cos.txt,v 1.4 2006/07/24 19:50:14 sthalik Exp $ 

$cos(&lt;number&gt;)

	*  Returns the cosine of the angle of &lt;number&gt; radians.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cosh?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>cosh</title>
        <link>http://www.epicsol.org/help/cosh?rev=1153771200</link>
        <description># $EPIC: cosh.txt,v 1.3 2006/07/24 19:50:14 sthalik Exp $ 

$cosh(&lt;number&gt;)

	*  Returns the hyperbolic cosine of &lt;number&gt;.
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/count?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>count</title>
        <link>http://www.epicsol.org/help/count?rev=1172803800</link>
        <description># $EPIC: count.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

$count(&lt;string&gt; &lt;text&gt;)

This function counts how many times &lt;string&gt; appears in the text specified by &lt;text&gt;, possibly overlapping.

The uses for a function like this are unlimited.  One may be to count how many times a person’s nick appears in a public message, for logging purposes.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/country?rev=1153728000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T03:00:00+00:00</dc:date>
        <title>country</title>
        <link>http://www.epicsol.org/help/country?rev=1153728000</link>
        <description># $EPIC: country.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

load country

This script is used for converting between a country’s (official) name and its ISO country code.  It can convert in either direction, and can convert to a country name based on an email address.  Everything is done through a single alias, /country.  The basic syntax is:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/cparse?rev=1174842086">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-25T12:01:26+00:00</dc:date>
        <title>cparse</title>
        <link>http://www.epicsol.org/help/cparse?rev=1174842086</link>
        <description># $EPIC: cparse.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

$cparse(&lt;text&gt;) 
 $cparse(&lt;text&gt; &lt;arguments&gt;...)
 This function parses &lt;text&gt; according to the following table: Any instance of         will be replaced with ^C codes to change the
                         text to         text to         background to
 ---------------------------------------------------------------------
 %k      %K      %0      black           bold black      black
 %r      %R      %1      red             bold red   …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/crypt?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>crypt</title>
        <link>http://www.epicsol.org/help/crypt?rev=1172803800</link>
        <description># $EPIC: crypt.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$crypt(&lt;string&gt; &lt;salt&gt;)

Given an arbitrary string and a “salt” (a randomizer), this function returns the input string in a one-way encrypted form.  This function depends on the availability of a local crypt(3) library function.  Only the first 8 characters of the input string are significant.  The salt is a two-character string, and may be composed of any combination of any alphanumeric character, a period (.), or a forward-sl…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp?rev=1153728000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T03:00:00+00:00</dc:date>
        <title>ctcp</title>
        <link>http://www.epicsol.org/help/ctcp?rev=1153728000</link>
        <description>ctcp &lt;target&gt; &lt;command&gt; 
  ctcp &lt;target&gt; &lt;command&gt; &lt;arguments&gt;

CTCP is the Client To Client Protocol.  The purpose of CTCP is to send requests for information to other clients on the network, instead of the server.  CTCP messages are specially coded and the client to which you send a CTCP request will respond if it supports the request.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_action?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_action</title>
        <link>http://www.epicsol.org/help/ctcp_action?rev=1153771200</link>
        <description>CTCP &lt;target&gt; action &lt;action description&gt;

This is the command that implements the functionality of the DESCRIBE and ME commands.  This command should not be used directly.  Actions you send are caught with on send_action and are caught by the other person with on
action</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_clientinfo?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_clientinfo</title>
        <link>http://www.epicsol.org/help/ctcp_clientinfo?rev=1153771200</link>
        <description>ctcp &lt;target&gt; clientinfo &lt;ctcp command&gt;

This CTCP request roughly acts as a “help” command.  If you do not provide any arguments, the other person’s client will give you a list of which CTCP requests it supports.  If you give it an argument, the  other person’s client will give you information about its implementation of that CTCP request.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_echo?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_echo</title>
        <link>http://www.epicsol.org/help/ctcp_echo?rev=1153771200</link>
        <description>ctcp &lt;target&gt; echo &lt;any text&gt;

This CTCP request asks the other client to return your message back to you.  Tricks like this were formerly the way that PING times were measured.  Many clients do not support this request because attacks  by floodnets can disconnect you from your irc server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_finger?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_finger</title>
        <link>http://www.epicsol.org/help/ctcp_finger?rev=1153771200</link>
        <description>ctcp &lt;target&gt; finger

This CTCP request asks for more detailed information about the person you send it to.  The information returned is usually under the control of the other person and may or may not be useful.  Many clients do not support CTCP requests or severely throttle the rate at which they reply because floodnets make it easy to be knocked off of your IRC server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_ping?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_ping</title>
        <link>http://www.epicsol.org/help/ctcp_ping?rev=1153771200</link>
        <description>ctcp &lt;target&gt; ping &lt;current time&gt;

This command implements the underlying support for the PING command. It is not intended to be used directly.

# $EPIC: ctcp_ping.txt,v 1.3 2006/07/24 19:50:14 sthalik Exp $</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_time?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>ctcp_time</title>
        <link>http://www.epicsol.org/help/ctcp_time?rev=1156876398</link>
        <description>ctcp &lt;target&gt; time

This asks another client for its local time of day.  This differs from the TIME command, which queries the server instead of a client.  Not every client will return a reply for this request.

# $EPIC: ctcp_time.txt,v 1.5 2006/08/29 18:22:56 sthalik Exp $</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_userinfo?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_userinfo</title>
        <link>http://www.epicsol.org/help/ctcp_userinfo?rev=1153771200</link>
        <description>ctcp &lt;target&gt; userinfo

This asks another client to return whatever text it has stored in its USER_INFORMATION variable which can be just about anything. Not every client will return a reply for this request.

# $EPIC: ctcp_userinfo.txt,v 1.3 2006/07/24 19:50:14 sthalik Exp $</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_utc?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_utc</title>
        <link>http://www.epicsol.org/help/ctcp_utc?rev=1153771200</link>
        <description>ctcp &lt;target&gt; utc &lt;time value&gt;

This “inline” CTCP request includes a timestamp as the argument.  This timestamp is the number of seconds since the UNIX epoch, the same as is used by the PING command.  The receiver’s client will expand the timestamp to the receiver’s own locale-dependent time representation.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ctcp_version?rev=1153771200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T15:00:00+00:00</dc:date>
        <title>ctcp_version</title>
        <link>http://www.epicsol.org/help/ctcp_version?rev=1153771200</link>
        <description>ctcp &lt;target&gt; version

This command asks another client what irc client they are using, including the version information, if available.

Many users’ scripts or clients have been customized or modified to intercept CTCP VERSION requests and return falsified information.  You should not trust the value returned by this request unless you trust the person you queried.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/curcmd?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>curcmd</title>
        <link>http://www.epicsol.org/help/curcmd?rev=1171347600</link>
        <description># $EPIC: curcmd.txt,v 1.2 2007/02/13 06:05:45 jnelson Exp $ 

$curcmd()

When called while a ircii_syntax is running, this function returns the command being executed.  This is either a builtin command name, a user-created alias name, or an unknown command name.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/curpos?rev=1153728000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-24T03:00:00+00:00</dc:date>
        <title>curpos</title>
        <link>http://www.epicsol.org/help/curpos?rev=1153728000</link>
        <description># $EPIC: curpos.txt,v 1.2 2006/07/24 07:11:25 sthalik Exp $ 

$curpos()

	*  Arguments, if any, are ignored.
	*  This function returns the “index” of the cursor’s position in the “current” input line ($L).
	*  As with all “index” values, counting starts from zero.
	*  Counting begins after the input prompt, if any.
	*  The “current” input line is the last screen to receive a key-press. If you use this function outside of a key binding, this may be an important consideration.  U…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/currchans?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>currchans</title>
        <link>http://www.epicsol.org/help/currchans?rev=1152593863</link>
        <description># $EPIC: currchans.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$currchans([&lt;server refnum&gt;])

Returns the current channels for each window connected to &lt;server refnum&gt;. If &lt;server refnum&gt; is -1, then $lastserver() is assumed.

If no arguments are passed, all current channels are returned.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/data_array?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>data_array</title>
        <link>http://www.epicsol.org/help/data_array?rev=1152593863</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/data_struct?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>data_struct</title>
        <link>http://www.epicsol.org/help/data_struct?rev=1152593863</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dbmctl?rev=1179193800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-14T20:50:00+00:00</dc:date>
        <title>dbmctl</title>
        <link>http://www.epicsol.org/help/dbmctl?rev=1179193800</link>
        <description># $EPIC: dbmctl.txt,v 1.2 2006/10/06 02:07:37 jnelson Exp $ 

$dbmctl(OPEN type filename) 
 $dbmctl(OPEN_READ type filename) 
 $dbmctl(CLOSE refnum) 
 $dbmctl(ADD refnum “key” data) 
 $dbmctl(CHANGE refnum “key” data) 
 $dbmctl(DELETE refnum “key”) 
 $dbmctl(READ refnum “key”) 
 $dbmctl(NEXT_KEY refnum start-over) 
 $dbmctl(ALL_KEYS refnum) 
 $dbmctl(ERROR refnum)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc?rev=1170458926">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-02T17:28:46+00:00</dc:date>
        <title>dcc</title>
        <link>http://www.epicsol.org/help/dcc?rev=1170458926</link>
        <description># $EPIC: dcc.txt,v 1.3 2006/08/01 02:17:03 sthalik Exp $ 

dcc [&lt;command&gt; [&lt;arguments&gt;]]

DCC stands for Direct Client-to-Client connection.  The DCC  command manages all off these connections.  There are two primary uses for  DCC; chatting with other users without having to use the irc network; and file transfers.  These are examples; they are not the limit of DCC’s capabilities.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_chat?rev=1170458926">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-02T17:28:46+00:00</dc:date>
        <title>dcc_chat</title>
        <link>http://www.epicsol.org/help/dcc_chat?rev=1170458926</link>
        <description># $EPIC: dcc_chat.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

dcc chat &lt;nick&gt; [-p &lt;port&gt;]

DCC CHAT initiates a direct connection to another client, allowing you to talk to that person without the messages passing through the irc network. Because messages over DCC CHAT do not travel over a public irc network, they are more secure against snooping, and the messages will be much faster since they do not have to make many hops across irc servers to the destination. Netsplits, server changes, and …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_close?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>dcc_close</title>
        <link>http://www.epicsol.org/help/dcc_close?rev=1156876398</link>
        <description># $EPIC: dcc_close.txt,v 1.4 2006/08/29 18:22:56 sthalik Exp $ 

dcc close [&lt;type&gt;|-all|*] [&lt;nick&gt;|-all|*] [”&lt;filename&gt;”]

DCC CLOSE cancels a DCC session: 

	*  For DCC SEND, it rescinds the offer to send a file
	*  For DCC GET, it rejects our interest in receiving the file
	*  For DCC CHAT, it closes the dedicated chat connection
	*  For $connect(), it closes the raw client socket connection
	*  For $listen(), it closes the listening socket (but not any connections)
	*  For a file transfer…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_closeall?rev=1154398714">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:18:34+00:00</dc:date>
        <title>dcc_closeall</title>
        <link>http://www.epicsol.org/help/dcc_closeall?rev=1154398714</link>
        <description># $EPIC: dcc_closeall.txt,v 1.3 2006/08/01 02:17:03 sthalik Exp $ 

dcc closeall

This will close every open or pending DCC connection and send the necessary CTCP DCC REJECT replies to all peers.  Your DCC list will be quite empty after this command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_get?rev=1157025429">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T06:57:09+00:00</dc:date>
        <title>dcc_get</title>
        <link>http://www.epicsol.org/help/dcc_get?rev=1157025429</link>
        <description># $EPIC: dcc_get.txt,v 1.4 2006/08/31 11:57:06 sthalik Exp $ 

dcc get [=]&lt;nick&gt; &lt;file&gt; [file2] [file3] ... 
 dcc get [=]&lt;nick&gt; &lt;file&gt; [file2] [file3] ... /directory 
 dcc get [=]&lt;nick&gt; &lt;file&gt; &lt;not-offered-file&gt; 
 dcc get [=]&lt;nick&gt;

DCC GET opens a file transfer connection and downloads a file that someone else has offered you with the DCC SEND command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_list?rev=1153944000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:00+00:00</dc:date>
        <title>dcc_list</title>
        <link>http://www.epicsol.org/help/dcc_list?rev=1153944000</link>
        <description># $EPIC: dcc_list.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

dcc list

Whenever you need to take stock of your DCC connections, you can use the DCC LIST command to show you all active and pending DCC’s.  The  information shown includes the type of connection, whether the connection  is entropic, the nickname of the other person, the current status, the time that the connection was opened, the size of the file being  transfered (if any), the transfer throughput, and the name of the file bein…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_ports?rev=1179623955">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-19T20:19:15+00:00</dc:date>
        <title>dcc_ports</title>
        <link>http://www.epicsol.org/help/dcc_ports?rev=1179623955</link>
        <description># $EPIC: dcc_ports.txt,v 1.1 2007/05/20 01:19:15 jnelson Exp $ 

load dcc_ports 
 set dcc_port_first 1024 
 set dcc_port_last 65536

This script implements a dcc port range facility.  Each time you offer a dcc chat or dcc send to someone else, the next open port in the  port range will be used as though you had supplied the -p option to the dcc command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_raw?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>dcc_raw</title>
        <link>http://www.epicsol.org/help/dcc_raw?rev=1153944001</link>
        <description># $EPIC: dcc_raw.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

dcc raw &lt;fd&gt; &lt;host&gt; &lt;message&gt;

The DCC RAW command implements the underlying functionality for the MSG =&lt;fd&gt; &lt;message&gt; command.  You should prefer to use MSG instead because you do not then have to keep track of the hostname.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_rename?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>dcc_rename</title>
        <link>http://www.epicsol.org/help/dcc_rename?rev=1153944001</link>
        <description># $EPIC: dcc_rename.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

dcc rename [&lt;nick&gt;] &lt;name&gt; [&lt;new name&gt;] dcc rename -chat &lt;dcc-nick&gt; &lt;new nick&gt;

Sometimes someone will offer you a filename that you already have, and you want to get the file but not clobber your existing file.  With the /DCC RENAME command, you can change the name that this new file will be saved as, sparing your existing file from removal.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_resume?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>dcc_resume</title>
        <link>http://www.epicsol.org/help/dcc_resume?rev=1154400332</link>
        <description># $EPIC: dcc_resume.txt,v 1.6 2006/08/01 02:45:08 sthalik Exp $ 

dcc resume [=]&lt;nick&gt; &lt;file&gt;

If a previous DCC GET file transfer from another person did not complete successfully, you may be left with a partial file.  Normally, you would have to start over again, but if you are trying to get a very large file, you may not want to start over again.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dcc_send?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>dcc_send</title>
        <link>http://www.epicsol.org/help/dcc_send?rev=1153944001</link>
        <description># $EPIC: dcc_send.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

dcc send [=]&lt;nick&gt; [-p &lt;port&gt;] &lt;file&gt; [&lt;file&gt; ...] 

Sometimes you want to share a file with another person on irc.  The DCC SEND command sends an offer to share to another person. The remote client must of course open the connection before the file transfer will begin.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dccctl?rev=1179624000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-19T20:20:00+00:00</dc:date>
        <title>dccctl</title>
        <link>http://www.epicsol.org/help/dccctl?rev=1179624000</link>
        <description># $EPIC: dccctl.txt,v 1.6 2006/08/30 19:28:30 sthalik Exp $ 

$dccctl(REFNUMS) 
  $dccctl(TYPEMATCH [pattern]) 
  $dccctl(DESCMATCH [pattern]) 
  $dccctl(FILEMATCH [pattern]) 
  $dccctl(USERMATCH [pattern]) 
  $dccctl(OTHERMATCH [pattern]) 
  $dccctl(LOCKED [pattern]) 
  $dccctl(REFBASE [number]) 
  $dccctl(HELD) 
  $dccctl(UNHELD) 
  $dccctl(WRITABLES) 
  $dccctl(USERHOSTMATCH [userhost]) 
  $dccctl(GET &lt;refnum&gt; &lt;item&gt;) 
  $dccctl(SET &lt;refnum&gt; &lt;item&gt; &lt;value&gt;)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/debug.irc?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>debug.irc</title>
        <link>http://www.epicsol.org/help/debug.irc?rev=1153944001</link>
        <description># $EPIC: debug.irc.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

load debug.irc 
 debug_section 
 debug_endsection

This script provides an example of how to effectively debug sections of code in large scripts, or while other scripts are loaded. It consists of two aliases, which are inserted into the code to be debugged to turn debugging on/off where needed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/debugging?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>debugging</title>
        <link>http://www.epicsol.org/help/debugging?rev=1156876398</link>
        <description>Several tools exist in the client which can aid in debugging and testing scripts. 

	*  /set debug 
 Allows the client to show which commands are actually being executed, how they are being parsed, and what alias and variable substitutions are taking effect.
	*  /pretend 
 Causes the client to “pretend” it received a given line of text from the server. Use with caution.
	*  /shook 
 Causes a given hook to be triggered as if the event had actually occurred.
	*  /xdebug inbound (not officially…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/decode?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>decode</title>
        <link>http://www.epicsol.org/help/decode?rev=1153944001</link>
        <description># $EPIC: decode.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

$decode(&lt;text&gt;)

	*  If the &lt;text&gt; argument is omitted the empty string is returned.
	*  The &lt;text&gt; argument must be text that was previously returned by the $encode() function.  All other inputs will yield undefined results.
	*  This function returns the original &lt;text&gt; that was passed to the $encode() function.
	*  Hardcoding $encode()d values into your script IS A BAD THING.  Please be aware that $encode() may change in the future …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/defer?rev=1154398714">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:18:34+00:00</dc:date>
        <title>defer</title>
        <link>http://www.epicsol.org/help/defer?rev=1154398714</link>
        <description># $EPIC: defer.txt,v 1.3 2006/08/01 02:17:03 sthalik Exp $ 

defer {&lt;stuff&gt;}

The DEFER command schedules &lt;stuff&gt; to be executed later on when the client is idle, and there is no risk that if &lt;stuff&gt; were to destroy something that it would crash the client.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/delarray?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>delarray</title>
        <link>http://www.epicsol.org/help/delarray?rev=1153944001</link>
        <description># $EPIC: delarray.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

$delarray(&lt;array&gt;)

This function removes all items in an array created with $setitem(), having the effect of deleting the array.

This function deletes an array.  Generally this is most useful when cleaning up after a script.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/delitem?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>delitem</title>
        <link>http://www.epicsol.org/help/delitem?rev=1153944001</link>
        <description># $EPIC: delitem.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

$delitem(&lt;array&gt; &lt;item#&gt;)

This function is used to delete an entry from an array created with $setitem().  If the item deleted is the only one present in the array, the array is deleted too.  If the item is not the last item in the array, all items beyond it (with higher item numbers) are shifted down by one to fill in the gap.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/delitems?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>delitems</title>
        <link>http://www.epicsol.org/help/delitems?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/deop?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>deop</title>
        <link>http://www.epicsol.org/help/deop?rev=1153944001</link>
        <description>deop

This command is used by an irc operator to remove his or her operator status.  In short it gets the user’s current nickname from the server  and then uses MODE to remove oper status. That’s it.

DEOP has the same effect as setting user mode -o with MODE.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/describe?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>describe</title>
        <link>http://www.epicsol.org/help/describe?rev=1153944001</link>
        <description># $EPIC: describe.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

describe &lt;nickname|channel&gt; &lt;action description&gt;

DESCRIBE lets you perform an action.  It lets you describe what you’re doing as though someone is watching you, rather than you telling them. You may send an action to either an individual or to an entire channel.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/deuhc?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>deuhc</title>
        <link>http://www.epicsol.org/help/deuhc?rev=1153944001</link>
        <description># $EPIC: deuhc.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

$deuhc(&lt;user@host&gt;)

This function removes a *! or *!*@ from the &lt;user@host&gt;, if it is present.

It can be used as a quick way to get only the hostname from a full address argument.

arguments without *! or *!*@ in front</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/die?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>die</title>
        <link>http://www.epicsol.org/help/die?rev=1152593863</link>
        <description>die

DIE causes the operator’s server to do just that; die.  The process terminates normally.

This command is limited to irc operators.  Additionally, it may not be available even to them, depending on how the server was compiled.  The server must #define either OPER_DIE or LOCAL_DIE (or both) for someone to be able to use it at all.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/diff?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>diff</title>
        <link>http://www.epicsol.org/help/diff?rev=1153944001</link>
        <description># $EPIC: diff.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

$diff(&lt;word list 1&gt; / &lt;word list 2&gt;)

	*  There must be a literal slash character (’/’) that separates the two word lists.  If it is omitted the empty string is returned.
	*  It is not required to have spaces on either side of the slash, but it also does not hurt to have them.
	*  The return value is a word list comprised of the negated set-difference of &lt;word list 1&gt; and &lt;word list 2&gt;, that is to say:
	*  The return value is a word…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/disambiguation?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>disambiguation</title>
        <link>http://www.epicsol.org/help/disambiguation?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the log command or the log function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/disconnect?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>disconnect</title>
        <link>http://www.epicsol.org/help/disconnect?rev=1171347600</link>
        <description># $EPIC: disconnect.txt,v 1.4 2006/09/19 10:52:37 sthalik Exp $ 

disconnect [&lt;server number&gt; [&lt;reason&gt;]]

The disconnect command disconnects you from an irc server but does not make the client quit.  If you are on multiple servers, only the one server will be disconnected and the others are unaffected.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/do?rev=1153944001">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-26T15:00:01+00:00</dc:date>
        <title>do</title>
        <link>http://www.epicsol.org/help/do?rev=1153944001</link>
        <description>#$EPIC: do.txt,v 1.2 2006/07/26 19:47:17 sthalik Exp $ 

do &lt;commands&gt; 
 do { &lt;commands&gt; } [while (&lt;condition&gt;)]

DO has two uses.  In its first use it is a synonym for EVAL, but it’s a bad idea to use EVAL either.

Its second use is a post-test loop.  You are obliged to put your commands in curly braces and after the closing curly brace a WHILE expression.   DO .. WHILE loops always execute at least once.  You must be careful to put the WHILE expression on the same line as the closing brace. …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/dump?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>dump</title>
        <link>http://www.epicsol.org/help/dump?rev=1152593863</link>
        <description>#$EPIC: dump.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

dump [all|alias|var|on]

This mass-deletes all of your aliases, assigns (variables) and/or ons. This can be useful if a script is trying to reload and wants to know that there is nothing else that will interfere with it, without having to restart epic.  It can also be used to completely wipe away all of the scripts that epic loads by default when you start up.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/echo?rev=1154399286">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:28:06+00:00</dc:date>
        <title>echo</title>
        <link>http://www.epicsol.org/help/echo?rev=1154399286</link>
        <description>echo [&lt;anything&gt;]

This command prints its arguments back to the screen.  That’s it.  It is useful for printing status messages from inside scripts, or inside hooks for redefining server messages.

The ECHO command is also the only command (one of two, actually; see XECHO) that can write to the screen when set DISPLAY is off. ECHO now has no length limitation, it can display any string within the confines of memory.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/edit_topic?rev=1171945200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T22:20:00+00:00</dc:date>
        <title>edit_topic</title>
        <link>http://www.epicsol.org/help/edit_topic?rev=1171945200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/encode?rev=1154399286">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:28:06+00:00</dc:date>
        <title>encode</title>
        <link>http://www.epicsol.org/help/encode?rev=1154399286</link>
        <description># $EPIC: encode.txt,v 1.2 2006/08/01 02:24:39 sthalik Exp $ 

$encode(&lt;text&gt;)

	*  If the &lt;text&gt; argument is omitted the empty string is returned.
	*  The output of this function is a transformation of &lt;text&gt; that has the following characteristics AND ONLY the following characteristics:
	*  It is unique      encode(X) != encode(Y) for all X != Y
	*  It is case sensitive: 
 encode(foo) != encode(FOO)
	*  It is reversable: 
 decode($encode(foo)) == [foo]
	*  It can be assigned to: 
 @ encode(foo) …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/encrypt?rev=1157031213">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T08:33:33+00:00</dc:date>
        <title>encrypt</title>
        <link>http://www.epicsol.org/help/encrypt?rev=1157031213</link>
        <description># $EPIC: encrypt.txt,v 1.3 2006/08/31 13:33:30 sthalik Exp $ 

encrypt 
 encrypt [server]/&lt;channel&gt; [-&lt;cipher&gt;] &lt;key&gt; [&lt;program&gt;] 
 encrypt [server]/&lt;channel,sourcenick!user@host&gt; [-&lt;cipher&gt;] &lt;key&gt; [&lt;program&gt;]

This allows you to maintain an encrypted conversation with a person or channel.  Any messages you send to the specified target will automatically be encrypted.  If the recipient has likewise specified the proper encryption key for you, the incoming message will automatically be decrypted.…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/encryptparm?rev=1172121600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-21T23:20:00+00:00</dc:date>
        <title>encryptparm</title>
        <link>http://www.epicsol.org/help/encryptparm?rev=1172121600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/environment_variables?rev=1154399286">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:28:06+00:00</dc:date>
        <title>environment_variables</title>
        <link>http://www.epicsol.org/help/environment_variables?rev=1154399286</link>
        <description>Numerous environment variables are recognized by .  Environment variables are various settings that describe your login process on a Unix system.  How they are set mainly depends on the command shell you use. 

	*  For csh and tcsh shells: 
 setenv variable “value”</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/eof?rev=1154399286">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:28:06+00:00</dc:date>
        <title>eof</title>
        <link>http://www.epicsol.org/help/eof?rev=1154399286</link>
        <description># $EPIC: eof.txt,v 1.2 2006/08/01 02:24:39 sthalik Exp $ 

$eof(&lt;file descriptor&gt;)

This function tests whether the client is currently at the end of the file pointed to by the given file descriptor.  The only valid input is a file descriptor returned by the $open() function.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/epic-crypt-gpg-aa?rev=1172120849">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-21T23:07:29+00:00</dc:date>
        <title>epic-crypt-gpg-aa</title>
        <link>http://www.epicsol.org/help/epic-crypt-gpg-aa?rev=1172120849</link>
        <description># $EPIC: epic-crypt-gpg-aa.txt,v 1.1 2007/02/22 05:07:29 jnelson Exp $



This is a (bash) shell script that can be used as an external program with the client’s external encryption program support.  Both the sender and receiver must be encrypting with each other using this script as the external cipher program.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/epic-crypt-gpg?rev=1172120849">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-21T23:07:29+00:00</dc:date>
        <title>epic-crypt-gpg</title>
        <link>http://www.epicsol.org/help/epic-crypt-gpg?rev=1172120849</link>
        <description># $EPIC: epic-crypt-gpg.txt,v 1.1 2007/02/22 05:07:29 jnelson Exp $



This is a (bash) shell script that can be used as an external program with the client’s external encryption program support.  Both the sender and receiver must be encrypting with each other using this script as the external cipher program.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/epic?rev=1154399286">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:28:06+00:00</dc:date>
        <title>epic</title>
        <link>http://www.epicsol.org/help/epic?rev=1154399286</link>
        <description># $EPIC: epic.txt,v 1.2 2006/08/01 02:24:39 sthalik Exp $ 

$epic()

Returns true if the client is an EPIC client.

If this function returns true, the client is an EPIC3 client, or some variant of it.  The $V and $J expandos will tell you the exact version of the client.  This function is necessary because the stock ircII client’s value for $V and EPIC’s overlap.  This is mostly a useful way for scripts to see if they can load or not.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/etiquette?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>etiquette</title>
        <link>http://www.epicsol.org/help/etiquette?rev=1152593863</link>
        <description>Original Authors Lea Viljanen  (LadyBug)  &lt;viljanen@kreeta.helsinki.fi&gt;             Ari Husa      (luru)     &lt;so-luru@tolsun.oulu.fi&gt;                  Modified By Troy Rollo    (Troy)     &lt;troy@plod.cbme.unsw.oz.au&gt;                Further Modified By James Sneeringer    (CrowMan)   &lt;jvs@ocslink.com&gt;            
1) Language</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/eval?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>eval</title>
        <link>http://www.epicsol.org/help/eval?rev=1171347600</link>
        <description>eval &lt;block&gt;

Eval accepts a &lt;block&gt; of code and executes it.  Generally the only place you need to use eval is at the input prompt.  The commands you run at the input prompt are different from commands you run in your script:  at the input prompt, command arguments are taken as a literal string, whereas in your scripts, command arguments are expanded and dequoted before the command is  executed.  The eval command permits you to run a command at the input  prompt as though it were running in a s…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/exec?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>exec</title>
        <link>http://www.epicsol.org/help/exec?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the exec command or the exec function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/exec_command?rev=1156972800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-30T16:20:00+00:00</dc:date>
        <title>exec_command</title>
        <link>http://www.epicsol.org/help/exec_command?rev=1156972800</link>
        <description># $EPIC: exec_command.txt,v 1.3 2006/08/30 21:02:47 sthalik Exp $ 

exec [&lt;options&gt;] [&lt;shell commands&gt;] 
 exec -direct &lt;commands&gt; 
 exec -name &lt;name&gt; &lt;process id|shell commands&gt; 
 exec -out &lt;process id|shell commands&gt; 
 exec -msg &lt;nickname|channel&gt; &lt;process id|shell commands&gt; 
 exec -notice &lt;nickname|channel&gt; &lt;process id|shell commands&gt; 
 exec -in &lt;process id&gt; &lt;text to send to process&gt; 
 exec -window &lt;process id|shell commands&gt; 
 exec -&lt;signal&gt; &lt;process id&gt; 
 exec -close &lt;process id&gt; 
 exec -clo…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/exec_function?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>exec_function</title>
        <link>http://www.epicsol.org/help/exec_function?rev=1156876398</link>
        <description># $EPIC: exec_function.txt,v 1.4 2006/08/29 18:22:56 sthalik Exp $ 

$exec(&lt;program&gt; &lt;args&gt;)

	*  If the &lt;program&gt; argument is ommited, the empty string is returned.
	*  Otherwise, &lt;program&gt; is forked and executed with &lt;args&gt; for arguments.
	*  This function returns 3 (three) FDs, which are pipes to/from STDIN, STDOUT and STDERR of the forked process respectively.
	*  The first FD returned (STDIN) is a write mode FD.
	*  The subsequent FDs (STDOUT and STDERR) are read mode FDs.
	*  The FDs retur…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/exit?rev=1153108800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T23:00:00+00:00</dc:date>
        <title>exit</title>
        <link>http://www.epicsol.org/help/exit?rev=1153108800</link>
        <description># $EPIC: exit.txt,v 1.2 2006/07/17 03:42:24 jnelson Exp $ 

exit &lt;reason&gt;

The exit command is an internal alias for quit.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/exp?rev=1153108800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T23:00:00+00:00</dc:date>
        <title>exp</title>
        <link>http://www.epicsol.org/help/exp?rev=1153108800</link>
        <description># $EPIC: exp.txt,v 1.2 2006/07/17 03:42:24 jnelson Exp $ 

$exp(&lt;number&gt;) 

* The function returns the value of e raised to &lt;number&gt;. * If &lt;number&gt; is omitted, the empty string is returned. * As always, the return value is limited to 6 decimal places. * As always, DOM or RANGE means an error ocurred.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/expando_substitution?rev=1186435564">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-06T16:26:04+00:00</dc:date>
        <title>expando_substitution</title>
        <link>http://www.epicsol.org/help/expando_substitution?rev=1186435564</link>
        <description>Before a string can be used, it must be “expanded” whereby the expandos (things that start with $) in the string are removed and replaced with their values,  and backslashes (\\) are dequoted.  However, stuff inside of parenthesis  “(...)” or curly braces “{...}” is considered literal text and is not  expanded.  The stuff inside parenthesis and curly braces is usually expanded later by someone else.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/expandos?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>expandos</title>
        <link>http://www.epicsol.org/help/expandos?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/expressions?rev=1192295231">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-13T12:07:11+00:00</dc:date>
        <title>expressions</title>
        <link>http://www.epicsol.org/help/expressions?rev=1192295231</link>
        <description>About &quot;expression mode&quot; and &quot;text mode&quot;

EPIC has two “modes” it executes your code in.  “Text mode” is the standard mode that every command starts out in. 
 Text mode				    Expression mode  Everything is plain text		     Everything is operator or operand First word is command, rest is arg list    Can escape to text mode with []s $’s start “expandos” (macro substitution)  $’s are not permitted before vars
 “Expression mode” occurs in all of the following text-mode commands: …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fe?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>fe</title>
        <link>http://www.epicsol.org/help/fe?rev=1184106000</link>
        <description>fe (&lt;list&gt;) &lt;variable&gt; [&lt;variable&gt; ...] { &lt;actions&gt; } 
 fe &lt;source_variable&gt; &lt;variable&gt; [&lt;variable&gt; ...] { &lt;actions&gt; }

Form 1:

FE is one of several loop types available in ircII-EPIC.  This loop takes a list of items, and for each one, it performs the specified action.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fec?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>fec</title>
        <link>http://www.epicsol.org/help/fec?rev=1154400332</link>
        <description>fec (&lt;string&gt;) &lt;variable&gt; [&lt;variable&gt; ...] { &lt;actions&gt; } 
 fec &lt;source_variable&gt; &lt;variable&gt; [&lt;variable&gt; ...] { &lt;actions&gt; }

The fec command works in the same way as fe, except that it iterates over each character rather than each word.

Leading whitespace between the opening parenthesis and first non-whitespace character and trailing whitespace between the final non-whitespace character and the closing parenthesis is ignored.  This is probably not the ideal behavior, but it is backwards compatab…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ferror?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>ferror</title>
        <link>http://www.epicsol.org/help/ferror?rev=1160162400</link>
        <description># $EPIC: ferror.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$ferror(&lt;file descriptor&gt;)

This function returns non-zero if an error has occurred on the  file descriptor since the last read, because the read and readb functions clear the file descriptors error code.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fexist?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>fexist</title>
        <link>http://www.epicsol.org/help/fexist?rev=1172803800</link>
        <description># $EPIC: fexist.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$fexist(&lt;file&gt;) 
  $fexist(&quot;&quot; &lt;file&gt;)

	*  In the first case, &lt;file&gt; is a single extended word (you may surround it with double quotes if it contains spaces).  Any further arguments are ignored.
	*  In the second case, the first argument is an empty string, and the rest of the arguments are taken as a filename literally.  Do not backslash or double quote anything in &lt;file&gt;.
	*  Tile-expansion is supported in both forms.
	*  If &lt;file&gt; …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/files?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>files</title>
        <link>http://www.epicsol.org/help/files?rev=1154400332</link>
        <description># $EPIC: files.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

load files

This script is meant as a working example of the possible uses of EPIC’s various built-in file-access functions.  Three aliases are provided: 
  Alias       Description                                                /cat     like the Unix command, it displays the named file               /grep    like the Unix command, it searches for pattern $0 in files $1-  /log_it  writes an arbitrary line to file $0                   …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/filter?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>filter</title>
        <link>http://www.epicsol.org/help/filter?rev=1154400332</link>
        <description># $EPIC: filter.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$filter(&lt;pattern&gt; &lt;word list&gt;)

	*  If the &lt;pattern&gt; argument is omitted the empty string is returned.
	*  This function returns a space separated word list of all of the words in &lt;word list&gt; that are NOT matched by &lt;pattern&gt;.
	*  This is the complement to $pattern(), and the inverse of $rfilter().
	*  Double quoted words are honored, but the double quotes will be lost in the return value.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/finditem?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>finditem</title>
        <link>http://www.epicsol.org/help/finditem?rev=1172553600</link>
        <description># $EPIC: finditem.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$finditem(&lt;array&gt; &lt;string&gt;) 
  $ifinditem(&lt;array&gt; &lt;string&gt;) 
  $ifindfirst(&lt;array&gt; &lt;string&gt;)

These functions do a binary search on the items stored in the given array, looking for an exact match of the input string.  It will only return the results of an exact match.  Unlike other string handlers in the client, these are case-sensitive.  They only operate on arrays created with the $setitem() function.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/finditems?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>finditems</title>
        <link>http://www.epicsol.org/help/finditems?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/findw?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>findw</title>
        <link>http://www.epicsol.org/help/findw?rev=1154400332</link>
        <description># $EPIC: findw.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$findw(&lt;word&gt; &lt;wordlist&gt;)

This function searches &lt;wordlist&gt; for &lt;word&gt; and returns the place it was found. If &lt;word&gt; isn’t in &lt;wordlist&gt;, -1 is returned.

This function should put many scripters to ease, as it has been written into many scripts :)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/findws?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>findws</title>
        <link>http://www.epicsol.org/help/findws?rev=1171513201</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fix_arglist?rev=1172341200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-24T12:20:00+00:00</dc:date>
        <title>fix_arglist</title>
        <link>http://www.epicsol.org/help/fix_arglist?rev=1172341200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/flood_control?rev=1172802724">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:32:04+00:00</dc:date>
        <title>flood_control</title>
        <link>http://www.epicsol.org/help/flood_control?rev=1172802724</link>
        <description>$EPIC: flood_control.txt,v 1.1 2007/03/02 02:32:04 jnelson Exp $ 

The client has an anti-flood facility whose purpose is to prevent crapflooding to your display.  Since flood control is a client-side  facility, it can’t stop someone from consuming all your cpu or bandwidth.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/floodinfo?rev=1172947800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:50:00+00:00</dc:date>
        <title>floodinfo</title>
        <link>http://www.epicsol.org/help/floodinfo?rev=1172947800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/floodprot?rev=1172685000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-28T11:50:00+00:00</dc:date>
        <title>floodprot</title>
        <link>http://www.epicsol.org/help/floodprot?rev=1172685000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/floor?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>floor</title>
        <link>http://www.epicsol.org/help/floor?rev=1154400332</link>
        <description># $EPIC: floor.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$floor(&lt;number&gt;)

Calculates the largest integer that is less than or equal to &lt;number&gt;

The largest integer that is less than or equal to the argument, or nothing if no argument is specified.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/flush?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>flush</title>
        <link>http://www.epicsol.org/help/flush?rev=1154400332</link>
        <description>flush

This command effectively does a /REDIRECT 0 WAIT.  In other words, it suppresses all output to all of your windows from your current server for one full “WAIT” cycle (the time it takes for a command to go out to the server and come back)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fnexist?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>fnexist</title>
        <link>http://www.epicsol.org/help/fnexist?rev=1154400332</link>
        <description># $EPIC: fnexist.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$fnexist(&lt;function&gt;)

This function tells wether or not a built-in function exists.

This can be used to emulate a built-in function in older versions of epic that may not support it.


1   If the built-in function &lt;function&gt; exists
0   If &lt;function&gt; doesn't exist</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/for?rev=1154401155">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:59:15+00:00</dc:date>
        <title>for</title>
        <link>http://www.epicsol.org/help/for?rev=1154401155</link>
        <description>for (once, expression, each) { block } 
  for var from firstval to lastval { block } 
 for var from firstval to lastval step stepval { block } 
 for var in (word list) { block }

FOR is a general purpose loop.  It is modeled on the C for statement, and works in a very similar manner.  Aside from the action, there are three parts to a FOR loop:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/foreach?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>foreach</title>
        <link>http://www.epicsol.org/help/foreach?rev=1154400332</link>
        <description>foreach [-]&lt;structure&gt; &lt;variable&gt; { &lt;action&gt; }

The FOREACH command is a loop type that iterates through the items in a variable (or alias, see below) structure.  This is often useful for purging an entire structure, or for searching through it for a certain piece of data.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/frewind?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>frewind</title>
        <link>http://www.epicsol.org/help/frewind?rev=1160162400</link>
        <description># $EPIC: frewind.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$frewind(&lt;file descriptor&gt;)

This function resets the file pointer back to the beginning of the file.   The next read or readb in the file after this call will read the  first line of the file.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fromw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>fromw</title>
        <link>http://www.epicsol.org/help/fromw?rev=1172803800</link>
        <description># $EPIC: fromw.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$fromw(&lt;word&gt; &lt;word list&gt;)

	*  If the &lt;word&gt; argument is omitted this function returns the empty string.
	*  The &lt;word list&gt; is a list of literal words.  Before EPIC4-1.1.10, the &lt;word list&gt; was a list of wildcard patterns.
	*  If &lt;word&gt; is not found in &lt;word list&gt;, this function returns the empty string.
	*  Otherwise, the function behaves “as if” the following had been
	*  performed: 
 &lt;val&gt; = findw(&lt;word&gt; &lt;word list&gt;) 
 &lt;functi…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fseek?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>fseek</title>
        <link>http://www.epicsol.org/help/fseek?rev=1160162400</link>
        <description># $EPIC: fseek.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$fseek(file descriptor position anchor)

This function resets the file pointer to position bytes away from  anchor.  The next read or readb of the file after this call will read the data from the new location.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fsize?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>fsize</title>
        <link>http://www.epicsol.org/help/fsize?rev=1172803800</link>
        <description># $EPIC: fsize.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$fsize(&lt;file&gt;) $fsize(”” &lt;file&gt;)

	*  In the first case, &lt;file&gt; is a single extended word (you may surround it with double quotes if it contains spaces).  Any further arguments are ignored.
	*  In the second case, the first argument is an empty string, and the rest of the arguments are taken as a filename literally.  Do not backslash or double quote anything in &lt;file&gt;.
	*  Tile-expansion is supported in both forms.
	*  If &lt;file&gt; ex…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/fskip?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>fskip</title>
        <link>http://www.epicsol.org/help/fskip?rev=1160162400</link>
        <description># $EPIC: fskip.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$fskip(file descriptor number)

The fskip function skips the next number lines in the file. The return value is the number of lines that were actually skipped. If you try to skip more lines than are left in the file (end of file), the return value will be less than number.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ftell?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>ftell</title>
        <link>http://www.epicsol.org/help/ftell?rev=1160162400</link>
        <description># $EPIC: ftell.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$ftell(file descriptor)

This function returns the current position of the file pointer, measured in bytes from the beginning of the file.  This value can be used to save your position in the file, and you can later use</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ftime?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>ftime</title>
        <link>http://www.epicsol.org/help/ftime?rev=1172803800</link>
        <description># $EPIC: ftime.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

$ftime(&lt;file&gt;)

This function gets the last modified time (mtime) of a file, and returns it in seconds since the epoch.

when the file was last modified


eval echo $stime($ftime(/usr/local/bin/irc))

&quot;Tue Oct 21 23:30:54 1997&quot;</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ftruncate?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>ftruncate</title>
        <link>http://www.epicsol.org/help/ftruncate?rev=1160162400</link>
        <description># $EPIC: ftruncate.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

$ftruncate(bytes filename)

The ftruncate file causes the filename to change to exactly bytes bytes in size.  The file is grown or shrunk as necessary.  If the file is shrunk, the data beyond the new file size is irretrievably lost.  If the file is grown, the contents of the new space is unspecified, but usually it is  nuls (ascii 0).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/functioncall?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>functioncall</title>
        <link>http://www.epicsol.org/help/functioncall?rev=1156876398</link>
        <description># $EPIC: functioncall.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$functioncall()

	*  This function returns 1 if the current script context is expecting a return value (ie, in an alias called as a function and not as a command.)
	*  This function returns 0 in all other circumstances, including but not limited to aliases executed as commands, /on bodies, /userhost -cmd bodies, and any other place where a return value is not expected.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/functions_overview?rev=1157605729">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-07T00:08:49+00:00</dc:date>
        <title>functions_overview</title>
        <link>http://www.epicsol.org/help/functions_overview?rev=1157605729</link>
        <description>EPIC functions are very similar to those of common procedural languages - they have arguments and they return a value. There are many different kinds of functions - ones that manipulate strings, ones that retrieve information from the client, ones that perform math operations et cetera.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/functions_script?rev=1154400332">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T21:45:32+00:00</dc:date>
        <title>functions_script</title>
        <link>http://www.epicsol.org/help/functions_script?rev=1154400332</link>
        <description># $EPIC: functions_script.txt,v 1.2 2006/08/01 02:45:08 sthalik Exp $ 

load functions

This script contains several functions useful in scripting for text display.  Of primary interest are $format() and $lformat().  They behave similarly to using the $[]var notation, except they will not truncate text that is wider than the specified width.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/geom?rev=1154402813">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:26:53+00:00</dc:date>
        <title>geom</title>
        <link>http://www.epicsol.org/help/geom?rev=1154402813</link>
        <description># $EPIC: geom.txt,v 1.3 2006/08/01 03:26:48 sthalik Exp $ 

$geom() 
  $geom(&lt;winref&gt;)

	*  In the first case, the screen of the client’s global current window is used.
	*  In the second case, the screen of the given window refnum is used.
	*  In both cases, the return value is two numbers, the first is the number of columns and the second is the number of lines on the screen.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getarrays?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getarrays</title>
        <link>http://www.epicsol.org/help/getarrays?rev=1154402550</link>
        <description># $EPIC: getarrays.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getarrays()

This function displays all existing arrays created by $setitem().

This function is used to show all current arrays.  his might be useful for modifying data in multiple arrays, when it is not known precisely which ones exist at the moment in question.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getcap?rev=1166008063">
        <dc:format>text/html</dc:format>
        <dc:date>2006-12-13T05:07:43+00:00</dc:date>
        <title>getcap</title>
        <link>http://www.epicsol.org/help/getcap?rev=1166008063</link>
        <description># $EPIC: getcap.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getcap(TERM &lt;capname&gt; &lt;nametype&gt; &lt;mangle&gt;)

	*  The first argument must be a capability type; currently only “TERM” is supported.
	*  If the &lt;capname&gt; argument is omitted, the empty string is returned.
	*  If the &lt;nametype&gt; argument is omitted, the name type is taken as 0.
	*  If the &lt;mangle&gt; argument is omitted, the mangle value is taken as 1.
	*  This function queries a capability database (currently only TERMinal capabilities …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getcommands?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getcommands</title>
        <link>http://www.epicsol.org/help/getcommands?rev=1154402550</link>
        <description># $EPIC: getcommands.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getcommands() 
  $getcommands(&lt;pattern&gt;)

	*  If no argument is given, the return value is a word list of all built in commands.
	*  If an argument is given, the return value is a word list of all built in commands that match the given pattern.
	*  Multiple patterns may be specified; the result is a concatenated list of return values as if each pattern had been processed individually. Specifically, any duplicates will NOT be rem…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getenv?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getenv</title>
        <link>http://www.epicsol.org/help/getenv?rev=1154402550</link>
        <description># $EPIC: getenv.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getenv(&lt;variable&gt;)

This function returns the &lt;variable&gt; from the shell’s environment.

This function is especially useful when a /set or /assign variable conflicts with an environment variable.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getfunctions?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>getfunctions</title>
        <link>http://www.epicsol.org/help/getfunctions?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getgid?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getgid</title>
        <link>http://www.epicsol.org/help/getgid?rev=1154402550</link>
        <description># $EPIC: getgid.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getgid()

Gets the current group id, similar to the Unix system call.

current groupid</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getitem?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getitem</title>
        <link>http://www.epicsol.org/help/getitem?rev=1154402550</link>
        <description># $EPIC: getitem.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getitem(&lt;array&gt; &lt;item#&gt;) 
  $igetitem(&lt;array&gt; &lt;index#&gt;)

These functions are used to fetch data held in the given array.

The $getitem() function retrieves data based on its item number in the array (counting from zero, the order in which the data was entered).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getlogin?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getlogin</title>
        <link>http://www.epicsol.org/help/getlogin?rev=1154402550</link>
        <description># $EPIC: getlogin.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getlogin()

Gets the name of the current logged in user, similar to the Unix system call.

current logged in username</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getmatches?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>getmatches</title>
        <link>http://www.epicsol.org/help/getmatches?rev=1172553600</link>
        <description># $EPIC: getmatches.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getmatches(&lt;array&gt; &lt;pattern&gt;) 
  $getrmatches(&lt;array&gt; &lt;string&gt;)

This functions operate in a manner similar to $matchitem() and $rmatchitem(), except that they return a list of all items that match the input pattern or string, not just the best match.  Item numbers are returned, not the actual array contents.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getopt?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>getopt</title>
        <link>http://www.epicsol.org/help/getopt?rev=1172803800</link>
        <description># $EPIC: getopt.txt,v 1.3 2006/08/01 03:26:48 sthalik Exp $ 

$getopt(&lt;optopt-var&gt; &lt;optarg-var&gt; &lt;option-list&gt; &lt;argument-list&gt;)

	*  This function should be called as the expression of a WHILE command.
	*  If the &lt;optopt-var&gt; argument is omitted the empty string is returned.
	*  If the &lt;optarg-var&gt; argument is omitted the empty string is returned.
	*  If the &lt;option-list&gt; argument is omitted the empty string is returned.
	*  The &lt;optopt-var&gt; argument is taken as the name of a variable in which to…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getpgrp?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getpgrp</title>
        <link>http://www.epicsol.org/help/getpgrp?rev=1154402550</link>
        <description># $EPIC: getpgrp.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getpgrp()

Gets the current process group id of the client, similar to the Unix system call.

current process group id</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getrmatches?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>getrmatches</title>
        <link>http://www.epicsol.org/help/getrmatches?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getserial?rev=1171855258">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-18T21:20:58+00:00</dc:date>
        <title>getserial</title>
        <link>http://www.epicsol.org/help/getserial?rev=1171855258</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getset?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>getset</title>
        <link>http://www.epicsol.org/help/getset?rev=1152593863</link>
        <description># $EPIC: getset.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$getset(&lt;set name&gt;)

	*  If the &lt;set name&gt; argument is omitted the empty string is returned.
	*  If the set variable &lt;set name&gt; does not exist, the empty string is returned.
	*  This function returns the value that would be returned by the “set value” $&lt;set name&gt;.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getsets?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getsets</title>
        <link>http://www.epicsol.org/help/getsets?rev=1154402550</link>
        <description># $EPIC: getsets.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getsets() $getsets(&lt;pattern&gt;)

	*  If no argument is given, the return value is a word list of all built in set variables.
	*  If an argument is given, the return value is a word list of all built in set variables that match the given pattern.
	*  Multiple patterns may be specified; the result is a concatenated list of return values as if each pattern had been processed individually. Specifically, any duplicates will NOT be removed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/gettmatch?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>gettmatch</title>
        <link>http://www.epicsol.org/help/gettmatch?rev=1154402550</link>
        <description># $EPIC: gettmatch.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$gettmatch(&lt;array&gt; &lt;pattern&gt;)

This function returns the best match of &lt;pattern&gt; within the array of strings specified by &lt;array&gt;.  This is different than $getmatches(), which returns all matches.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/getuid?rev=1154402550">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:22:30+00:00</dc:date>
        <title>getuid</title>
        <link>http://www.epicsol.org/help/getuid?rev=1154402550</link>
        <description># $EPIC: getuid.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$getuid()

Gets the current user id, similar to the Unix system call.

current userid</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/glob?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>glob</title>
        <link>http://www.epicsol.org/help/glob?rev=1172803800</link>
        <description># $EPIC: glob.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$glob(&lt;file glob pattern&gt;)

This function is used to find filenames that are matched by specified patterns.  This function is controlled by a compile time option, so it may not be available on every installation.  Multiple patterns may be specified.  Hidden files (dot-files) are not displayed unless a glob pattern beginning with a dot is given.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/global?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>global</title>
        <link>http://www.epicsol.org/help/global?rev=1156876398</link>
        <description># $EPIC: global.txt,v 1.4 2006/08/29 18:33:16 sthalik Exp $ 

load global

This script is loaded automatically when the client first starts.  At the time of this writing, it automatically loads 2.8SCRIPT and LOCAL.  It also sets the following aliases:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/globi?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>globi</title>
        <link>http://www.epicsol.org/help/globi?rev=1172803800</link>
        <description># $EPIC: globi.txt,v 1.2 2006/08/01 03:22:01 sthalik Exp $ 

$globi(&lt;file glob pattern&gt;)

This is just like $glob(), but it’s case insensitive.  This is necessary for doing filename generation when you can’t control whether the files  will be in uppercase or lower case (such as with the /HELP command.)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/glossary?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>glossary</title>
        <link>http://www.epicsol.org/help/glossary?rev=1152593863</link>
        <description>This file contains definitions and examples for epic concepts that are not  covered by their own help files</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/grep?rev=1171939800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T20:50:00+00:00</dc:date>
        <title>grep</title>
        <link>http://www.epicsol.org/help/grep?rev=1171939800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/guh?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>guh</title>
        <link>http://www.epicsol.org/help/guh?rev=1156876398</link>
        <description># $EPIC: guh.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

load guh

This script consists of a trio of functions, primarily aimed at fetching information about other clients.  Each relies on a server query, so they may not return the requested information immediately.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/hash_32bit?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>hash_32bit</title>
        <link>http://www.epicsol.org/help/hash_32bit?rev=1172803800</link>
        <description># $EPIC: hash_32bit.txt,v 1.2 2006/08/01 03:29:42 sthalik Exp $ 

$hash_32bit(&lt;word&gt; &lt;length&gt;)

	*  If the &lt;word&gt; argument is omitted the empty string is returned
	*  If the &lt;length&gt; argument is omitted it defaults to 0
	*  If the &lt;length&gt; argument is a negative number of is greater than 64, it is changed to 20.
	*  The return value of this function is a 32 bit signed integer that is a “hash” of the first &lt;length&gt; characters in &lt;word&gt;.
	*  Analytically speaking, hashing is a specific type of…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/help?rev=1171945200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T22:20:00+00:00</dc:date>
        <title>help</title>
        <link>http://www.epicsol.org/help/help?rev=1171945200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/highlight?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>highlight</title>
        <link>http://www.epicsol.org/help/highlight?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/history?rev=1174087200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-16T18:20:00+00:00</dc:date>
        <title>history</title>
        <link>http://www.epicsol.org/help/history?rev=1174087200</link>
        <description># $EPIC: history.txt,v 1.3 2006/08/01 03:30:43 sthalik Exp $ 

history 
 history [&lt;number&gt;] 
 ! [&lt;history number|history match&gt;]

With the HISTORY command you can display commands that you have previously executed at the input prompt.  The HISTORY command  attempts to behave similar to bash or tcsh for your sanity.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/hold_mode?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>hold_mode</title>
        <link>http://www.epicsol.org/help/hold_mode?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/hook?rev=1154402989">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:29:49+00:00</dc:date>
        <title>hook</title>
        <link>http://www.epicsol.org/help/hook?rev=1154402989</link>
        <description>hook &lt;anything&gt;

HOOK throws an on hook event.  The on hook feature is your way to create your own user-defined ons.

This script will echo a line every 10 seconds:
    on ^hook &quot;foo&quot; {
       timer 10 {
          echo This line is repeated every 10 seconds
          hook foo
       }
    }
    hook foo
 #$EPIC: hook.txt,v 1.2 2006/08/01 03:29:42 sthalik Exp $</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/hookctl?rev=1157079000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T21:50:00+00:00</dc:date>
        <title>hookctl</title>
        <link>http://www.epicsol.org/help/hookctl?rev=1157079000</link>
        <description>=== ADDING AND REMOVING HOOKS ===
  $hookctl(ADD [#][!][']&lt;noise&gt;&lt;TYPE&gt; [&lt;serial&gt;] &lt;pattern&gt; 
                                                      [(&lt;arg list&gt;)] &lt;code&gt;)
      Compare this to:
         /ON [#]&lt;noise&gt;&lt;TYPE&gt; [&lt;serial&gt;] [!]&lt;pattern&gt; [(&lt;arglist&gt;)] &lt;code&gt;      Where [#] is used to indicate a &lt;serial&gt; number should be used,
      where [!] is used to indicate that the ON is a &quot;negative&quot; ON
      where ['] is used to indicate that the ON is a &quot;flexible&quot; ON
      where [&lt;noise&gt;] is one…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/hostname?rev=1158664800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-19T06:20:00+00:00</dc:date>
        <title>hostname</title>
        <link>http://www.epicsol.org/help/hostname?rev=1158664800</link>
        <description># $EPIC: hostname.txt,v 1.4 2006/09/19 10:52:37 sthalik Exp $ 

hostname &lt;hostname for ipv4 and ipv6&gt; 
 hostname [hostname for ipv4]/[hostname for ipv6]

EPIC has many opportunities to create internet connections.  The most  obvious circumstances are server connections and dcc connections.  Every  internet connection has a specific internet protocol (IP) address (in IPv4,  addresses are 32 bit integers; in IPv6, they are larger) for both you and  for the person you’re talking to.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/idle?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>idle</title>
        <link>http://www.epicsol.org/help/idle?rev=1154403642</link>
        <description># $EPIC: idle.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$idle()

	*  Arguments, if any, will be ignored.
	*  Returns the number of seconds since you last pressed a key.
	*  Equivalent to $E.
	*  Present for compatibility with ircII.

This returns your “idle time”, which is measured by the number of seconds since you last pressed a key, which is what we consider “not idle”.  Use  $idle() instead of $E if you want to be laterally compatible with standard  ircII.  Note that the client…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/if?rev=1180585200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-30T23:20:00+00:00</dc:date>
        <title>if</title>
        <link>http://www.epicsol.org/help/if?rev=1180585200</link>
        <description>if (&lt;condition&gt;) &lt;then&gt; 
 if (&lt;condition&gt;) { &lt;then&gt; } [{ &lt;else&gt; }] 
 if (&lt;condition&gt;) { &lt;then&gt; } elsif (&lt;condition&gt;) { &lt;then&gt; } else { &lt;then&gt; } 
 if (&lt;condition&gt;) { &lt;then&gt; } elif (&lt;condition&gt;) { &lt;then&gt; } 
 if (&lt;condition&gt;) { &lt;then&gt; } else if (&lt;condition&gt;) { &lt;then&gt; }</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ifindfirst?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>ifindfirst</title>
        <link>http://www.epicsol.org/help/ifindfirst?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ifinditem?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>ifinditem</title>
        <link>http://www.epicsol.org/help/ifinditem?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ifinditems?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>ifinditems</title>
        <link>http://www.epicsol.org/help/ifinditems?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/igetitem?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>igetitem</title>
        <link>http://www.epicsol.org/help/igetitem?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/igetmatches?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>igetmatches</title>
        <link>http://www.epicsol.org/help/igetmatches?rev=1154403642</link>
        <description># $EPIC: igetmatches.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$igetmatches(&lt;array&gt; &lt;pattern&gt;) 
  $igetrmatches(&lt;array&gt; &lt;string&gt;)

This functions operate in a manner similar to $getmatches() and $getrmatches(), except that they return an index number (in alphabetical order) of the array members rather than the item numbers.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/igetrmatches?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>igetrmatches</title>
        <link>http://www.epicsol.org/help/igetrmatches?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ignore?rev=1157034000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T09:20:00+00:00</dc:date>
        <title>ignore</title>
        <link>http://www.epicsol.org/help/ignore?rev=1157034000</link>
        <description># $EPIC: ignore.txt,v 1.4 2006/08/31 14:06:54 sthalik Exp $ 

ignore [&lt;nick&gt;]             +|^]&lt;message type(s)&gt;] \\
__ignore__ [&lt;user@host&gt;]        [[-|+|^]&lt;message type(s)&gt;] \\
__ignore__ [&lt;nick!user@host&gt;]   [[-|+|^]&lt;message type(s)&gt;] \\
__ignore__ [&lt;channel&gt;]          [[-|+|^]&lt;message type(s)&gt;] \\
__ignore__ [&lt;refnum&gt;]           [[-|+|^]&lt;message type(s)&gt;] \\
__ignore__ [&lt;something&gt;] [&lt;types&gt;] [REASON &quot;&lt;reason&gt;&quot;] \\
__ignore__ [&lt;something&gt;] [&lt;types&gt;] [REASON &quot;&lt;reason&gt;&quot;]

======Description:====…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ignorectl?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>ignorectl</title>
        <link>http://www.epicsol.org/help/ignorectl?rev=1156876398</link>
        <description># $EPIC: ignorectl.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$ignorectl(REFNUMS) 
  $ignorectl(REFNUM &lt;refnum&gt;) 
  $ignorectl(ADD &lt;ignore-pattern&gt; [level-desc]) 
  $ignorectl(CHANGE &lt;refnum&gt; [level-desc]) 
  $ignorectl(DELETE &lt;refnum&gt;) 
  $ignorectl(PATTERN &lt;wildcard-pattern&gt;) 
  $ignorectl(RPATTERN &lt;nick!user@host&gt;) 
  $ignorectl(WITH_TYPES [level-desc]) 
  $ignorectl(GET &lt;refnum&gt; &lt;item&gt;) 
  $ignorectl(SET &lt;refnum&gt; &lt;item&gt; &lt;value&gt;)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/index?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>index</title>
        <link>http://www.epicsol.org/help/index?rev=1172803800</link>
        <description># $EPIC: index.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$index(&lt;characters&gt; &lt;text&gt;)

	*  If the &lt;characters&gt; argument is omitted the empty string is returned.
	*  &lt;characters&gt; may contain any number of different characters.  If you want to include the space character, enclose &lt;characters&gt; in double quotes.  If you want to include the double-quote character, then put some other character before it that won’t be in &lt;text&gt;.
	*  If the first character in &lt;characters&gt; is the caret (”^”…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/indextoitem?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>indextoitem</title>
        <link>http://www.epicsol.org/help/indextoitem?rev=1154403642</link>
        <description># $EPIC: indextoitem.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$indextoitem(&lt;array&gt; &lt;index number&gt;) $itemtoindex(&lt;array&gt; &lt;item number&gt;)

These functions are used to convert between array item numbers are index numbers.

Item numbers are counted incrementally as items are added to an array, starting at 0 (zero).  Each new item uses the next available item number; if there are 5 items in an array, the next item that may be added is item number 5 (remember that we count from zero... 5 items is …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/indextoword?rev=1154404068">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:47:48+00:00</dc:date>
        <title>indextoword</title>
        <link>http://www.epicsol.org/help/indextoword?rev=1154404068</link>
        <description># $EPIC: indextoword.txt,v 1.3 2006/08/01 03:47:40 sthalik Exp $ 

$indextoword(&lt;position&gt; &lt;text&gt;)

	*  If the &lt;position&gt; argument is omitted the empty string is returned.
	*  If the &lt;position&gt; argument is a negative number the empty string is returned.
	*  If the &lt;text&gt; argument is omitted the empty string is returned.
	*  If the length of &lt;text&gt; is less than &lt;position&gt; the empty string is returned.
	*  Otherwise, the return value returns a value suitable for use with the $word() function (or o…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/info?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>info</title>
        <link>http://www.epicsol.org/help/info?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the info command or the info function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/info_command?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>info_command</title>
        <link>http://www.epicsol.org/help/info_command?rev=1152593863</link>
        <description>info [&lt;server&gt;]

This command asks the server for information about the ircd program. You will see a list of contributers to ircd, and ircII, and EPIC.

You can query a remote server, but that doesn’t serve much purpose since networks usually run the same software network-wide.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/info_function?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>info_function</title>
        <link>http://www.epicsol.org/help/info_function?rev=1154403642</link>
        <description># $EPIC: info_function.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$info(c|o|s|v|r|i)

This function returns information about how the client was compiled.

This function is used to fetch information stored in the client at compile time.  It can be used to find out who compiled it, and when; what #define options were enabled; and to get the checksums of the binary.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/input?rev=1157109600">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-01T06:20:00+00:00</dc:date>
        <title>input</title>
        <link>http://www.epicsol.org/help/input?rev=1157109600</link>
        <description>input      “&lt;prompt&gt;” &lt;command&gt; [&lt;arguments&gt;] 
 input_char “&lt;prompt&gt;” &lt;command&gt; [&lt;arguments&gt;]

This command is primarily for use inside scripts.  It allows the client to present the user with a visible prompt for specific commands.  This can be used for interactive commands, for command confirmation, etc. Multiple commands may be specified if surrounded with curly braces.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/input_char?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>input_char</title>
        <link>http://www.epicsol.org/help/input_char?rev=1154403642</link>
        <description>input_char [-noecho] “&lt;prompt&gt;” {&lt;stuff&gt;}

This command prompts the user to type ONE character and then runs the  &lt;stuff&gt; and $* will be the user’s response.

The -noecho option will suppress the outputting of the character to the input line as it is typed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/input_handling?rev=1179609176">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-19T16:12:56+00:00</dc:date>
        <title>input_handling</title>
        <link>http://www.epicsol.org/help/input_handling?rev=1179609176</link>
        <description>I get many requests for utf8 support.  As of the time I write this, epic does not support utf8, and support for it is not planned in the short term. This document describes how epic handles your keypresses, and discusses how utf8 support might grow in the future.  This document is not intended to be  excruciatingly exacting enough to satisfy pedants, but rather to gently  introduce people to the issues and why console programs have a much harder time of it than graphical program.s</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/insert?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>insert</title>
        <link>http://www.epicsol.org/help/insert?rev=1172803800</link>
        <description># $EPIC: insert.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$insert(&lt;num&gt; &lt;word&gt; &lt;text&gt;)

	*  If the &lt;num&gt; integer argument is omitted the empty string is returned.
	*  If the &lt;word&gt; argument is omitted the empty string is returned.
	*  The return value of this function is &lt;text&gt; with the &lt;word&gt; argument inserted after the &lt;num&gt;th character.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/insertw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>insertw</title>
        <link>http://www.epicsol.org/help/insertw?rev=1172803800</link>
        <description># $EPIC: insertw.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$insertw(&lt;index&gt; &lt;word&gt; &lt;word list&gt;)

	*  If the &lt;index&gt; argument is omitted the empty string is returned.
	*  If the &lt;index&gt; argument is less than 1, then the return value is the rest of the argument list as it is passed. (&lt;word&gt; &lt;word list&gt;)
	*  Otherwise, the return value is a copy of &lt;word list&gt; that has had &lt;word&gt; inserted as the &lt;index&gt;th word, counting from zero.
	*  No words in &lt;word list&gt; are removed.
	*  Historically &lt;word …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/introduction?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>introduction</title>
        <link>http://www.epicsol.org/help/introduction?rev=1154403642</link>
        <description>Crash Course in irc with EPIC

 You are using the EPIC irc client.  Assuming you have the correct help files for your client, you are using version 4 of EPIC.  EPIC is a variant of the ircII client that contains countless enhancements, while retaining near full backward compatibility with ircII version 2.8.2.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/invite?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>invite</title>
        <link>http://www.epicsol.org/help/invite?rev=1154403642</link>
        <description># $EPIC: invite.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

invite &lt;nickname&gt; &lt;channel&gt;

You may invite another irc user to join a channel by sending them an  invitation with INVITE.  If a channel is join-by-invitation-only (mode +i), you must be a channel operator to invite people there.  Some servers also require that you be a member of a channel to invite others when the channel is not invite-only.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/iptolong?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>iptolong</title>
        <link>http://www.epicsol.org/help/iptolong?rev=1154403642</link>
        <description># $EPIC: iptolong.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$iptolong(&lt;dotted-quad&gt;)

	*  If the &lt;dotted-quad&gt; value is omitted the empty string is returned.
	*  The &lt;dotted-quad&gt; value is taken to be a dotted-quad ipv4 internet address of the form “A.B.C.D” where A,B,C,D are integers less than 256.
	*  The return value is the NETWORK ORDER integer equivalent of &lt;dotted-quad&gt;.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/iptoname?rev=1154404068">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:47:48+00:00</dc:date>
        <title>iptoname</title>
        <link>http://www.epicsol.org/help/iptoname?rev=1154404068</link>
        <description># $EPIC: iptoname.txt,v 1.3 2006/08/01 03:47:40 sthalik Exp $ 

$iptoname(&lt;ip address&gt;) 
  $nametoip(&lt;hostname&gt;)

These functions are used to convert an IP address to a hostname, and vice versa.   The $iptoname() function returns the hostname associated with the given IP address, and $nametoip() does the opposite.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ipv6?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>ipv6</title>
        <link>http://www.epicsol.org/help/ipv6?rev=1156876398</link>
        <description>IPv6 Support

As of 7/29/2002 EPIC fully supports IPv6 in server descriptions, server connections, $connect(), $listen(), /DCC GET, Virtual Hostnames, $iptoname().

Server descriptions:

Surround the ipv6 p-addr with square brackets: 
 /server [1:2::3]:...</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ircii_syntax?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>ircii_syntax</title>
        <link>http://www.epicsol.org/help/ircii_syntax?rev=1171347600</link>
        <description>The ircII language is organized into blocks.

A block is a sequence of statements separated by semicolons.

A statement is one of the following

	*  A command statement
	*  An expression statement
	*  A block statement

 A command statement is of the form</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/irclib?rev=1156132200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T22:50:00+00:00</dc:date>
        <title>irclib</title>
        <link>http://www.epicsol.org/help/irclib?rev=1156132200</link>
        <description># $EPIC: irclib.txt,v 1.3 2006/08/21 03:39:11 sthalik Exp $ 

$irclib()

This function returns the path to the irc library that the client is currently using.  This value is set at client boot time and does not change afterwards. The irc library path influences the default values of /SET LOAD_PATH and /SET HELP_PATH.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ircuser?rev=1158664800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-19T06:20:00+00:00</dc:date>
        <title>ircuser</title>
        <link>http://www.epicsol.org/help/ircuser?rev=1158664800</link>
        <description># $EPIC: ircuser.txt,v 1.3 2006/09/19 10:52:37 sthalik Exp $ 

ircuser &lt;username&gt;

Whenever you connect to an irc server, the client sends some information about you to the server (``registration’‘).  One of the pieces of infor- mation it sends is your “username”.  This is supposed to be the name of the account you are logged into.  The server treats this username as nothing more than a fallback value; a hint.  The server does not trust the client to send trustworthy data (and why should…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isalpha?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>isalpha</title>
        <link>http://www.epicsol.org/help/isalpha?rev=1152593863</link>
        <description># $EPIC: isalpha.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$isalpha(&lt;text&gt;) 
 $isdigit(&lt;text&gt;)

These function test whether the first character in the given string is an alphabetical character or a digit.  Only the first character is tested.

These functions are useful for testing an input string to see whether it is a number or a text string.  One use for this might be to check if it would be suitable input for $iptoname() or $nametoip().  Keep in mind that only the first character is t…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isaway?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>isaway</title>
        <link>http://www.epicsol.org/help/isaway?rev=1154403642</link>
        <description># $EPIC: isaway.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$isaway() 
 $isaway(&lt;server refnum&gt;)

	*  If the &lt;server refnum&gt; argument is omitted, the “from (current) server” is the default.
	*  If the &lt;server refnum&gt; argument is not a number, it will be changed to the server refnum 0.
	*  If the &lt;server refnum&gt; argument is not a valid server refnum, the return value is 0.
	*  This function returns 1 if you are AWAY on that server, and 0 if you are not.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ischannel?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>ischannel</title>
        <link>http://www.epicsol.org/help/ischannel?rev=1154403642</link>
        <description># $EPIC: ischannel.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$ischannel(&lt;channel name&gt;)

	*  This function returns 1 if &lt;channel name&gt; is a valid channel name, and 0 if it is not a valid channel name.
	*  A channel is “valid” if it begins with the plus character, (’+’), the hash character (’#’), the ampersand (’&amp;’), or the bang (’!’).
	*  This function does NOT tell you whether or not a channel exists.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ischanop?rev=1160761867">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-13T12:51:07+00:00</dc:date>
        <title>ischanop</title>
        <link>http://www.epicsol.org/help/ischanop?rev=1160761867</link>
        <description># $EPIC: ischanop.txt,v 1.5 2006/10/13 17:51:04 sthalik Exp $ 

$ischanop(&lt;nick&gt; &lt;channel&gt;)

	*  If the &lt;nick&gt; argument is omitted, the empty string is returned.
	*  If the &lt;channel&gt; argument is omitted, or if it is a literal star (’*’), then the current channel is assumed.  
	*  BEWARE -- if you are connected to more than one server and the current window is connected to a different server than whatever context this function is called in, it may falsely return 0.  To be sure, always specify…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ischanvoice?rev=1154404068">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:47:48+00:00</dc:date>
        <title>ischanvoice</title>
        <link>http://www.epicsol.org/help/ischanvoice?rev=1154404068</link>
        <description># $EPIC: ischanvoice.txt,v 1.3 2006/08/01 03:47:40 sthalik Exp $ 

$ischanvoice(&lt;nick&gt; &lt;channel&gt;)

This function searches the client’s channel cache for the user &lt;nick&gt; on the channel &lt;channel&gt; for the current server refnum, and returns their current channel voiced status.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isconnected?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>isconnected</title>
        <link>http://www.epicsol.org/help/isconnected?rev=1154403642</link>
        <description># $EPIC: isconnected.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$isconnected([&lt;server refnum&gt;])

This function tells wether a server is fully connected and ready to receive data. If no arguments are given, the last server to send you data is assumed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/iscurchan?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>iscurchan</title>
        <link>http://www.epicsol.org/help/iscurchan?rev=1152593863</link>
        <description># $EPIC: iscurchan.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$iscurchan(&lt;channel name&gt;)

This function returns ‘1’ if the input channel name is the current channel on any window connected to the current server.

This function was intended to allow more flexibility for testing the current channel in an ON hook.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isdigit?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>isdigit</title>
        <link>http://www.epicsol.org/help/isdigit?rev=1152593863</link>
        <description># $EPIC: isdigit.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$isalpha(&lt;text&gt;) 
  $isdigit(&lt;text&gt;)

These function test whether the first character in the given string is an alphabetical character or a digit.  Only the first character is tested.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isdisplaying?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>isdisplaying</title>
        <link>http://www.epicsol.org/help/isdisplaying?rev=1156876398</link>
        <description># $EPIC: isdisplaying.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$isdisplaying()

	*  This function returns 0 if output is being “suppressed”.
	*  This function returns 1 if output is not being “suppressed”
	*  Output is NEVER “suppressed” in the following circumstances
	*  The /ECHO command turns off the suppressed value unless you specify the /ECHO -SAY option
	*  The /SENDLINE command turns off the suppressed value.
	*  Output is “suppressed” in the following circumstances:…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isencrypted?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>isencrypted</title>
        <link>http://www.epicsol.org/help/isencrypted?rev=1152593863</link>
        <description># $EPIC: isencrypted.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$isencrypted(&lt;server refnum&gt;)

	*  This function returns 0

The EPIC-SSL client’s version of this function returns 1 if the connect to server &lt;server refnum&gt; is encrypted (via SSL).  EPIC’s version always returns 0 because it does not support SSL server connections.  Use this function to isolate code that needs to behave differently for SSL server connections.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isfilevalid?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>isfilevalid</title>
        <link>http://www.epicsol.org/help/isfilevalid?rev=1171513201</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ishalfop?rev=1160761867">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-13T12:51:07+00:00</dc:date>
        <title>ishalfop</title>
        <link>http://www.epicsol.org/help/ishalfop?rev=1160761867</link>
        <description># $EPIC: ishalfop.txt,v 1.5 2006/10/13 17:51:04 sthalik Exp $ 

$ishalfop(&lt;nick&gt; &lt;channel&gt;)

	*  If the &lt;nick&gt; argument is omitted, the empty string is returned.
	*  If the &lt;channel&gt; argument is omitted, or if it is a literal star (’*’), then the current channel is assumed.  
	*  BEWARE -- if you are connected to more than one server and the current window is connected to a different server than whatever context this function is called in, it may falsely return 0.  To be sure, always specify…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/isnumber?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>isnumber</title>
        <link>http://www.epicsol.org/help/isnumber?rev=1154403642</link>
        <description># $EPIC: isnumber.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$isnumber(&lt;text&gt;) 
  $isnumber(b&lt;base-num&gt; &lt;text&gt;) 
 $isnumber(&lt;text&gt; b&lt;base-num&gt;)

	*  The &lt;base-num&gt; argument may either be the first or second word, but in either case must be prefixed with the literal ‘b’ character.
	*  The &lt;text&gt; argument may either be the first or second word, but in either case must NOT be prefixed with the literal ‘b’ character.
	*  If the &lt;base-num&gt; argument is not specified, the default value is 0.…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ison?rev=1156966113">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-30T14:28:33+00:00</dc:date>
        <title>ison</title>
        <link>http://www.epicsol.org/help/ison?rev=1156966113</link>
        <description>ison [-n] [-s] [-len &lt;number&gt;] [-oncmd &lt;command&gt;] [-offcmd &lt;command&gt;] [&lt;nick&gt; [&lt;nick&gt; ...]]

This server query implements the underlying functionality for the NOTIFY command.  Given a list of nicknames, it returns the subset of those nicknames that are currently on your network.  If none of them are on the network, an empty list is returned.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/itemtoindex?rev=1154403642">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:40:42+00:00</dc:date>
        <title>itemtoindex</title>
        <link>http://www.epicsol.org/help/itemtoindex?rev=1154403642</link>
        <description># $EPIC: itemtoindex.txt,v 1.2 2006/08/01 03:40:36 sthalik Exp $ 

$indextoitem(&lt;array&gt; &lt;index number&gt;) 
 $itemtoindex(&lt;array&gt; &lt;item number&gt;)

These functions are used to convert between array item numbers are index numbers.

Item numbers are counted incrementally as items are added to an array, starting at 0 (zero).  Each new item uses the next available item number; if there are 5 items in an array, the next item that may be added is item number 5 (remember that we count from zero... 5 items i…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/jn?rev=1154404317">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:51:57+00:00</dc:date>
        <title>jn</title>
        <link>http://www.epicsol.org/help/jn?rev=1154404317</link>
        <description># $EPIC: jn.txt,v 1.3 2006/08/01 03:51:53 sthalik Exp $ 

$jn(&lt;level&gt; &lt;number&gt;)

	*  Returns the bessel function of the first kind of the order &lt;level&gt; for &lt;number&gt;.
	*  If the &lt;level&gt; or &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means there was an error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/join?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>join</title>
        <link>http://www.epicsol.org/help/join?rev=1156876398</link>
        <description># $EPIC: join.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

//join [-invite|&lt;channel list&gt; [&lt;key&gt;]] 
 join        (join channel you were invited to) 
 join &lt;chan&gt;[,&lt;chan&gt;]    (comma separate multiple channels) [keys do not work with commas] 
 join channel &lt;key&gt;    (will auto-prepend a # for you) 
 join #channel &lt;key&gt;   (join a network channel) 
 join &amp;channel &lt;key&gt;   (join a local server channel) 
 join !channel &lt;key&gt;   (join an IRCNet “id” channel) 
 join +channel     (join an IRCNet “mod…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/joinstr?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>joinstr</title>
        <link>http://www.epicsol.org/help/joinstr?rev=1171513201</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/jot?rev=1154404289">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:51:29+00:00</dc:date>
        <title>jot</title>
        <link>http://www.epicsol.org/help/jot?rev=1154404289</link>
        <description># $EPIC: jot.txt,v 1.2 2006/08/01 03:50:35 sthalik Exp $ 

$jot(&lt;start&gt; &lt;stop&gt; &lt;interval&gt;)

	*  If the &lt;start&gt; argument is omitted the empty string is returned.
	*  If the &lt;stop&gt; argument is omitted the empty string is returned.
	*  If the &lt;interval&gt; argument is omitted the default value of 1 is used.
	*  If the &lt;interval&gt; argument is 0, the empty string is returned.
	*  The &lt;interval&gt; argument should be an integer value -- support for fractional numbers will be added in the future.
	*  The &lt;int…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/karll_arrays?rev=1172552257">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T22:57:37+00:00</dc:date>
        <title>karll_arrays</title>
        <link>http://www.epicsol.org/help/karll_arrays?rev=1172552257</link>
        <description>What are Karll Arrays?

Karll Arrays (named after the person who contributed them to the client) are named collections of items.  Unlike the client’s standard associative  arrays, karll arrays use index refnums to refer to items.

Arrays can have any name that is a lawful C string, and array names are  case sensitive.  An array is created when you set item 0 in that array. Any other operation on a non-existant array has not been created is a  “not found” error.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/key?rev=1154404511">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:55:11+00:00</dc:date>
        <title>key</title>
        <link>http://www.epicsol.org/help/key?rev=1154404511</link>
        <description># $EPIC: key.txt,v 1.2 2006/08/01 03:55:07 sthalik Exp $ 

$key(&lt;channel list&gt;)

	*  If the &lt;channel list&gt; argument is omitted, the current channel is used.  THIS MAY NOT BE THE CORRECT CHANNEL IN AN /ON!
	*  &lt;channel list&gt; is taken as a word list (space separated) of channel names.  The asterisk (”*”) is a special channel name that refers to the current window’s current channel.  THIS MAY NOT BE THE CORRECT CHANNEL IN AN /ON!
	*  The return value is a word list of channel keys correspondi…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/key_bindings?rev=1154404511">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:55:11+00:00</dc:date>
        <title>key_bindings</title>
        <link>http://www.epicsol.org/help/key_bindings?rev=1154404511</link>
        <description>How to Use Key Bindings in EPIC

 One of the strengths of this client is its /bind command.  It permits any key or sequences of keys to be bound to any arbitrary action.  You are most likely already familiar with using keyboard shortcuts with other programs.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/kick?rev=1154404511">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:55:11+00:00</dc:date>
        <title>kick</title>
        <link>http://www.epicsol.org/help/kick?rev=1154404511</link>
        <description># $EPIC: kick.txt,v 1.2 2006/08/01 03:55:07 sthalik Exp $ 

kick *|&lt;channel&gt; &lt;nickname&gt; [&lt;reason for kick&gt;]

This command revokes the membership of another irc user from a channel in which you are a channel operator.  Customarily, it is used to remove troublemakers, flooders, or others who are making a nuisance of themselves. You may specify a reason for the kick, and doing so is considered good  style by most; however it is not required.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/kill?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>kill</title>
        <link>http://www.epicsol.org/help/kill?rev=1184106000</link>
        <description>kill &lt;nick&gt; &lt;comment&gt;

KILL is used to forcibly remote a client from the irc network.  It works similarly to KICK, except that a reason must be given (even if it is meaningless or flat-out wrong).

In general, KILL is useful only as a warning tool for abusive users. Modern irc clients (this one included) have automated means for reconnecting to a server after a disconnection (whether due to a KILL or something else), so KILL is by no means a permanent solution.  It is not intended as a means for…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/killpid?rev=1154404511">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:55:11+00:00</dc:date>
        <title>killpid</title>
        <link>http://www.epicsol.org/help/killpid?rev=1154404511</link>
        <description>#$EPIC: killpid.txt,v 1.2 2006/08/01 03:55:07 sthalik Exp $ 

$killpid(&lt;signal&gt; &lt;pid&gt; [...&lt;pid&gt;])

This function sends a signal to one or more pids

This allows sending signals to other processes without having to used exec to invoke the kill command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/knock?rev=1154404511">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:55:11+00:00</dc:date>
        <title>knock</title>
        <link>http://www.epicsol.org/help/knock?rev=1154404511</link>
        <description># $EPIC: knock.txt,v 1.2 2006/08/01 03:55:07 sthalik Exp $ 

knock &lt;channel&gt;

The KNOCK command sends a message to &lt;channel&gt; asking them to  INVITE you.  This is useful for channels with the +i channel  mode (which requires an invitation from a channel operator before  you may join.)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/lastlog?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>lastlog</title>
        <link>http://www.epicsol.org/help/lastlog?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the lastlog command or the lastlog function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/lastlog_command?rev=1171939800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T20:50:00+00:00</dc:date>
        <title>lastlog_command</title>
        <link>http://www.epicsol.org/help/lastlog_command?rev=1171939800</link>
        <description># $EPIC: lastlog_command.txt,v 1.6 2006/08/31 14:06:54 sthalik Exp $ 

lastlog [-] [-&lt;flag&gt;] [--&lt;flag&gt;] [-mangle &lt;descr&gt;] [&lt;pattern&gt;] [&lt;number of entries&gt; [&lt;start&gt;]]

LASTLOG allows you to grep through output lines that have previously been displayed on your screen.  The contents of this buffer are controlled by SET LASTLOG_LEVEL and the size is controlled by SET LASTLOG.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/lastlog_function?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>lastlog_function</title>
        <link>http://www.epicsol.org/help/lastlog_function?rev=1172803800</link>
        <description># $EPIC: lastlog_function.txt,v 1.2 2006/08/01 04:07:08 sthalik Exp $ 

$lastlog(&lt;window&gt; &lt;pattern&gt; &lt;level&gt; ...)

This function searches the lastlog buffer of window &lt;window&gt; for lines matching &lt;pattern&gt; _and_ with lastlog level matching any of &lt;level&gt;. All arguments are required, but you can specify additional &lt;level&gt;s. If you wish all lines matching &lt;pattern&gt; to be returned, specify &lt;level&gt; as ALL.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/left?rev=1154405583">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:13:03+00:00</dc:date>
        <title>left</title>
        <link>http://www.epicsol.org/help/left?rev=1154405583</link>
        <description># $EPIC: left.txt,v 1.4 2006/08/01 04:12:59 sthalik Exp $ 

$left(&lt;count&gt; &lt;text&gt;)

	*  If &lt;count&gt; is omitted, this function returns the empty string.
	*  If &lt;text&gt; is omitted, this function returns the empty string.
	*  If &lt;count&gt; is less than 0, this function returns the empty string.
	*  If &lt;text&gt; is more than &lt;count&gt; characters long, then this function will return a copy of the first &lt;count&gt; characters in &lt;text&gt;.
	*  If &lt;text&gt; is less than or exactly &lt;count&gt; characters long, then this functio…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/leftpc?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>leftpc</title>
        <link>http://www.epicsol.org/help/leftpc?rev=1152593863</link>
        <description># $EPIC: leftpc.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$leftpc(&lt;count&gt; &lt;text&gt;)

This function returns the leftmost &lt;count&gt; printable characters of &lt;text&gt;, taking into account ANSI color codes.

&lt;count&gt; number of printable characters in &lt;text&gt;</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/leftw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>leftw</title>
        <link>http://www.epicsol.org/help/leftw?rev=1172803800</link>
        <description># $EPIC: leftw.txt,v 1.2 2006/08/01 04:07:08 sthalik Exp $ 

$leftw(&lt;count&gt; &lt;word list&gt;)

	*  If the &lt;count&gt; argument is omitted the empty string is returned.
	*  If the &lt;count&gt; argument is less than 1, the empty string is returned.
	*  This function returns the first &lt;count&gt; words from &lt;word list&gt;.
	*  Historically &lt;word list&gt; does not support double-quoted words. This may change in the future.  Try using /xdebug extractw.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/less-pipe?rev=1171738200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T12:50:00+00:00</dc:date>
        <title>less-pipe</title>
        <link>http://www.epicsol.org/help/less-pipe?rev=1171738200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/less?rev=1171738200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T12:50:00+00:00</dc:date>
        <title>less</title>
        <link>http://www.epicsol.org/help/less?rev=1171738200</link>
        <description># $EPIC: less.txt,v 1.3 2006/08/01 04:11:44 sthalik Exp $ 

load more

This script is an emulation of the Unix utility of the same name.  It displays the contents of a text file, pausing after each windowfull.

This script was written by Jeremy Nelson (hop), &lt;jnelson@acronet.net&gt;, who was inspired by the more script by archon, &lt;archon@tamu.edu&gt;.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/levelctl?rev=1171738200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T12:50:00+00:00</dc:date>
        <title>levelctl</title>
        <link>http://www.epicsol.org/help/levelctl?rev=1171738200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/levels?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>levels</title>
        <link>http://www.epicsol.org/help/levels?rev=1171513201</link>
        <description>This is a list of message levels that ignore, flood and lastlog commands use. 
 Level    Description                                                            CRAP                                                                            PUBLICS  Public messages sent and received from channels.                       MSGS     Private messages sent and received from individual nicks.              NOTICES  Notices sent and received from channels and nicks.                     WALLS    Received WA…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/levelwindow?rev=1154405507">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:11:47+00:00</dc:date>
        <title>levelwindow</title>
        <link>http://www.epicsol.org/help/levelwindow?rev=1154405507</link>
        <description># $EPIC: levelwindow.txt,v 1.3 2006/08/01 04:11:44 sthalik Exp $ 

$levelwindow(&lt;server refnum&gt; &lt;lastlog level descriptions&gt;)

	*  &lt;server refnum&gt; is, well, a server refnum (reference number)
	*  &lt;lastlog level descriptions&gt; is of the same format as /WINDOW LEVEL
	*  Only windows connected to the specified server are considered
	*  The return value is the window refnum of one of the windows connected to &lt;server refnum&gt; that has one or more of the level descriptions.
	*  To avoid ambiguity, it’…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/license?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>license</title>
        <link>http://www.epicsol.org/help/license?rev=1152593863</link>
        <description>license

This command shows you the copyright notices and license information for the software you are using.  Please remember that a license is a legal document that unconditionally grants you certain legal rights  that you would ordinarily not be entitled to.  Please honor the kindness of the granter by following the boundaries of the license.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/line?rev=1156967631">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-30T14:53:51+00:00</dc:date>
        <title>line</title>
        <link>http://www.epicsol.org/help/line?rev=1156967631</link>
        <description># $EPIC: line.txt,v 1.3 2006/08/30 19:53:48 sthalik Exp $ 

$line(&lt;line&gt; [&lt;window&gt;|-level] [-time] ...)

This function retrieves data from the lastlog buffer. 

	*  &lt;line&gt; is the number of the line in the lastlog.  1 is the last line.
	*  &lt;window&gt; is the window number of the lastlog buffer.  It defaults to the current window.  Only the last one specified is used.
	*  If the given line doesn’t exist, the empty string is returned.
	*  Otherwise, the raw text of the line is returned.
	*  If the -…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/links?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>links</title>
        <link>http://www.epicsol.org/help/links?rev=1156876398</link>
        <description>#$EPIC: links.txt,v 1.4 2006/08/29 18:22:56 sthalik Exp $ 

links [&lt;glob&gt;]

IMPORTANT: See Privacy and Restrictions sections before using this command for important warnings.

Show linked servers, and interconnections between them.

To list all servers on the network:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/list?rev=1154405233">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:07:13+00:00</dc:date>
        <title>list</title>
        <link>http://www.epicsol.org/help/list?rev=1154405233</link>
        <description>list [&lt;switch&gt; [&lt;arg&gt;] [&lt;switch&gt; [&lt;arg&gt;] ...]] [&lt;channel&gt;]

This query asks the server about all of the public channels that exist on the current network.  A summary of each channel, including the channel name, the number of users on the channel, and the channel’s topic (if any) will be displayed, one per line.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/listarray?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>listarray</title>
        <link>http://www.epicsol.org/help/listarray?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/listen?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>listen</title>
        <link>http://www.epicsol.org/help/listen?rev=1156876398</link>
        <description># $EPIC: listen.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$listen() 
 $listen(&lt;port&gt; [family])

	*  The listen function establishes a passive TCP connection (``server’‘).
	*  The &lt;port&gt; argument is optional and if provided is taken as a number.
	*  If the &lt;port&gt; argument is not a number, the empty string is returned.
	*  If the &lt;port&gt; argument is not zero and less than 1024, the empty string is returned.
	*  The optional family argument can be 4, 6, v4, or v6, and tells the client whethe…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/load?rev=1157161231">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-01T20:40:31+00:00</dc:date>
        <title>load</title>
        <link>http://www.epicsol.org/help/load?rev=1157161231</link>
        <description>load [-args] &lt;file&gt; [&lt;file&gt; ...]

The load command runs blocks of code from a file.  When you start up the client, it loads your ~/.epicrc file (assuming you didn’t use  the -q command line option.

Each &lt;file&gt; is searched for each of the directories in the colon-separated set load_path variable.  &lt;file&gt; can be an absolute pathname, or it can  start with a tilde, and the client does tilde expansion.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/loadformats?rev=1172721000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-28T21:50:00+00:00</dc:date>
        <title>loadformats</title>
        <link>http://www.epicsol.org/help/loadformats?rev=1172721000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/loadinfo?rev=1154405233">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:07:13+00:00</dc:date>
        <title>loadinfo</title>
        <link>http://www.epicsol.org/help/loadinfo?rev=1154405233</link>
        <description># $EPIC: loadinfo.txt,v 1.2 2006/08/01 04:07:08 sthalik Exp $ 

$loadinfo()

	*  If the loadinfo function is called when the LOAD command is not currently executing, the literal string “-1” is returned.
	*  Otherwise, the loadinfo function returns a three-word list where the first word is the line number in the file being loaded, the second word is the name of the file being loaded, and the third word is “pf” or “std” depending on the loader that was used.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/local.examp?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>local.examp</title>
        <link>http://www.epicsol.org/help/local.examp?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/local?rev=1154405233">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:07:13+00:00</dc:date>
        <title>local</title>
        <link>http://www.epicsol.org/help/local?rev=1154405233</link>
        <description>local &lt;variable name&gt;  
 local &lt;variable name&gt;,&lt;variable name&gt; 
 local &lt;variable name&gt; &lt;value&gt; 
 local -&lt;variable name&gt;  
 local &lt;structure&gt;. 
 local -dump

The local command creates local variables (as opposed to global variables). A local variable can be used until the end of the current atomic scope.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/log?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>log</title>
        <link>http://www.epicsol.org/help/log?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the log command or the log function or the logctl function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/log10?rev=1154405507">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:11:47+00:00</dc:date>
        <title>log10</title>
        <link>http://www.epicsol.org/help/log10?rev=1154405507</link>
        <description># $EPIC: log10.txt,v 1.3 2006/08/01 04:11:44 sthalik Exp $ 

$log10(&lt;number&gt;)

	*  Returns the base-10 logarithm of &lt;number&gt;
	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM and RANGE means an error occured.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/log_command?rev=1171513201">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-14T22:20:01+00:00</dc:date>
        <title>log_command</title>
        <link>http://www.epicsol.org/help/log_command?rev=1171513201</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/log_function?rev=1156114200">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T17:50:00+00:00</dc:date>
        <title>log_function</title>
        <link>http://www.epicsol.org/help/log_function?rev=1156114200</link>
        <description># $EPIC: log_function.txt,v 1.4 2006/08/20 22:36:18 sthalik Exp $ 

$log_function|log(&lt;number&gt;) 

	*  Returns the natural logarithm of &lt;number&gt;.
	*  If &lt;number&gt; is omitted, the empty string is returned.
	*  As always, the return value is limited to 6 decimal places.
	*  As always, DOM or RANGE means an error occurred.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/logctl?rev=1156967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-30T14:54:09+00:00</dc:date>
        <title>logctl</title>
        <link>http://www.epicsol.org/help/logctl?rev=1156967649</link>
        <description># $EPIC: logctl.txt,v 1.10 2006/08/30 19:54:06 sthalik Exp $ 

$logctl(REFNUMS [ACTIVE|INACTIVE|ALL]) 
 $logctl(REFNUM &lt;log-desc&gt;) 
 $logctl(ADD log-desc [target]) 
 $logctl(DELETE log-desc [target]) 
 $logctl(GET &lt;refnum&gt; [ITEM]) 
 $logctl(SET &lt;refnum&gt; [ITEM] [VALUE]) 
 $logctl(MATCH [pattern]) 
 $logctl(PMATCH [pattern]) 
 $logctl(CURRENT)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/longtoip?rev=1154405233">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T23:07:13+00:00</dc:date>
        <title>longtoip</title>
        <link>http://www.epicsol.org/help/longtoip?rev=1154405233</link>
        <description># $EPIC: longtoip.txt,v 1.2 2006/08/01 04:07:08 sthalik Exp $ 

$longtoip(&lt;integer&gt;)

	*  If the &lt;integer&gt; value is omitted the empty string is returned.
	*  The &lt;integer&gt; value is taken to be a 32 bit unsigned integer.
	*  The &lt;integer&gt; value is taken to be in NETWORK ORDER.
	*  The return value is the dotted-quad IP address of &lt;integer&gt;</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/lusers?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>lusers</title>
        <link>http://www.epicsol.org/help/lusers?rev=1152593863</link>
        <description>lusers [&lt;server mask&gt; [&lt;remote server&gt;]]

LUSERS (shorthand for List USERS) returns summary information about how many users are using the network.  It shows how many users are visible and how many are invisible.  It may also show how many users are connected to your server, and the maximum number of users who have been connected to your server at any one time.  It may also show the maximum number of users connected to the network at any one time.  Other information of this sort may be returned.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/lval?rev=1186435550">
        <dc:format>text/html</dc:format>
        <dc:date>2007-08-06T16:25:50+00:00</dc:date>
        <title>lval</title>
        <link>http://www.epicsol.org/help/lval?rev=1186435550</link>
        <description># $EPIC: lval.txt,v 1.1 2007/08/06 21:25:50 jnelson Exp $



An lvalue is the token on the left hand side of an assignment operation. More broadly speaking, an lvalue is a thing that may be assigned to.

There are several places where you use an lvalue:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mail?rev=1173043200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-04T15:20:00+00:00</dc:date>
        <title>mail</title>
        <link>http://www.epicsol.org/help/mail?rev=1173043200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/man?rev=1154409365">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:16:05+00:00</dc:date>
        <title>man</title>
        <link>http://www.epicsol.org/help/man?rev=1154409365</link>
        <description># $EPIC: man.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

load man

This script creates a man-like interface to the EPIC help files. It will search all subdirectories for a particular topic.

This script was written by Dawid Kuroczko.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mangle_types?rev=1172344800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-24T13:20:00+00:00</dc:date>
        <title>mangle_types</title>
        <link>http://www.epicsol.org/help/mangle_types?rev=1172344800</link>
        <description>Mangle types are used by:

	*  /lastlog -mangle
	*  /log mangle
	*  /set mangle_inbound
	*  /set mangle_outbound
	*  The status bar

All characters are grouped into one of 9 “types”:
Type number   Description             ASCII characters                                                   0             Normal chars            32-127, 160-255                                                    1             High bit control chars  128-159                                                          …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/map?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>map</title>
        <link>http://www.epicsol.org/help/map?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the map command or the map script?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/map_command?rev=1154409365">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:16:05+00:00</dc:date>
        <title>map_command</title>
        <link>http://www.epicsol.org/help/map_command?rev=1154409365</link>
        <description>map

This displays a hierarchical map of the topology of the current network, drawn from your server’s perspective.  The map is vaguely tree-shaped.

This command is available on undernet-class servers.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/map_script?rev=1173043200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-04T15:20:00+00:00</dc:date>
        <title>map_script</title>
        <link>http://www.epicsol.org/help/map_script?rev=1173043200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mask?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>mask</title>
        <link>http://www.epicsol.org/help/mask?rev=1172803800</link>
        <description># $EPIC: mask.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$mask(&lt;type&gt; &lt;address&gt;)

This function returns &lt;address&gt; in a wildcard mask according to the type specified by &lt;type&gt;. The mask types are defined in the following table: 
  &lt;type&gt;     &lt;address&gt; has a hostname       &lt;address&gt; has an ip
-------------------------------------------------------------------
    0            *!u@h.d                        *!u@d.h
    1            *!*u@h.d                       *!*u@d.h
    2            *!*@h.d…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/match?rev=1154409365">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:16:05+00:00</dc:date>
        <title>match</title>
        <link>http://www.epicsol.org/help/match?rev=1154409365</link>
        <description># $EPIC: match.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$match(&lt;pattern&gt; &lt;word list&gt;)

	*  If the &lt;pattern&gt; argument is omitted the empty string is returned.
	*  &lt;word list&gt; contains zero or more space separated “extended words”
	*  Each word in &lt;word list&gt; is taken as literal text, and each are matched against &lt;pattern&gt;.
	*  If none of the words in &lt;word list&gt; are matched by &lt;pattern&gt;, then the return value of match is 0 (zero).
	*  Otherwise, the return value is the index of the first…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/matchitem?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>matchitem</title>
        <link>http://www.epicsol.org/help/matchitem?rev=1172553600</link>
        <description># $EPIC: matchitem.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$matchitem(&lt;array&gt; &lt;word&gt;) 
 $rmatchitem(&lt;array&gt; &lt;pattern&gt;)

These functions are used to search through the given array for the item that best matches the given word or pattern.

These functions are analogous to $match() and $rmatch().  Given a word or pattern, they search through the given array’s contents and look for the best match, if any.  Basically, the array’s contents behave as if they were the list of words or patterns…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/maxlen?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>maxlen</title>
        <link>http://www.epicsol.org/help/maxlen?rev=1152593863</link>
        <description># $EPIC: maxlen.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$maxlen(&lt;word list&gt;)

	*  If the &lt;word list&gt; argument is omitted the value 0 is returned.
	*  The return value is the length of the longest word in &lt;word list&gt;.

If you want to “line up” a list of words into columns, you need to know how wide your columns should be, and that is determined by the “widest” word.  This function will give you that value, so you can compute how wide your columns should be and how many you can f…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/me?rev=1155950400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T20:20:00+00:00</dc:date>
        <title>me</title>
        <link>http://www.epicsol.org/help/me?rev=1155950400</link>
        <description># $EPIC: me.txt,v 1.3 2006/08/19 01:19:53 sthalik Exp $ 

me &lt;action description&gt;

ME lets you perform an action on your current channel.  It lets you describe what you’re doing as though someone is watching you, rather than you telling them.

To perform an action:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mesg?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>mesg</title>
        <link>http://www.epicsol.org/help/mesg?rev=1152593863</link>
        <description># $EPIC: mesg.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

mesg    [display the current terminal writability state] 
 mesg yes    [make your terminal world-writeable] 
 mesg no   [make your terminal not world-writeable]

This command simulates the effect of the unix mesg(1) command. When you specify the ‘yes’ flag, other users on your system may write messages directly to your terminal, which will mess up your ircII screen. If you specify the ‘no’ flag, other users will be prohibite…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/meta-compat?rev=1171939800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T20:50:00+00:00</dc:date>
        <title>meta-compat</title>
        <link>http://www.epicsol.org/help/meta-compat?rev=1171939800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/metric_time?rev=1154409365">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:16:05+00:00</dc:date>
        <title>metric_time</title>
        <link>http://www.epicsol.org/help/metric_time?rev=1154409365</link>
        <description># $EPIC: metric_time.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$metric_time()

The current metric time, represented as: 
$0  The number of whole days since the epoch               $1  The number of (fractional) millidays since the epoch.  
You can use this when you’re feeling particularly geeky.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mid?rev=1154409365">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:16:05+00:00</dc:date>
        <title>mid</title>
        <link>http://www.epicsol.org/help/mid?rev=1154409365</link>
        <description># $EPIC: mid.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$mid(&lt;start&gt; &lt;length&gt; &lt;text&gt;)

	*  If &lt;start&gt; is omitted, this function returns the empty string.
	*  If &lt;length&gt; is omitted, this function returns the empty string.
	*  If &lt;text&gt; is omitted, this function returns the empty string.
	*  If &lt;start&gt; is greater than the number of characters in &lt;text&gt;, this function returns the empty string.
	*  If &lt;length&gt; is zero, this function returns the empty string.
	*  If &lt;length&gt; is negative, this fun…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/midw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>midw</title>
        <link>http://www.epicsol.org/help/midw?rev=1172803800</link>
        <description># $EPIC: midw.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$midw(&lt;start&gt; &lt;length&gt; &lt;word list&gt;)

	*  If the &lt;start&gt; argument is omitted the empty string is returned.
	*  If the &lt;length&gt; argument is omitted the empty string is returned.
	*  If the &lt;start&gt; argument is less than 0, the empty string is returned.
	*  If the &lt;length&gt; argument is less than 1, the empty string is returned.
	*  The return value is the first &lt;length&gt; words of the result of removing the first &lt;start&gt; words from &lt;word list&gt;…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mkdir?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>mkdir</title>
        <link>http://www.epicsol.org/help/mkdir?rev=1172803800</link>
        <description># $EPIC: mkdir.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$mkdir(&lt;directory&gt; [&lt;directory&gt; ...])

This function adds the following directories to the filesystem, using the mkdir(3) library call.  The default permissions are 0777, minus the current umask value.  Any number of directories may be created at once.  Tilde-expansion is permitted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mktime?rev=1157044800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T12:20:00+00:00</dc:date>
        <title>mktime</title>
        <link>http://www.epicsol.org/help/mktime?rev=1157044800</link>
        <description># $EPIC: mktime.txt,v 1.2 2006/08/31 16:53:16 sthalik Exp $ 

$mktime(&lt;year&gt; &lt;month&gt; &lt;day&gt; &lt;hour&gt; &lt;minute&gt; &lt;second&gt; &lt;DST&gt;)

This function returns the epoch time basing on specified parameters. 
 Parameter          Name    Description                         $0                 year    Number of years since 1900          $1                 month   Month, in range of 0-11             $2                 day     Day of the month, in range of 1-31  $3                 hour    Hour, in range of 0-23    …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mode?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>mode</title>
        <link>http://www.epicsol.org/help/mode?rev=1156876398</link>
        <description># $EPIC: mode.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

mode &lt;your nickname|channel&gt; [&lt;+|-&gt;&lt;mode&gt; [&lt;mode parameter(s)&gt;]]


# Currently I (hop) am renovating the structure of this help file.  The
# first part of the help file will be a basic description of the purpose
# of modes in irc, both to users and to channels.  Then a description of
# user modes will follow, with each user mode documented and its side
# effects explained.  Each network will get a section where its deviant
# user modes …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/motd?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>motd</title>
        <link>http://www.epicsol.org/help/motd?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the motd command or the motd script?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/motd_command?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>motd_command</title>
        <link>http://www.epicsol.org/help/motd_command?rev=1152593863</link>
        <description>motd [&lt;server|nickname&gt;]

This queries a server’s Message Of The Day.  Each server is supposed to have an MOTD and your server sent you an MOTD when you connected to it. These messages will tell you about the server you are connected to, and any other information the server administrator wants you to know about.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/motd_script?rev=1171945200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T22:20:00+00:00</dc:date>
        <title>motd_script</title>
        <link>http://www.epicsol.org/help/motd_script?rev=1171945200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/msar?rev=1154409365">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:16:05+00:00</dc:date>
        <title>msar</title>
        <link>http://www.epicsol.org/help/msar?rev=1154409365</link>
        <description># $EPIC: msar.txt,v 1.2 2006/08/01 05:15:58 sthalik Exp $ 

$msar([i][g][r]/[&lt;search&gt;/&lt;replace&gt;/]*&lt;text&gt;)

	*  The arguments are composed of:
		*  zero or more of the options ‘i’, ‘g’, and ‘r’,
		*  a delimiter which can be any character other than ‘i’, ‘g’, or ‘r’, and is customarily a forward-slash,
		*  ZERO OR MORE SETS OF SUBSTITUTIONS:
			*  some text (”&lt;search&gt;”) that may not contain the delimiter to be removed,
			*  a delimiter; the same as (2),
			*  some te…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/msg?rev=1157079000">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T21:50:00+00:00</dc:date>
        <title>msg</title>
        <link>http://www.epicsol.org/help/msg?rev=1157079000</link>
        <description># $EPIC: msg.txt,v 1.5 2006/09/01 02:43:42 sthalik Exp $ 

msg [-server/]&lt;nickname&gt; &lt;text to send&gt; 
 msg [-server/]&lt;channel&gt; &lt;text to send&gt; 
 msg =&lt;dcc chat peer&gt; &lt;text to send&gt; 
 msg %&lt;process id|process name&gt; &lt;text to send&gt; 
 msg /&lt;command&gt; &lt;command arguments&gt;</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/mychannels?rev=1154409509">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:18:29+00:00</dc:date>
        <title>mychannels</title>
        <link>http://www.epicsol.org/help/mychannels?rev=1154409509</link>
        <description># $EPIC: mychannels.txt,v 1.3 2006/08/01 05:18:26 sthalik Exp $ 

$mychannels() 
 $mychannels(&lt;server refnum&gt;) 
 $mychannels(#&lt;window refnum&gt;) 
 $mychannels(&lt;window name&gt;)

	*  This function returns a space separated word list of all of the currently active channels on the specified server.  Pending channels (those which you have sent off a JOIN but have not received a reply back from the server) are NOT included.
	*  If the argument is a number, then it is taken as a server refnum, and the chan…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/myservers?rev=1156128692">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T21:51:32+00:00</dc:date>
        <title>myservers</title>
        <link>http://www.epicsol.org/help/myservers?rev=1156128692</link>
        <description># $EPIC: myservers.txt,v 1.3 2006/08/21 02:51:28 sthalik Exp $ 

$myservers() 
 $myservers(&lt;anything&gt;)

	*  If provided with no arguments, this function returns a space separated list of server names of all servers that epic has a connection open to. For registered connections (you’ve gotten the 001 numeric), the name will be “its” name (the server’s own name as used in the 001 numeric). For pending connections (you’ve not gotten the 001 numeric yet), the name will be “our” name (t…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/names?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>names</title>
        <link>http://www.epicsol.org/help/names?rev=1184106000</link>
        <description>names [&lt;switch&gt; [&lt;arg&gt;] [&lt;switch&gt; [&lt;arg&gt;] ...]] [&lt;channel&gt;]

NAMES is similar to LIST except it will show nicknames in addition to channel names.  Only visible users on public channels are returned.

If a nickname is prefixed with a +, that means they are a channel voice  (mode +v) on that channel.  If a nickname is prefixed with @, that means  they are a channel operator (mode +o) on that channel.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/nametoip?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>nametoip</title>
        <link>http://www.epicsol.org/help/nametoip?rev=1154410382</link>
        <description># $EPIC: nametoip.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$iptoname(&lt;ip address&gt;) 
 $nametoip(&lt;hostname&gt;)

These functions are used to convert an IP address to a hostname, and vice versa.   The $iptoname() function returns the hostname associated with the given IP address, and $nametoip() does the opposite.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/netsplit?rev=1172121600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-21T23:20:00+00:00</dc:date>
        <title>netsplit</title>
        <link>http://www.epicsol.org/help/netsplit?rev=1172121600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/new_user?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>new_user</title>
        <link>http://www.epicsol.org/help/new_user?rev=1156876398</link>
        <description>New user information about IRC

 This file is for users new to irc.  Its intention is to briefly describe what irc is all about.  It is not a command summary. Please refer to Introduction to get started with the various EPIC commands.

IRC stands for Internet Relay Chat.  It is a networked, real-time, online chat system.  Its popularity has grown enormously since its invention more than 7 years ago, and shows no signs of stopping anytime soon. There are currently upwards of 30 irc “networks”…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/newaway?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>newaway</title>
        <link>http://www.epicsol.org/help/newaway?rev=1156876398</link>
        <description># $EPIC: newaway.txt,v 1.3 2006/08/29 18:33:16 sthalik Exp $ 

load newaway

This script does essentially the same thing that set SHOW_AWAY_ONCE once did. It suppresses the on 301 server numeric if the same one is received more than once.  It will display changes in AWAY messages.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/newnick?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>newnick</title>
        <link>http://www.epicsol.org/help/newnick?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/nick?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>nick</title>
        <link>http://www.epicsol.org/help/nick?rev=1154410382</link>
        <description># $EPIC: nick.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

nick [&lt;new nickname&gt;]

The NICK command allows you to change your nickname.  If you try to  change to a nickname that someone else is using, you will get an error  message to that effect and your nickname will be unchanged.  Nicknames  are CASE-INSENSITIVE.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/nickcomp?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>nickcomp</title>
        <link>http://www.epicsol.org/help/nickcomp?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/nochops?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>nochops</title>
        <link>http://www.epicsol.org/help/nochops?rev=1154410382</link>
        <description># $EPIC: nochops.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$nochops(&lt;channel&gt;)

	*  If the &lt;channel&gt; argument is omitted, the current window’s current channel is used.  THIS IS NOT NECCESARILY THE CORRECT CHANNEL IN AN /ON!
	*  If the &lt;channel&gt; argument is the literal star character (``*’‘), the current window’s current channel is used.  THIS IS NOT NECCESARILY THE CORRECT CHANNEL IN AN /ON!
	*  This function returns the non-channel-operators on the specified channel.
	*  You must be…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/nohighlight?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>nohighlight</title>
        <link>http://www.epicsol.org/help/nohighlight?rev=1154410382</link>
        <description># $EPIC: nohighlight.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$nohighlight(&lt;string&gt;)

This function returns &lt;string&gt; with all highlight characters escaped. All ^B, ^V, ^_, ^O, ^C, and ^[ characters will be replaced by an inverse of their control character, to remove all highlighting.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/nopaste?rev=1160162400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-06T14:20:00+00:00</dc:date>
        <title>nopaste</title>
        <link>http://www.epicsol.org/help/nopaste?rev=1160162400</link>
        <description># $EPIC: nopaste.txt,v 1.2 2006/10/06 19:08:28 jnelson Exp $ 

load nopaste set nopaste ON set nopaste OFF

This script adds the set NOPASTE variable.  When you set it on, it keeps you from flooding your current target by (accidentally) pasting text to your client screen.  When you set it off, this protection is disabled.  The default value is OFF.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/note?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>note</title>
        <link>http://www.epicsol.org/help/note?rev=1152593863</link>
        <description># $EPIC: note.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

note &lt;command&gt; [+|-&lt;flags&gt;] [&lt;arguments&gt;]

The NOTE command is a historic irc server command (meaning this help file really belongs in section 3).  You would be hard pressed to find a  server that supports the NOTE command.  As of mid-2001, only the  undernet servers even come with the NOTE system, and it isn’t turned on by default, and it isn’t even a configuration-time option.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notice?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>notice</title>
        <link>http://www.epicsol.org/help/notice?rev=1156876398</link>
        <description>notice &lt;nickname&gt; &lt;text to send&gt; 
  notice &lt;channel&gt; &lt;text to send&gt; 
  notice =&lt;dcc chat peer&gt; &lt;text to send&gt; 
  notice %&lt;process id|process name&gt; &lt;text to send&gt; 
  notice /&lt;command&gt; &lt;command arguments&gt;

The NOTICE command is just like the MSG command, and is used to  send a message to another target.  Whenever you use msg in response to an irc privmsg (a msg, or a ctcp request), it will be converted  into a notice for you.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notify?rev=1154410621">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:37:01+00:00</dc:date>
        <title>notify</title>
        <link>http://www.epicsol.org/help/notify?rev=1154410621</link>
        <description>This is a disambiguation page.  Do you mean the notify command, the notify function, or the notify script?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notify_command?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>notify_command</title>
        <link>http://www.epicsol.org/help/notify_command?rev=1154410382</link>
        <description># $EPIC: notify_command.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

notify 
 notify - 
 notify +]&lt;nickname&gt; [[+]&lt;nickname&gt; ... 
 notify -]&lt;nickname&gt; [[-]&lt;nickname&gt; ...

You will want to know when your irc friends enter and leave irc.  You can manage a list of nicknames with the /NOTIFY command, and when any of those nicknames join or leave your network, or when anyone changes to or from  one of the nicknames, you will be informed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notify_function?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>notify_function</title>
        <link>http://www.epicsol.org/help/notify_function?rev=1154410382</link>
        <description># $EPIC: notify_function.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$notify([on|off serv &lt;server number&gt;])

This function provides an interface to the client’s internal NOTIFY list.  If no arguments are passed, a list of all nicknames on the list is returned.  If the ON command is used, only those nicknames that are currently present on the given server are shows; if the OFF command is used, those not on irc are shown.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notify_script?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>notify_script</title>
        <link>http://www.epicsol.org/help/notify_script?rev=1154410382</link>
        <description># $EPIC: notify_script.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

load notify

This is a scripted notify system, much like EPIC’s internal notify system, with the ability to manage both global and local notify lists. 
   Alias       Description                            /nlist     shows nicknames in all notify lists       /notify    manages local and global notify lists    
 The syntax for managing notify lists is similar to that of EPIC’s internal /notify.  To modify a list, supply a li…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notifywindows?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>notifywindows</title>
        <link>http://www.epicsol.org/help/notifywindows?rev=1154410382</link>
        <description># $EPIC: notifywindows.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$notifywindows()

	*  This function returns a space-separated list of window refnums that meet the following criteria:
	*  The window must have /window notify ON
	*  The window must be hidden
	*  The window must have received output since it was hidden
	*  If no windows meet this criteria, the empty string is returned.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/notw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>notw</title>
        <link>http://www.epicsol.org/help/notw?rev=1172803800</link>
        <description># $EPIC: notw.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$notw(&lt;number&gt; &lt;word list&gt;)

	*  If the &lt;number&gt; argument is omitted the empty string is returned.
	*  If the &lt;number&gt; argument is negative, &lt;word list&gt; is returned.
	*  The return value of this function is &lt;word list&gt; with the &lt;number&gt;th word omitted, counting from zero.
	*  Extra spaces surrounding the &lt;number&gt;th word will be removed.
	*  Historically &lt;word list&gt; does not support double-quoted words. This may change in the future.  Tr…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/numarrays?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>numarrays</title>
        <link>http://www.epicsol.org/help/numarrays?rev=1154410382</link>
        <description># $EPIC: numarrays.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$numarrays()

This function shows the total number of arrays created by $setitem(). It takes no arguments, and ignores any passed to it.

This function is used to show how many arrays currently exist.  This might be useful if the arrays were named in a sequential order, thus allowing you to know what the next available number is.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/numitems?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>numitems</title>
        <link>http://www.epicsol.org/help/numitems?rev=1154410382</link>
        <description># $EPIC: numitems.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$numitems(&lt;array&gt;)

This function is used to show how many items are currently defined in the given array.

This function shows how many items are in an array.  This is quite useful, because the number it returns is the next available item number in the array.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/numlines?rev=1154410621">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:37:01+00:00</dc:date>
        <title>numlines</title>
        <link>http://www.epicsol.org/help/numlines?rev=1154410621</link>
        <description># $EPIC: numlines.txt,v 1.3 2006/08/01 05:36:58 sthalik Exp $ 

$numlines(&lt;columns&gt; &lt;string&gt;)

This function tells you the number of lines that the given string would occupy after final display in a window with a width of &lt;columns&gt;.

This function can be used to determine how many lines a particular string will occupy in particular window. One thing this could be used for is scripting a file pager that will correctly pause between each screen of output, regardless of long lines and SET CONTINUED…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/numonchannel?rev=1155953084">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:04:44+00:00</dc:date>
        <title>numonchannel</title>
        <link>http://www.epicsol.org/help/numonchannel?rev=1155953084</link>
        <description># $EPIC: numonchannel.txt,v 1.3 2006/08/19 02:04:37 sthalik Exp $ 

$numonchannel(&lt;channel&gt;)

	*  If the &lt;channel&gt; argument is omitted the current window’s current channel is assumed. 
 THIS MAY NOT NECCESARILY BE THE CORRECT CHANNEL IN AN /ON!
	*  If the &lt;channel&gt; argument is the literal asterisk, (``*’‘), then the current window’s current channel is assumed. 
 THIS MAY NOT NECCESARILY BE THE CORRECT CHANNEL IN AN /ON!
	*  This function returns the number of members of the given channel…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/numsort?rev=1153108800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T23:00:00+00:00</dc:date>
        <title>numsort</title>
        <link>http://www.epicsol.org/help/numsort?rev=1153108800</link>
        <description># $EPIC: numsort.txt,v 1.2 2006/07/17 03:42:24 jnelson Exp $ 

$numsort(&lt;list&gt;)

This function sorts the word list &lt;list&gt; in ascending numerical order. The numbers in &lt;list&gt; must be integral values, not decimal numbers. Non-numeric words are sorted in ascii order between 0 and 1. Numbers embedded within words in &lt;list&gt; are properly recognized.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/numwords?rev=1154410382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-01T00:33:02+00:00</dc:date>
        <title>numwords</title>
        <link>http://www.epicsol.org/help/numwords?rev=1154410382</link>
        <description># $EPIC: numwords.txt,v 1.2 2006/08/01 05:32:26 sthalik Exp $ 

$numwords(&lt;word list&gt;)

This function serves as a replacement for the $#var notation when you want to count the words in a string not held in a variable.

This function is used to count the number of words in an arbitrary string.  Normally, you could get this value with the $#var form, but that doesn’t work for parameter expandos or function return values.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on?rev=1192295390">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-13T12:09:50+00:00</dc:date>
        <title>on</title>
        <link>http://www.epicsol.org/help/on?rev=1192295390</link>
        <description># $EPIC: on.txt,v 1.7 2006/08/30 18:34:50 sthalik Exp $ 

This file is currently being overhauled, so it’s a mess.

on [#][&lt;modes&gt;]&lt;event-type&gt; [&lt;serial#&gt;] [-|^]&lt;match&gt; [{ &lt;action&gt; }]

ircII-EPIC is an event-driven programming language.  What this means is that your script does not cause things to happen, but rather waits for things to happen (”events”) and then reacts to them.  Each time an event occurs, EPIC executes any event handlers you have registered for the event.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_action?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_action</title>
        <link>http://www.epicsol.org/help/on_action?rev=1172946000</link>
        <description># $EPIC: on_action.txt,v 1.3 2006/08/19 02:04:37 sthalik Exp $ 

on action

This hook is triggered whenever the client observes a  CTCP ACTION.  It will hook when the recipient is either  the user or a channel.
$0   nickname of the ACTION sender                        $1   target of the ACTION (user’s nickname or a channel)  $2-  message body of the ACTION                           
To distinguish personal actions from those sent to a channel:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_channel_lost?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_channel_lost</title>
        <link>http://www.epicsol.org/help/on_channel_lost?rev=1172946000</link>
        <description># $EPIC: on_channel_lost.txt,v 1.3 2007/03/03 17:58:33 jnelson Exp $ 

on [&lt;modes&gt;]channel_lost [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This event is thrown whenever your membership in a channel ends for any  reason whatsoever.

The most common causes of losing your channel membership are part, kick, disconnect, and being disconnected by the server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_channel_nick?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_channel_nick</title>
        <link>http://www.epicsol.org/help/on_channel_nick?rev=1172946000</link>
        <description>on channel_nick

A channel_nick event is thrown each time someone (including you) on one of your channels changes nickname.  If the nick changer is on multiple channels with you, multiple events are thrown.  The default action of the channel_nick event is to throw an on nickname event.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_channel_signoff?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_channel_signoff</title>
        <link>http://www.epicsol.org/help/on_channel_signoff?rev=1172946000</link>
        <description>on [&lt;modes&gt;]channel_signoff [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

The channel_signoff event is thrown every time someone on one of your channels quits irc.  If the person is on multiple channels with you, multiple events are thrown.  The default action for channel_signoff is to throw a SIGNOFF event.  This event is not thrown when you quit irc, the event for that is exit.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_channel_sync?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_channel_sync</title>
        <link>http://www.epicsol.org/help/on_channel_sync?rev=1172946000</link>
        <description># $EPIC: on_channel_sync.txt,v 1.2 2006/08/19 01:57:03 sthalik Exp $ 

on [&lt;modes&gt;]channel_sync [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This event is thrown after all of the cached information about a channel has been collected.  When this event is thrown, it is safe to ask about who is on the channel, chanop status, userhost, and so forth.  Before this event is thrown, there are no promises!</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_connect?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_connect</title>
        <link>http://www.epicsol.org/help/on_connect?rev=1172946000</link>
        <description># $EPIC: on_connect.txt,v 1.3 2006/08/19 02:04:37 sthalik Exp $ 

on [&lt;modes&gt;]connect [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client has successfully registered with an irc server.  This hook differs from on server_established in that the on server_established hook is triggered as soon as the client establishes a TCP connection with a server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_ctcp?rev=1191860912">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-08T11:28:32+00:00</dc:date>
        <title>on_ctcp</title>
        <link>http://www.epicsol.org/help/on_ctcp?rev=1191860912</link>
        <description>on [&lt;modes&gt;]ctcp [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a CTCP message, whether directly or one sent to a channel it is on.
$0    nickname of CTCP message sender                     $1    target of CTCP (client’s nickname or channel name)  $2    type of CTCP                                        $3-   arguments to CTCP command, if any                   
To customize the normal CTCP message:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_ctcp_reply?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_ctcp_reply</title>
        <link>http://www.epicsol.org/help/on_ctcp_reply?rev=1172946000</link>
        <description># $EPIC: on_ctcp_reply.txt,v 1.3 2006/08/19 02:04:37 sthalik Exp $ 

on [&lt;modes&gt;]ctcp_reply [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a CTCP reply from another client.  Note that the client doesn’t necessarily need to send any CTCP messages to receive a “reply”.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_ctcp_request?rev=1191860912">
        <dc:format>text/html</dc:format>
        <dc:date>2007-10-08T11:28:32+00:00</dc:date>
        <title>on_ctcp_request</title>
        <link>http://www.epicsol.org/help/on_ctcp_request?rev=1191860912</link>
        <description>on ctcp_request

This hook is triggered whenever the client receives a CTCP request sent to you personally or one of the channels you are on.  Using the CTCP command within this on causes a properly formatted reply to be sent.

Because this on is hooked as the result of a PRIVMSG, you cannot send a PRIVMSG in reply to this on, only NOTICEs.  If you use the CTCP command, it will send a ctcp reply.  If you use the MSG command it will be sent as a NOTICE.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_activity?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_activity</title>
        <link>http://www.epicsol.org/help/on_dcc_activity?rev=1172946000</link>
        <description># $EPIC: on_dcc_activity.txt,v 1.2 2006/08/19 01:57:03 sthalik Exp $ 

on [&lt;modes&gt;]dcc_activity [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client updates the %D status expando, which holds metadata about the last open DCC transaction that had activity.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_chat?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_chat</title>
        <link>http://www.epicsol.org/help/on_dcc_chat?rev=1172946000</link>
        <description>on [&lt;modes&gt;]dcc_chat [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a message across a DCC CHAT connection.
$0    nickname of the message sender $1-   message received 
DCC falls outside of the irc protocol, and as such there are no restrictions on automated replies.  This creates the potential for uncontrolled looping, so caution is advised.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_connect?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_connect</title>
        <link>http://www.epicsol.org/help/on_dcc_connect?rev=1172946000</link>
        <description>on [&lt;modes&gt;]dcc_connect [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client successfully establishes a DCC connection with another client.  Currently, this is either a CHAT or a SEND connection.
$0  nickname of remote client $1  type of DCC connection $2  ip address of remote client $3  port on the ip address the client is connected to $4  file name (SEND only) $5  file size (SEND only) 
To customize the connection message:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_list?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_list</title>
        <link>http://www.epicsol.org/help/on_dcc_list?rev=1172946000</link>
        <description>on [&lt;modes&gt;]dcc_list [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a /dcc or /dcc list command is issued. The ‘banner’ of the list can be determined when $0 is “Start”, and the end of the list is determined when $0 is “end”.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_lost?rev=1179624000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-19T20:20:00+00:00</dc:date>
        <title>on_dcc_lost</title>
        <link>http://www.epicsol.org/help/on_dcc_lost?rev=1179624000</link>
        <description>#$EPIC: on_dcc_lost.txt,v 1.2 2006/08/19 01:57:03 sthalik Exp $ 

on [&lt;modes&gt;]dcc_lost [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a DCC CHAT or SEND connection ends whether or not the connection was successful or not.
$0    nickname of the dcc connection $1-   disconnection message (varies) 
To indicate that dcc connection was terminated:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_offer?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_offer</title>
        <link>http://www.epicsol.org/help/on_dcc_offer?rev=1172946000</link>
        <description>on [&lt;modes&gt;]dcc_offer [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client offers an outbound DCC.  This could be either a DCC CHAT or a file transfer.
$0    person who is being offered the DCC $1    type of DCC being offered $2    filename being offered (if type of DCC is ‘SEND’) $3-   size of file being offered (if type of DCC is ‘SEND’) 
To alert user of bad DCC’s:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_raw?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_raw</title>
        <link>http://www.epicsol.org/help/on_dcc_raw?rev=1172946000</link>
        <description>on [&lt;modes&gt;]dcc_raw [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a raw message about a tcp connection established, or a connection attempt, with $connect(). Raw messages are sent across established tcp connections with DCC RAW.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_dcc_request?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_dcc_request</title>
        <link>http://www.epicsol.org/help/on_dcc_request?rev=1172946000</link>
        <description>on [&lt;modes&gt;]dcc_request [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a DCC request of some sort (currently CHAT or SEND).
$0 nickname of remote client$1 type of DCC connection$2 description of dcc connection (currently same as $1)$3 ip address of remote client$4 port on the ip address the client is connected to$5 file name (SEND only)$6 file size (SEND only)
To customize the dcc request message:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_disconnect?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_disconnect</title>
        <link>http://www.epicsol.org/help/on_disconnect?rev=1172946000</link>
        <description>on [&lt;modes&gt;]disconnect [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client is disconnected from a server, and it is unable to reconnect to the server itself (assuming the AUTO_RECONNECT setting is turned on).  This would be any situation in which the client would normally print the following message:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_encrypted_notice?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_encrypted_notice</title>
        <link>http://www.epicsol.org/help/on_encrypted_notice?rev=1172946000</link>
        <description>on encrypted_notice

This event is generated when someone sends you an encrypted notice (that contains a ctcp sed), As with all notice hooks, you cannot send a msg or notice to a person over irc from within this hook. The default action of this event is to throw a general_notice event.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_encrypted_privmsg?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_encrypted_privmsg</title>
        <link>http://www.epicsol.org/help/on_encrypted_privmsg?rev=1172946000</link>
        <description>on [&lt;modes&gt;]encrypted_privmsg [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a MSG encrypted with CTCP SED.  This is how the ENCRYPT command normally works.
$0    nickname of message sender $1    target of message (the sender or channel) $2-   message received 
To clearly distinguish encrypted MSGs from unencrypted ones:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_error?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_error</title>
        <link>http://www.epicsol.org/help/on_error?rev=1172946000</link>
        <description>on [&lt;modes&gt;]error [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a server sends the client an ERROR message.
$0    server who sent the message (your server) $1-   the text of the error message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_exec?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_exec</title>
        <link>http://www.epicsol.org/help/on_exec?rev=1172946000</link>
        <description>on [&lt;modes&gt;]exec [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever an EXECed process generates output to standard output.
$0    the exec name or refnum that triggered the hook. $1-    a line of the process’s stdout 
To distinguish process output from other window output:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_exec_errors?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_exec_errors</title>
        <link>http://www.epicsol.org/help/on_exec_errors?rev=1172946000</link>
        <description>on [&lt;modes&gt;]exec_errors [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever an EXECed process produces output to standard error.
$0    process number or name of the EXECed process   $1-   a line of the process’s output to stderr                        
To distinguish process errors from other window output:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_exec_exit?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_exec_exit</title>
        <link>http://www.epicsol.org/help/on_exec_exit?rev=1172946000</link>
        <description>on [&lt;modes&gt;]exec_exit [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever an EXECed process finishes, either because it exits, it is killed by a signal, or you asked the client  to disown it.

This hook is always thrown, no matter what the value of  set notify_on_termination is.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_exec_prompt?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_exec_prompt</title>
        <link>http://www.epicsol.org/help/on_exec_prompt?rev=1172946000</link>
        <description>on [&lt;modes&gt;]exec_prompt [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever an EXECed process displays a “prompt”. More precisely, it is triggered when the process returns any line of output that is not terminated by a newline.  This is generally the case with interactive commands, such as nslookup(1).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_exit?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_exit</title>
        <link>http://www.epicsol.org/help/on_exit?rev=1172946000</link>
        <description>on [&lt;modes&gt;]exit [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered when the client is about to exit normally (from the QUIT command, etc.).  It is mostly useful for doing cleanup before exiting, such as saving any current settings.  It cannot be used to trap the QUIT command; the client will exit immediately after this hook is triggered..</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_flood?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_flood</title>
        <link>http://www.epicsol.org/help/on_flood?rev=1172946000</link>
        <description>on [&lt;modes&gt;]flood [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client’s internal flood detection code is activated.  The client is “flooded” when it receives a large number of messages (of any sort) in a relatively short period of time.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_general_notice?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_general_notice</title>
        <link>http://www.epicsol.org/help/on_general_notice?rev=1172946000</link>
        <description># $EPIC: on_general_notice.txt,v 1.3 2006/08/19 02:17:54 sthalik Exp $ 

on [&lt;modes&gt;]general_notice [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

A general_notice event is thrown whenever you receive a NOTICE.  The default action for general_notice is to throw one of the encrypted_notice, notice, oper_notice, public_notice, or server_notice events, as the case may be.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_general_privmsg?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_general_privmsg</title>
        <link>http://www.epicsol.org/help/on_general_privmsg?rev=1172946000</link>
        <description>#$EPIC: on_general_privmsg.txt,v 1.2 2006/08/19 02:15:40 sthalik Exp $ 

on [&lt;modes&gt;]general_privmsg [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a PRIVMSG from another client.
$0    nickname of message sender $1    target of PRIVMSG $2-   text of message 
If this hook is used in silent mode, the corresponding MSG, MSG_GROUP, PUBLIC, and PUBLIC_OTHER hooks will not be thrown.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_hook?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_hook</title>
        <link>http://www.epicsol.org/help/on_hook?rev=1172946000</link>
        <description>on [&lt;modes&gt;]hook [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the HOOK command is issued with the appropriate arguments.  Its sole purpose is to be hooked by HOOK.  It is useful for avoiding alias recursion.
$*   text to hook</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_idle?rev=1172946000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-03T12:20:00+00:00</dc:date>
        <title>on_idle</title>
        <link>http://www.epicsol.org/help/on_idle?rev=1172946000</link>
        <description>on [&lt;modes&gt;]idle [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client’s idle time reaches the given value, in minutes.  The idle time is reset when the client is given a command.
$0    minutes idle 
To automatically set the client away after being idle for 5 minutes:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_input?rev=1155953746">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:15:46+00:00</dc:date>
        <title>on_input</title>
        <link>http://www.epicsol.org/help/on_input?rev=1155953746</link>
        <description>on [&lt;modes&gt;]input [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a command is entered on the input line, or when text is sent to a channel or query.

This is a very powerful mechanism of the client.  Used intelligently, it permits a very fine degree of control over the text entered on the input line.  Used carelessly, and it can easily disable the client. Use with caution.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_invite?rev=1155953746">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:15:46+00:00</dc:date>
        <title>on_invite</title>
        <link>http://www.epicsol.org/help/on_invite?rev=1155953746</link>
        <description>on [&lt;modes&gt;]invite [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives an invitation to a channel.
$0    nickname inviting the client to a channel   $1    channel invited to                          
Customizing the appearance of the invitation:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_join?rev=1155953746">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:15:46+00:00</dc:date>
        <title>on_join</title>
        <link>http://www.epicsol.org/help/on_join?rev=1155953746</link>
        <description>on [&lt;modes&gt;]join [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client joins a channel, or whenever it observes another client joining a common channel.
$0    nickname of person joining channel $1    channel joined $2    address of person joining channel (same as $userhost()) $3    person joining’s channel status (on avalon 2.9 servers), could be either (+o) or (+v) 
To distinguish between the client and other users joining the channel:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_keybinding?rev=1157028799">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T07:53:19+00:00</dc:date>
        <title>on_keybinding</title>
        <link>http://www.epicsol.org/help/on_keybinding?rev=1157028799</link>
        <description>on [&lt;modes&gt;]keybinding [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a keybinding is activated.
$0    The keybinding that’s activated                         $1    Length of the sequence (future expansion - currently 0) $2    ASCII number of the key that’s activated it</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_kick?rev=1155953746">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:15:46+00:00</dc:date>
        <title>on_kick</title>
        <link>http://www.epicsol.org/help/on_kick?rev=1155953746</link>
        <description>on [&lt;modes&gt;]kick [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client observes another client (or itself!) being kicked from a channel.
$0    nickname of user kicked from channel      $1    nickname of user kicking $0 from channel  $2    channel kick observed on                  $3-   kick message                              
To distinguish who is being kicked on a channel:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_kill?rev=1155953746">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:15:46+00:00</dc:date>
        <title>on_kill</title>
        <link>http://www.epicsol.org/help/on_kill?rev=1155953746</link>
        <description>on [&lt;modes&gt;]kill [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever someone is kill(3)ed by an oper.
$0    server who sent the message (your server) $1    the victim being killed $2    the oper who issued the kill $3    server path to the oper $4-   reason for the kill 
To display kills in a more sane manner:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_list?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_list</title>
        <link>http://www.epicsol.org/help/on_list?rev=1155954999</link>
        <description>on [&lt;modes&gt;]list [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives server output from the LIST command.  Any individual line of output can trigger the hook.
$0    channel name $1    number of users on the channel $2-   channel topic (if any) 
To limit output to channels with a topic:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_mail?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_mail</title>
        <link>http://www.epicsol.org/help/on_mail?rev=1155954999</link>
        <description>on [&lt;modes&gt;]mail [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client detects that the user has new email locally.  It relies on MAIL being non-zero.
$0    number of new email messages $1    total number of email messages in user’s mailbox 
To keep the new mail message grammatically correct:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_mode?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_mode</title>
        <link>http://www.epicsol.org/help/on_mode?rev=1155954999</link>
        <description>on [&lt;modes&gt;]mode [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client observes a mode change on a channel, or whenever the client changes its modes.
$0    nickname of person issuing mode change $1    channel or nickname affected by mode change $2    modes changed $3-   arguments to modes (if any) 
To distinguish between user modes and channel modes:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_mode_stripped?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_mode_stripped</title>
        <link>http://www.epicsol.org/help/on_mode_stripped?rev=1155954999</link>
        <description>on [#][&lt;mode&gt;]mode_stripped [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is similar to the MODE hook, except it only hooks a single mode change at a time.  This hook relies on MODE_STRIPPER being turned on.  It is mostly useful in scripts that wish to evaluate each individual mode change.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_msg?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_msg</title>
        <link>http://www.epicsol.org/help/on_msg?rev=1155954999</link>
        <description># $Id: on_msg.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $



on [&lt;modes&gt;]msg [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a MSG from another client.
$0    nickname of message sender $1-   text of message 
The client does not permit automated responses to a MSG with another MSG. Such replies may use NOTICE instead.  Any attempt to use MSG within this hook will be automatically converted to a NOTICE.  The whole point of this is to prevent loops between…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_msg_group?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_msg_group</title>
        <link>http://www.epicsol.org/help/on_msg_group?rev=1155954999</link>
        <description>on [&lt;modes&gt;]msg_group [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is similar to the MSG hook, except it applies to messages sent to an undetermined group of people.  Typically, this is a server mask or hostmask, and is sent by an irc operator.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_names?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_names</title>
        <link>http://www.epicsol.org/help/on_names?rev=1155954999</link>
        <description>on [&lt;modes&gt;]names [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives server output from the NAMES command.
$0   channel name                                 $1-  nicknames of (visible) users on the channel  
This hook is not triggered by the implicit NAMES done when the client joins a channel.  Hook the 353 numeric instead.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_new_nickname?rev=1155955362">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:42:42+00:00</dc:date>
        <title>on_new_nickname</title>
        <link>http://www.epicsol.org/help/on_new_nickname?rev=1155955362</link>
        <description># $EPIC: on_new_nickname.txt,v 1.3 2006/08/19 02:42:38 sthalik Exp $ 

on [&lt;modes&gt;]new_nickname [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever your current nickname is no longer  acceptable and a new one must be created.  It is expected that you would use the NICK command in the &lt;action&gt; of this hook.  If you do not hook this, the client chooses a new one for you.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_nickname?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_nickname</title>
        <link>http://www.epicsol.org/help/on_nickname?rev=1155954999</link>
        <description>on [&lt;modes&gt;]nickname [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client observes a nickname change. It only hooks once per nick change, not once per channel.
$0 old nickname$1 new nickname
To distinguish the client from another user:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_note?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_note</title>
        <link>http://www.epicsol.org/help/on_note?rev=1155954999</link>
        <description>on [&lt;modes&gt;]note [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a NOTE.
$0       nickname of message sender                             $1       time the message was send (accurate +/- 60 seconds)    $2-      text of message                                        
To customize the display of irc NOTEs:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_notice?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_notice</title>
        <link>http://www.epicsol.org/help/on_notice?rev=1155954999</link>
        <description># $Id: on_notice.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $



on [&lt;modes&gt;]notice [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a NOTICE from another client.

This hook will not be thrown if a matching ON GENERAL_NOTICE hook is being used in silent mode. ON GENERAL_NOTICE and on NOTICE are mutually exclusive.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_notify_signoff?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_notify_signoff</title>
        <link>http://www.epicsol.org/help/on_notify_signoff?rev=1155954999</link>
        <description>on [&lt;modes&gt;]notify_signoff [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client detects that a nickname on its internal NOTIFY list has signed off from irc.
$0 nickname that signoff was detected for</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_notify_signon?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>on_notify_signon</title>
        <link>http://www.epicsol.org/help/on_notify_signon?rev=1156876398</link>
        <description>on [&lt;modes&gt;]notify_signon [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client detects that a nickname on its internal NOTIFY list has signed on to irc.
$0 nickname that signon was detected for                                                                              $1 user@host of person signing on (if set(4) notify_userhost_automatic is ON)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_numeric?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>on_numeric</title>
        <link>http://www.epicsol.org/help/on_numeric?rev=1171347600</link>
        <description>on [&lt;modes&gt;]on_numeric [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This on is triggered for every numeric that don’t have a more specific /on &lt;number&gt; hook.
$0    Numeric being thrown                      $1    The server which sent the message         $2    The message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_odd_server_stuff?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_odd_server_stuff</title>
        <link>http://www.epicsol.org/help/on_odd_server_stuff?rev=1155954999</link>
        <description>on [&lt;modes&gt;]odd_server_stuff [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This is easily the most flexible hook available in the client.  It allows any arbitrary string to be hooked from the server’s raw output.  It is useful for overriding the client’s default behavior when it otherwise wouldn’t permit it, or for hooking information when the available named hooks won’t do.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_oper_notice?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_oper_notice</title>
        <link>http://www.epicsol.org/help/on_oper_notice?rev=1155954999</link>
        <description>on [&lt;modes&gt;]oper_notice [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This is triggered whenever a global oper notice is received.
$0       server the notice came from      $1-      body of the message              
To alert the user of global oper notices:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_operwall?rev=1157031210">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-31T08:33:30+00:00</dc:date>
        <title>on_operwall</title>
        <link>http://www.epicsol.org/help/on_operwall?rev=1157031210</link>
        <description>on [&lt;modes&gt;]operwall [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives an OPERWALL event, used by EFNet servers. If you don’t hook this and happen to receive an OPERWALL event, it will be triggered as /on wallops.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_part?rev=1156565036">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-25T23:03:56+00:00</dc:date>
        <title>on_part</title>
        <link>http://www.epicsol.org/help/on_part?rev=1156565036</link>
        <description># $EPIC: on_part.txt,v 1.1 2006/08/26 04:03:56 sthalik Exp $



on [&lt;modes&gt;]part [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a client (the user’s or any other) is observed leaving a channel (but not signing off from irc).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_pong?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_pong</title>
        <link>http://www.epicsol.org/help/on_pong?rev=1155954999</link>
        <description>on [&lt;modes&gt;]pong [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a protocol PONG message.  Under normal circumstances, the sender will be a server. However, clients are also allowed to send PONG messages to each other. Since there is never any reason for a client to send a PONG to another client, this hook can be useful for blocking PONG floods.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_public?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_public</title>
        <link>http://www.epicsol.org/help/on_public?rev=1155954999</link>
        <description>on [&lt;modes&gt;]public [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a regular public message is sent to the client’s current channel by someone else also on the channel.
$0     nickname sending message     $1     channel sent to              $2-    text of message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_public_msg?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_public_msg</title>
        <link>http://www.epicsol.org/help/on_public_msg?rev=1155954999</link>
        <description>on [&lt;mode&gt;]public_msg [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a public message in a channel from someone not actually in the channel.
$0     nickname sending message   $1     channel sent to            $2-    text of message            
To customize how these messages are displayed:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_public_notice?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_public_notice</title>
        <link>http://www.epicsol.org/help/on_public_notice?rev=1155954999</link>
        <description># $EPIC: on_public_notice.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $ 

on [&lt;modes&gt;]public_notice [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a NOTICE is sent to any channel the client is on from someone not actually on that channel.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_public_other?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_public_other</title>
        <link>http://www.epicsol.org/help/on_public_other?rev=1155954999</link>
        <description>on [&lt;modes&gt;]public_other [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client observes a message sent to any channel it is on that isn’t its current channel, from someone else on that channel.
$0 nickname sending message$1 channel sent to$2- text of message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_raw_irc?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_raw_irc</title>
        <link>http://www.epicsol.org/help/on_raw_irc?rev=1155954999</link>
        <description>on [&lt;modes&gt;]raw_irc [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This is easily the most flexible hook available in the client.  It allows any arbitrary string to be hooked from the server’s raw output.  It is useful for overriding the client’s default behavior when it otherwise wouldn’t permit it, or for hooking information when the available named hooks won’t do.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_redirect?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_redirect</title>
        <link>http://www.epicsol.org/help/on_redirect?rev=1155954999</link>
        <description>on [&lt;modes&gt;]redirect [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever something is redirected.
$0 Target to which the text is about to be sent$1- The actual text to be sent</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_action?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_action</title>
        <link>http://www.epicsol.org/help/on_send_action?rev=1155954999</link>
        <description># $EPIC: on_send_action.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $ 

on [&lt;modes&gt;]send_action [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client sends a CTCP ACTION to a channel or to another person.
$0 target of the ACTION (nickname or channel)$1- text of message sent
To display separate messages for public and private actions:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_ctcp?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_ctcp</title>
        <link>http://www.epicsol.org/help/on_send_ctcp?rev=1155954999</link>
        <description>on [&lt;modes&gt;]send_ctcp [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client sends a CTCP request or reply to another client.
$0 “PRIVMSG” for requests, “NOTICE” for replies$1 nick the CTCP is being sent to$2 type of CTCP being sent$3- optional arguments to the CTCP being sent
To show the user when a CTCP request is sent:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_dcc_chat?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_dcc_chat</title>
        <link>http://www.epicsol.org/help/on_send_dcc_chat?rev=1155954999</link>
        <description>on [&lt;modes&gt;]send_dcc_chat [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client sends a message to another client across a DCC CHAT connection.
$0 nickname of recipient of message sent$1- text of message sent</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_msg?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_msg</title>
        <link>http://www.epicsol.org/help/on_send_msg?rev=1155954999</link>
        <description>on [&lt;modes&gt;]send_msg [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client sends a MSG to another user. It is only triggered when sending messages to individual clients, not to channels.
$0 nickname message is sent to$1- text of message sent</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_notice?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_notice</title>
        <link>http://www.epicsol.org/help/on_send_notice?rev=1155954999</link>
        <description>on [&lt;modes&gt;]send_notice [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client sends a NOTICE message to a channel or another client.
$0 nickname or channel the NOTICE is sent to$1- text of message sent</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_public?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_public</title>
        <link>http://www.epicsol.org/help/on_send_public?rev=1155954999</link>
        <description>on [&lt;modes&gt;]send_public [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client sends a regular, public message to any channel it is on.
$0 the channel the message is sent to$1- text of message sent</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_send_to_server?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_send_to_server</title>
        <link>http://www.epicsol.org/help/on_send_to_server?rev=1155954999</link>
        <description>on [&lt;modes&gt;]send_to_server [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook, when set, is triggered whenever the client sends data to the server that matches the hook.  It is useful for catching raw messages destined for the server and redefining them.  One such use is with DCC, as it offers no convenient way to send a raw request.  By using the silent mode, the default action (sending data to the server) is suppressed, allowing any arbitrary command to be replaced.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_server_established?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_server_established</title>
        <link>http://www.epicsol.org/help/on_server_established?rev=1155954999</link>
        <description># $EPIC: on_server_established.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $ 

on [&lt;modes&gt;]server_established [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered as soon as a TCP connection to a server is established.  This hook differs from “connect” hook in that the “connect” hook isn’t triggered until the 003 server line is received.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_server_lost?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_server_lost</title>
        <link>http://www.epicsol.org/help/on_server_lost?rev=1155954999</link>
        <description>on [&lt;modes&gt;]server_lost [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client is disconnected from any server for any reason.
$0 server refnum$1 server name$2- reason for disconnect. usually the same as your QUIT(1) message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_server_notice?rev=1155955362">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:42:42+00:00</dc:date>
        <title>on_server_notice</title>
        <link>http://www.epicsol.org/help/on_server_notice?rev=1155955362</link>
        <description># $EPIC: on_server_notice.txt,v 1.3 2006/08/19 02:42:38 sthalik Exp $ 

on [&lt;modes&gt;]server_notice [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This event is thrown any time any server sends you a NOTICE. Because remote servers can send you notices, and because it’s not possible to know all of the server names on a network, it is assumed if the sender has a dot (”.”) in their name, it’s a servername, and if there isn’t, then it is a normal irc nickname. If you’re on a network that has a ser…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_server_status?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>on_server_status</title>
        <link>http://www.epicsol.org/help/on_server_status?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_set?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>on_set</title>
        <link>http://www.epicsol.org/help/on_set?rev=1156876398</link>
        <description>on [&lt;modes&gt;]set [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a /set is issued.
$0   name of variable to be set. will be “set-error” if an invalid SET variable was specified                                         $1-  value the variable will be set to. will be “No such variable “FOO”“, where FOO is the invalid SET variable if $0 is “set-error”  
To make sure set security stays on:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_signoff?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_signoff</title>
        <link>http://www.epicsol.org/help/on_signoff?rev=1155954999</link>
        <description>on [&lt;modes&gt;]signoff [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client observes another client on a common channel signing off from irc.  It only hooks once per user, not once per channel.
$0 nickname of person signing off$1- signoff message
This hook is only triggered for other users.  To hook your own signoff, use the EXIT hook.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_silence?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_silence</title>
        <link>http://www.epicsol.org/help/on_silence?rev=1155954999</link>
        <description>on [&lt;modes&gt;]silence [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a reply from the server from a SILENCE command.
$0 a ‘+’ if a pattern was added, ‘-’ if one was removed$1 the pattern silenced (or unsilenced)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_ssl_server_cert?rev=1155955362">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:42:42+00:00</dc:date>
        <title>on_ssl_server_cert</title>
        <link>http://www.epicsol.org/help/on_ssl_server_cert?rev=1155955362</link>
        <description># $EPIC: on_ssl_server_cert.txt,v 1.3 2006/08/19 02:42:38 sthalik Exp $ 

on [&lt;modes&gt;]ssl_server_cert [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered after SSL negotation with an irc server has  successfully completed.
$0 The file descriptor for the server [NOT THE SERVER REFNUM]$1 The certificate subject, passed through $urlencode(). Use $urldecode($1) to recover the cert subject. $2 The certificate issuer, passed through $urlencode() Use $urldecode($2) to recover the cert issuer.…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_status_update?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_status_update</title>
        <link>http://www.epicsol.org/help/on_status_update?rev=1155954999</link>
        <description>on [&lt;modes&gt;]status_update [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the status bar of a visible window in dumb mode is updated.
$0 Refnum of the window whose status bar was updated$1 Which status bar has changed, 0 or 1$2- The actual status bar that has been updated</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_switch_channels?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_switch_channels</title>
        <link>http://www.epicsol.org/help/on_switch_channels?rev=1155954999</link>
        <description># $EPIC: on_switch_channels.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $



on [&lt;modes&gt;]switch_channels [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the current channel is switched.
$0 reference number of the window in which the switch occurred$1 channel you were talking to$2 channel you are now talking to</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_switch_windows?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_switch_windows</title>
        <link>http://www.epicsol.org/help/on_switch_windows?rev=1155954999</link>
        <description>on [&lt;modes&gt;]switch_windows [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client changes what it thinks your “current” window is in any given context.
$0 the old screen number$1 the old window number$2 the new screen number$3 the new window number
Note that the window might change through forces other than the window keybindings.  You can get a pretty good idea when this happens, though, because $0 and $2 will be different.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_timer?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_timer</title>
        <link>http://www.epicsol.org/help/on_timer?rev=1155954999</link>
        <description>on [#][&lt;mode&gt;]timer [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the specified time (or time glob pattern) matches the current time.  The time may be in one of two formats: 
Format             Description                                            hh:mm&lt;am|pm&gt;   0 &lt;= hh &lt;= 12, 0 &lt;= mm &lt;= 59, am or pm set accordingly hh:mm              0 &lt;= hh &lt;= 23, 0 &lt;= mm &lt;= 59                           $0 current time (format depends on CLOCK_24HOUR setting)
To inform the user of the…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_topic?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_topic</title>
        <link>http://www.epicsol.org/help/on_topic?rev=1155954999</link>
        <description>on [&lt;modes&gt;]topic [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered when the topic is changed on any channel the client is on.
$0 nickname of person changing topic$1 channel topic was changed on$2- new topic</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_unknown_command?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>on_unknown_command</title>
        <link>http://www.epicsol.org/help/on_unknown_command?rev=1171347600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_unload?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_unload</title>
        <link>http://www.epicsol.org/help/on_unload?rev=1155954999</link>
        <description>on [&lt;modes&gt;]unload [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the unload(5) command is issued to unload a packaged script.
$* the parameters passed to the /package command
(NOTE that passing more than one argument to /package may cause future incompatibilities, and should be avoided at all costs)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_wall?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_wall</title>
        <link>http://www.epicsol.org/help/on_wall?rev=1155954999</link>
        <description>on [#][&lt;mode&gt;]wall [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook used to be triggered whenever the client received a WALL message.  WALL is no longer in use on any known irc network, and this hook is but a relic of days long gone.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_wallop?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_wallop</title>
        <link>http://www.epicsol.org/help/on_wallop?rev=1155954999</link>
        <description>on [&lt;modes&gt;]wallop [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever the client receives a WALLOPS message (a message sent to all irc operators).
$0 nickname of the message sender$1 a ‘*’ if the sender is an operator, ‘S’ if the sender is a server$2- text of message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_who?rev=1155955464">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:44:24+00:00</dc:date>
        <title>on_who</title>
        <link>http://www.epicsol.org/help/on_who?rev=1155955464</link>
        <description>on [#][&lt;mode&gt;]who [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered when the client receives server output from the WHO command.  Each line received can trigger the hook.
$0 channel the user is on, of ‘*’ if none or if it is private$1 nickname of user$2 status of user: &lt;G|H&gt;[*][@|+]    ‘G’ for gone (away), ‘H’ for here (not away), ‘*’ for irc operator, ‘@’ for channel operator, ‘+’ for voice status $3 username portion of user’s address$4 hostname portion of …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_window?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_window</title>
        <link>http://www.epicsol.org/help/on_window?rev=1155954999</link>
        <description>on [&lt;modes&gt;]window [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever output to any window matches any existing WINDOW hook.  Extreme care should be taken when using this hook to redefine messages, as an ECHO command inside it will also be hooked by it.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_window_beforekill?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_window_beforekill</title>
        <link>http://www.epicsol.org/help/on_window_beforekill?rev=1155954999</link>
        <description>on [&lt;modes&gt;]window_beforekill [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered just before a window is killed.  It is permissible to query any data you want about the window, but it is NOT PERMISSIBLE to try to change anything about the window, particularly its visibility.  If you try to change the window, you may crash the client.  Use /DEFER to be on the safe side.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_window_command?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_window_command</title>
        <link>http://www.epicsol.org/help/on_window_command?rev=1155954999</link>
        <description># $EPIC: on_window_command.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $ 

on [&lt;modes&gt;]window_command [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered each time a /WINDOW command is executed, to inform you of any changes to the current operative window.  This can be useful  if you need to prep a window before commands are executed on it.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_window_create?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_window_create</title>
        <link>http://www.epicsol.org/help/on_window_create?rev=1155954999</link>
        <description>on [&lt;modes&gt;]window_create [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered whenever a new window is created. This enables defaults to be given to each window.
$0 reference number of created window /* doubles the status bar for each new window */
 on -window_create &quot;*&quot; {
    window double on
 }</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_window_kill?rev=1155954999">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:36:39+00:00</dc:date>
        <title>on_window_kill</title>
        <link>http://www.epicsol.org/help/on_window_kill?rev=1155954999</link>
        <description># $EPIC: on_window_kill.txt,v 1.2 2006/08/19 02:36:28 sthalik Exp $ 

on [&lt;modes&gt;]window_kill [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered after a window has been killed.  By the time that this is triggered, the window has been irrevocably destroyed, and cannot be used.  You can use this hook to clean up after your own data that may be keyed on the window’s refnum.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_window_server?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>on_window_server</title>
        <link>http://www.epicsol.org/help/on_window_server?rev=1171347600</link>
        <description># $EPIC: on_window_server.txt,v 1.2 2007/02/13 06:05:45 jnelson Exp $ 

on [&lt;modes&gt;]window_server [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This hook is triggered each time a window changes its server association for any reason whatsoever. 

The server refnum -2 is special, and it means the window has disconnected; it is no longer associated with any server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/on_yell?rev=1155955362">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T21:42:42+00:00</dc:date>
        <title>on_yell</title>
        <link>http://www.epicsol.org/help/on_yell?rev=1155955362</link>
        <description>on [&lt;modes&gt;]yell [&lt;serial#&gt;] [-|^]&lt;match&gt; { &lt;action&gt; }

This is hooked by fairly useless but necessary in beta yell()s. They are present in the client for debugging purposes, and scripters may not want them to appear. ON ^yell will suppress their output.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/onchannel?rev=1155958514">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:35:14+00:00</dc:date>
        <title>onchannel</title>
        <link>http://www.epicsol.org/help/onchannel?rev=1155958514</link>
        <description># $EPIC: onchannel.txt,v 1.4 2006/08/19 03:35:12 sthalik Exp $ 

$onchannel()      (First Action) 
 $onchannel(&lt;channel&gt;)   (First Action) 
 $onchannel(&lt;nick&gt; &lt;channel&gt;)  (Second Action)

	*  There are two different actions provided by this function.  The first action is to provide a list of nicknames that are on a channel.  The section action is to tell you whether a particular person is on a particular channel.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/open?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>open</title>
        <link>http://www.epicsol.org/help/open?rev=1172803800</link>
        <description># $EPIC: open.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$open(&lt;file&gt; R|W)

This functions allows the client to open an arbitrary file for reading or writing.  Write mode appends to the file.  The function returns a file descriptor for the open file; the file descriptor is an integer.  Tilde- expansion is permitted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/oper?rev=1155958382">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:33:02+00:00</dc:date>
        <title>oper</title>
        <link>http://www.epicsol.org/help/oper?rev=1155958382</link>
        <description>oper [&lt;nick&gt; [&lt;password&gt;]]

The OPER command is used to gain irc operator status on the current server, with the stipulation that the specified (or current) nickname and password match an O: line entry in the server’s configuration. If a password is not specified, the client will prompt for one.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/output-help?rev=1179609176">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-19T16:12:56+00:00</dc:date>
        <title>output-help</title>
        <link>http://www.epicsol.org/help/output-help?rev=1179609176</link>
        <description># $EPIC: output-help.txt,v 1.1 2007/05/19 21:12:56 jnelson Exp $ 

This help file discusses various problems you might have with getting output to work properly, and how to fix them.

About terminal emulators

A terminal emulator is the computer program that handles input and output  between you, the user, and a login shell (on a unix system).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/outputinfo?rev=1155958606">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:36:46+00:00</dc:date>
        <title>outputinfo</title>
        <link>http://www.epicsol.org/help/outputinfo?rev=1155958606</link>
        <description># $EPIC: outputinfo.txt,v 1.4 2006/08/19 03:36:44 sthalik Exp $ 

$outputinfo()

	*  This function does not take any arguments; they are ignored.
	*  The return value is the current output display context
	*  The current output display context is the mechanism by which the program figures out what window output should go to.
	*  Throughout the entire client, the tuple (server refnum, lastlog level) can map to only one window (but perhaps not to any window).
	*  The current output display context…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/package?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>package</title>
        <link>http://www.epicsol.org/help/package?rev=1156876398</link>
        <description>package &lt;name&gt;

The PACKAGE command allows a script to “group” all of the assigns, aliases, binds, ON hooks (and stubs) under a common package name. When the PACKAGE command is used, any alias/assigns/on that are registered until the end of the file are given the current package name. The package name can be changed anywhere in a script, even if PACKAGE had been previously used. However, packages only last until the end of the file, they never propagate upwards. Scripts that are loaded by ot…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pad?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>pad</title>
        <link>http://www.epicsol.org/help/pad?rev=1172803800</link>
        <description># $EPIC: pad.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

$pad(&lt;width&gt; &lt;char&gt; &lt;text&gt;)

	*  If the &lt;width&gt; argument is omitted the empty string is returned.
	*  If the &lt;char&gt; argument is omitted the empty string is returned.
	*  The &lt;width&gt; argument may be positive or negative.
	*  Although the &lt;char&gt; argument can be a string, only the first character is actually used.
	*  If the absolute value of &lt;width&gt; is less than the length of &lt;text&gt;, then &lt;text&gt; is returned.
	*  The number of “neccesary …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/parsekey?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>parsekey</title>
        <link>http://www.epicsol.org/help/parsekey?rev=1155959901</link>
        <description>parsekey &lt;key function&gt;

This command allows direct access to the functions normally bound to special keys via the BIND command.  It is useful for using rarely- used key functions that are not bound to a particular key.  Any of the functions that may be bound to a key may be used.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/part?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>part</title>
        <link>http://www.epicsol.org/help/part?rev=1155959901</link>
        <description># $EPIC: part.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

part &lt;channel&gt;|* [&lt;part message&gt;]

When you wish to leave a channel, you “PART” it.  After you have parted a channel you are no longer a member of that channel, you are no longer a channel operator or a channel voice, and you will no longer receive any messages sent to the channel.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pass?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>pass</title>
        <link>http://www.epicsol.org/help/pass?rev=1172803800</link>
        <description># $EPIC: pass.txt,v 1.3 2006/08/19 04:05:34 sthalik Exp $ 

$strip(&lt;chars&gt; &lt;text&gt;) 
 $pass(&lt;chars&gt; &lt;text&gt;)

	*  If the &lt;chars&gt; argument is omitted the empty string is returned.
	*  If the &lt;text&gt; argument is omitted the empty string is returned.
	*  The return value for $strip() is a copy of &lt;text&gt; from which every instance of any character in &lt;chars&gt; has been removed.
	*  The return value for $pass() is a copy of &lt;text&gt; from which every instance of any character not in &lt;chars&gt; has been removed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/paste?rev=1171939800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T20:50:00+00:00</dc:date>
        <title>paste</title>
        <link>http://www.epicsol.org/help/paste?rev=1171939800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pattern?rev=1179193800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-14T20:50:00+00:00</dc:date>
        <title>pattern</title>
        <link>http://www.epicsol.org/help/pattern?rev=1179193800</link>
        <description># $EPIC: pattern.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

$pattern(&lt;pattern&gt; &lt;word list&gt;)

	*  If the &lt;pattern&gt; argument is omitted the empty string is returned.
	*  This function returns a space separated word list of all of the words in &lt;word list&gt; that are matched by &lt;pattern&gt;.
	*  This is the complement to $filter(), and the inverse of $rpattern().
	*  Double quoted words are honored, but the double quotes will be lost in the return value.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/patterns?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>patterns</title>
        <link>http://www.epicsol.org/help/patterns?rev=1155959901</link>
        <description>Pattern Matching

 Literally, any string is a pattern.  In general, though, a pattern is a string intended to match, or be matched by, one or more other strings.  The pattern will usually contain one or more wildcards, but it doesn’t need to.

The following wildcard characters are supported:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pause?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>pause</title>
        <link>http://www.epicsol.org/help/pause?rev=1155959901</link>
        <description># $EPIC: pause.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

pause &lt;seconds&gt;

PAUSE performs a nonblocking sleep for &lt;seconds&gt; seconds.  During the nonblocking sleep, the client performs all actions as normal, except that PAUSE will not return until &lt;seconds&gt; seconds have elapsed.  Because things might have occurred during the nonblocking sleep, it not guaranteed that everything is as it was when the PAUSE started.  Servers may have closed, the input line may have changed, dccs may have finished…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/perl?rev=1153071059">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-16T12:30:59+00:00</dc:date>
        <title>perl</title>
        <link>http://www.epicsol.org/help/perl?rev=1153071059</link>
        <description>This is a disambiguation page.  Do you mean the perl command or the perl function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/perl_command?rev=1154062800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-28T00:00:00+00:00</dc:date>
        <title>perl_command</title>
        <link>http://www.epicsol.org/help/perl_command?rev=1154062800</link>
        <description>#$EPIC: perl_command.txt,v 1.3 2006/07/28 04:14:52 jnelson Exp $ 

perl {perl statement}

If EPIC was linked with an embedded perl interpreter, the perl statement shall be executed by perl.  If EPIC was not linked against perl, then no action shall take place.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/perl_function?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>perl_function</title>
        <link>http://www.epicsol.org/help/perl_function?rev=1156876398</link>
        <description># $EPIC: perl_function.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$perl(perl statement)

If EPIC was linked with an embedded perl interpreter, the perl statement shall be executed by perl.  If EPIC was not linked against perl, then no  action shall take place.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/perlcall?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>perlcall</title>
        <link>http://www.epicsol.org/help/perlcall?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/perlxcall?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>perlxcall</title>
        <link>http://www.epicsol.org/help/perlxcall?rev=1172803800</link>
        <description># $EPIC: perlxcall.txt,v 1.4 2006/08/29 18:33:16 sthalik Exp $ 

$perlcall(&lt;subroutine&gt; [&lt;text&gt;]) 
 $perlxcall(&lt;subroutine&gt; [&lt;array-in&gt; [&lt;array-out&gt; [&lt;index&gt; [&lt;text&gt;]]]])

These functions call a given subroutine in the embedded perl interpreter and return the subroutines return value.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pf_loader?rev=1179193800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-14T20:50:00+00:00</dc:date>
        <title>pf_loader</title>
        <link>http://www.epicsol.org/help/pf_loader?rev=1179193800</link>
        <description>load -pf &lt;file&gt; [&lt;file&gt; ...]

The pf loader (”pf” stands for “pre-formatted”) reads in a text file  that contains one big block of code and executes it.

All of the scripts that come with epic5 are in pf-format.  It is expected that most, if not all script packs that work with epic5 will be in pf-format. You should switch, because it’s much less painful for you this way.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pid?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>pid</title>
        <link>http://www.epicsol.org/help/pid?rev=1155959901</link>
        <description># $EPIC: pid.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

$pid()

	*  This function ignores its arguments
	*  This function returns the current process id of EPIC.

If you wanted to send a signal to your epic client, then you would need its process id.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ping?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>ping</title>
        <link>http://www.epicsol.org/help/ping?rev=1155959901</link>
        <description># $EPIC: ping.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

ping &lt;nickname&gt; ping &lt;channel&gt;

Lag is a way of life on irc.  “Lag” is determined by how much time it takes a message to get from the sender to the recipient.  The more lag, the longer it takes for someone to get your messages.  Sometimes you want to see just how long it will take for a message to get to someone else and back.  The PING command sends someone a specially crafted message asking them to send the message back.  When you…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pipe?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>pipe</title>
        <link>http://www.epicsol.org/help/pipe?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the pipe function or the pipe script?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pipe_function?rev=1155959901">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T22:58:21+00:00</dc:date>
        <title>pipe_function</title>
        <link>http://www.epicsol.org/help/pipe_function?rev=1155959901</link>
        <description># $EPIC: pipe_function.txt,v 1.2 2006/08/19 03:58:07 sthalik Exp $ 

$pipe(&lt;program&gt;)

This function executes &lt;program&gt; and returns its output. It is defined in the pipe(8) script. 

It’s an easy way to grab the output of a program quickly.

&lt;program&gt;’s output</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pipe_script?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>pipe_script</title>
        <link>http://www.epicsol.org/help/pipe_script?rev=1156876398</link>
        <description># $EPIC: pipe_script.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

load pipe

This script implements the pipe(6) function to capture output from an /exec‘d command and return in a function.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pop?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>pop</title>
        <link>http://www.epicsol.org/help/pop?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the pop command or the pop function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pop_command?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>pop_command</title>
        <link>http://www.epicsol.org/help/pop_command?rev=1156876398</link>
        <description># $EPIC: pop_command.txt,v 1.4 2006/08/29 18:22:56 sthalik Exp $ 

pop &lt;variable name&gt;

The pop command removes the final word from the  value of &lt;variable name&gt;.  DOUBLE QUOTED WORDS ARE NOT SUPPORTED (yet). If the value of &lt;variable name&gt; contains only one word, then the  variable is unset.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pop_function?rev=1171738200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T12:50:00+00:00</dc:date>
        <title>pop_function</title>
        <link>http://www.epicsol.org/help/pop_function?rev=1171738200</link>
        <description># $EPIC: pop_function.txt,v 1.4 2006/08/29 18:33:16 sthalik Exp $ 

$pop(&lt;variable name&gt;) 
 $pop(&lt;word list&gt;)

	*  If no arguments are provided, the empty string is returned.
	*  If the argument consists of only one word, it is taken as &lt;variable name&gt;.
	*  If more than one arguments are provided, they are taken as &lt;word list&gt;.
	*  If a &lt;word list&gt; is provided, the return value is the last word in &lt;word list&gt;.  DOUBLE QUOTED WORDS ARE NOT SUPPORTED.  (This may change in the future.)
	*  If &lt;vari…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ppid?rev=1156886400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T16:20:00+00:00</dc:date>
        <title>ppid</title>
        <link>http://www.epicsol.org/help/ppid?rev=1156886400</link>
        <description># $EPIC: ppid.txt,v 1.2 2006/08/29 21:02:33 jnelson Exp $ 

$ppid()

This function ignores its argument and returns the parent process id as returned by the ppid(2) system call.

If you wanted to send a signal to the shell that ran your epic client,  then you would need its process id.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/prefix?rev=1155960338">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T23:05:38+00:00</dc:date>
        <title>prefix</title>
        <link>http://www.epicsol.org/help/prefix?rev=1155960338</link>
        <description># $EPIC: prefix.txt,v 1.4 2006/08/19 04:05:34 sthalik Exp $ 

$prefix(&lt;word list&gt;)

	*  If the &lt;word list&gt; argument is omitted the empty string is returned.
	*  The return value of this function is whatever string is the common initial substring (CIS) of all of the words in &lt;word list&gt;.  If there is no CIS in &lt;word list&gt;, the empty string is returned.
	*  This function uses an O(M*N) algorithm where M is the number of words in &lt;word list&gt; and N is the length of the first word in &lt;word list&gt;. Tak…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/pretend?rev=1155960338">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T23:05:38+00:00</dc:date>
        <title>pretend</title>
        <link>http://www.epicsol.org/help/pretend?rev=1155960338</link>
        <description># $EPIC: pretend.txt,v 1.3 2006/08/19 04:05:34 sthalik Exp $ 

pretend &lt;arguments&gt;

The PRETEND command allows the client to “pretend” it received the given arguments from the server.  It is intended only to be used inside a hook action.  One possible use for this might be a highly customized scripted DCC system.  It is mostly only of use with on RAW_IRC.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/printlen?rev=1155960338">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T23:05:38+00:00</dc:date>
        <title>printlen</title>
        <link>http://www.epicsol.org/help/printlen?rev=1155960338</link>
        <description># $EPIC: printlen.txt,v 1.3 2006/08/19 04:05:34 sthalik Exp $ 

$printlen(&lt;text&gt;)

	*  The return value is the number of printable characters in &lt;text&gt;.
	*  ANSI escape sequences will be counted as printable characters by this function! 
 Convert &lt;text&gt; via $stripcrap(ANSI &lt;text&gt;) first if you suspect it may contain ansi escape sequences.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/programming?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>programming</title>
        <link>http://www.epicsol.org/help/programming?rev=1156876398</link>
        <description>This short (very short) document describes EPIC’s programming language (some would argue it’s but a scripting language) and how to use it.

The first thing to remember about scripts is that command characters are not required for commands!  In fact, their use is discouraged, as it only makes more work for the client when parsing the command.  There is, of course, an exception to this rule (but only one).  Because the client allows commands to be overloaded by aliases, there needs to be a way…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/push?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>push</title>
        <link>http://www.epicsol.org/help/push?rev=1152593863</link>
        <description>This is a disambiguation page.  Do you mean the push command or the push function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/push_command?rev=1174668600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-23T11:50:00+00:00</dc:date>
        <title>push_command</title>
        <link>http://www.epicsol.org/help/push_command?rev=1174668600</link>
        <description>push &lt;variable name&gt; &lt;word&gt; 
 pop  &lt;variable name&gt;

PUSH appends the given word (or words) to the given variable, padded with a single space.  The variable name itself may not contain a leading ‘$’; the command uses the variable itself, not the expanded contents.  If the variable does not exist, it is created containing the given word(s) (just as if ASSIGN were used).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/push_function?rev=1174668600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-23T11:50:00+00:00</dc:date>
        <title>push_function</title>
        <link>http://www.epicsol.org/help/push_function?rev=1174668600</link>
        <description># $EPIC: push_function.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$push(&lt;variable name&gt; &lt;data&gt;)

	*  If the &lt;variable name&gt; argument is omitted the empty string is returned.
	*  &lt;variable name&gt; should be the name of an ASSIGN variable.
	*  If the rvalue of &lt;variable name&gt; is the empty string, then the rvalue of &lt;variable name&gt; is set to &lt;data&gt;.
	*  Otherwise, the rvalue of &lt;variable name&gt; is set to the present value of &lt;variable name&gt; plus a space, plus &lt;data&gt;.
	*  The new rvalue of &lt;variable…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/query?rev=1155960510">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T23:08:30+00:00</dc:date>
        <title>query</title>
        <link>http://www.epicsol.org/help/query?rev=1155960510</link>
        <description># $EPIC: query.txt,v 1.2 2006/08/19 04:08:24 sthalik Exp $ 

query 
 query &lt;nickname&gt; 
 query &lt;channel&gt; 
 query =&lt;dcc chat peer&gt; 
 query %&lt;process id|process name&gt; 
 query /&lt;command&gt;

The QUERY command is exactly the same as WINDOW QUERY. See the help file for WINDOW QUERY(4) for details.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/querywin?rev=1156129518">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T22:05:18+00:00</dc:date>
        <title>querywin</title>
        <link>http://www.epicsol.org/help/querywin?rev=1156129518</link>
        <description># $EPIC: querywin.txt,v 1.3 2006/08/21 03:05:12 sthalik Exp $ 

$querywin(&lt;target&gt;) 
 $querywin(&lt;target&gt; &lt;server refnum&gt;)

This function returns the window owning the query target &lt;target&gt;, or “-1” if there are no queries for &lt;target&gt;. An optional server refnum argument may be specified in order to obtain the query window for a target on a particular server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/queue?rev=1155960510">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-18T23:08:30+00:00</dc:date>
        <title>queue</title>
        <link>http://www.epicsol.org/help/queue?rev=1155960510</link>
        <description># $EPIC: queue.txt,v 1.2 2006/08/19 04:08:24 sthalik Exp $ 

queue [&lt;flag&gt;] &lt;name&gt; [&lt;number&gt;] [&lt;commands&gt;]

QUEUE allows for a sort of batch processing in ircII-EPIC.  It is a convenient mechanism for preparing to execute a command at a later, undetermined time.  It can also be used as a sort of dynamically growing alias.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/quit?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>quit</title>
        <link>http://www.epicsol.org/help/quit?rev=1156876398</link>
        <description># $EPIC: quit.txt,v 1.4 2006/08/29 18:22:56 sthalik Exp $ 

quit [&lt;quit message&gt;]

When you are all done with talking, you can use the QUIT command to  exit from IRC and go back to your shell.   

	*  All of your dcc connections are terminated
	*  Your quit message is created, either &lt;quit message&gt; or set quit_message.
	*  on exit is thrown.
	*  TCL, Perl, and Ruby finalizers (if any) are run.
	*  You are disconnected from every server using your quit message.
	*  All of your logfiles are closed…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/quote?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>quote</title>
        <link>http://www.epicsol.org/help/quote?rev=1152593863</link>
        <description>quote &lt;rfc1459-statement&gt;

The quote command behaves the same as xquote without any options.

To send a PRIVMSG to foo:
    quote PRIVMSG foo :text of message</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/quoting_hell?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>quoting_hell</title>
        <link>http://www.epicsol.org/help/quoting_hell?rev=1184106000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/qword?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>qword</title>
        <link>http://www.epicsol.org/help/qword?rev=1172803800</link>
        <description># $EPIC: qword.txt,v 1.3 2007/03/02 02:32:04 jnelson Exp $ 

$qword(&lt;index&gt; &lt;list&gt;)

	*  If the &lt;index&gt; argument is omitted, the empty string is returned.
	*  If the &lt;list&gt; argument is omitted, the empty string is returned.
	*  The &lt;index&gt; argument is taken as an integer number.
	*  If &lt;index&gt; is a negative number, the empty string is returned.
	*  The return value is the &lt;index&gt;th word in &lt;list&gt;, counting from zero.
	*  Remember that &lt;list&gt; is always a list of words.
	*  In either case, if the …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rand?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>rand</title>
        <link>http://www.epicsol.org/help/rand?rev=1155967649</link>
        <description># $EPIC: rand.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$rand(&lt;maximum&gt;)

	*  If &lt;maximum&gt; is omitted, this function returns the empty string.
	*  Otherwise, a “random number” that fits in an “unsigned long” on your machine is created:
		*  If &lt;maximum&gt; is zero, the “random number” is returned as is.
		*  Otherwise, the return value is “as if” you had done the following: 
 ${rand(0) % &lt;maximum&gt;}</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/random_numbers?rev=1171737223">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T12:33:43+00:00</dc:date>
        <title>random_numbers</title>
        <link>http://www.epicsol.org/help/random_numbers?rev=1171737223</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/randread?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>randread</title>
        <link>http://www.epicsol.org/help/randread?rev=1172803800</link>
        <description># $EPIC: randread.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$randread(&lt;filename&gt;)

This function reads a random line from the specified &lt;filename&gt;.

This function has many novelty uses: random messages for /quit, /kick, /part, or /topic.

The empty string is returned on error (the file does not exist, the file is empty, or the file cannot be read).  Otherwise, a random line from the file is returned.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rbind?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>rbind</title>
        <link>http://www.epicsol.org/help/rbind?rev=1152593863</link>
        <description>rbind &lt;bind function&gt;

The rbind command shows you all of the key sequences that are  bound to the &lt;bind function&gt;.  This is useful if you know  what &lt;bind function&gt; you want to use but you don’t know what is  bound to it.

# $EPIC: rbind.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/read?rev=1181017200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-06-04T23:20:00+00:00</dc:date>
        <title>read</title>
        <link>http://www.epicsol.org/help/read?rev=1181017200</link>
        <description># $EPIC: read.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$read(&lt;fd&gt; [&lt;length&gt;])

This function is used to read data from a file pointed to by the given file descriptor.  The file descriptor is returned when the file is opened for reading with the $open() function.  If a second argument is passed, that many bytes are read and returned; otherwise, it reads up to the next newline.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/realpath?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>realpath</title>
        <link>http://www.epicsol.org/help/realpath?rev=1152593863</link>
        <description># $EPIC: realpath.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$realpath(&lt;filepath&gt;)

	*  If the &lt;filepath&gt; argument is omitted the empty string is returned.
	*  If the operating system does not have the realpath(3) function call, the &lt;filepath&gt; argument is returned.
	*  All directories, if any, in &lt;filepath&gt; must exist; if any of them do not exist the empty string is returned.
	*  The return function is the full absolute path of &lt;filepath&gt; with all symbolic links, `.’, `..’ and extra …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/reconnect?rev=1157153317">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-01T18:28:37+00:00</dc:date>
        <title>reconnect</title>
        <link>http://www.epicsol.org/help/reconnect?rev=1157153317</link>
        <description>This is a disambiguation page.  Do you mean the reconnect command or the reconnect script?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/reconnect_command?rev=1171347600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T00:20:00+00:00</dc:date>
        <title>reconnect_command</title>
        <link>http://www.epicsol.org/help/reconnect_command?rev=1171347600</link>
        <description># $EPIC: reconnect_command.txt,v 1.2 2006/09/19 10:52:37 sthalik Exp $ 

reconnect [&lt;reason&gt;]

The reconnect command does a disconnect of the current server immediately followed by a server +refnum.  The effect of this is your connection to the server is abandoned and then immediately restarted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/reconnect_script?rev=1172721000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-28T21:50:00+00:00</dc:date>
        <title>reconnect_script</title>
        <link>http://www.epicsol.org/help/reconnect_script?rev=1172721000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/redirect?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>redirect</title>
        <link>http://www.epicsol.org/help/redirect?rev=1156876398</link>
        <description># $EPIC: redirect.txt,v 1.4 2006/08/29 18:33:16 sthalik Exp $ 

redirect &lt;nick&gt;|*|&lt;channel&gt;|%&lt;process&gt;|=&lt;nick&gt; &lt;command&gt;

Redirect sends a copy of all of the output sent to any windows connected to the current server to any place you can send a MSG to (ie, an irc nickname, a channel, an EXEC process, a DCC CHAT, etc) The first argument is a MSG list and it can contain any number of targets and it’s formatted like like a MSG would be. REDIRECTing to the special target 0 (zero) acts as a sink an…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/referring_to_servers?rev=1157157444">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-01T19:37:24+00:00</dc:date>
        <title>referring_to_servers</title>
        <link>http://www.epicsol.org/help/referring_to_servers?rev=1157157444</link>
        <description># $EPIC: referring_to_servers.txt,v 1.1 2006/09/02 00:37:24 jnelson Exp $ 

A server has several pieces of data that identify it 
 Refnum         A small positive integer number  Our Name       The hostname you provided in the server description  Its Name       The name the server refers to itself as on irc  Group          The (local) group name you put the server into  Alt names      Any alternate name you have given the server 
 There are many places you provide a “server” to the client.  …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regcomp?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>regcomp</title>
        <link>http://www.epicsol.org/help/regcomp?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regcomp_cs?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>regcomp_cs</title>
        <link>http://www.epicsol.org/help/regcomp_cs?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regerror?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>regerror</title>
        <link>http://www.epicsol.org/help/regerror?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regex?rev=1171740000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T13:20:00+00:00</dc:date>
        <title>regex</title>
        <link>http://www.epicsol.org/help/regex?rev=1171740000</link>
        <description># $EPIC: regex.txt,v 1.4 2006/08/19 06:21:24 sthalik Exp $ 

$regcomp(&lt;regex pattern&gt;) 
 $regexec(&lt;compiled pattern&gt; &lt;string&gt;) 
 $regmatches(&lt;compiled pattern&gt; &lt;matches&gt; &lt;string&gt;) 
 $regerror(&lt;compiled pattern&gt;) 
 $regfree(&lt;compiled pattern&gt;)

These functions are an interface to “regular expression” pattern matching:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regexec?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>regexec</title>
        <link>http://www.epicsol.org/help/regexec?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regfree?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>regfree</title>
        <link>http://www.epicsol.org/help/regfree?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/regmatches?rev=1171378200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-13T08:50:00+00:00</dc:date>
        <title>regmatches</title>
        <link>http://www.epicsol.org/help/regmatches?rev=1171378200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rehash?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>rehash</title>
        <link>http://www.epicsol.org/help/rehash?rev=1155967649</link>
        <description>#$EPIC: rehash.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

rehash [command]

This command is used to force the current server to reload its ircd.conf configuration file.  This is useful for effecting configuration changes without starting a new server. A command can be given on some servers which extends rehash to other configuration files and other functionality.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/remw?rev=1184106000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-07-10T17:20:00+00:00</dc:date>
        <title>remw</title>
        <link>http://www.epicsol.org/help/remw?rev=1184106000</link>
        <description># $EPIC: remw.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$remw(&lt;word&gt; &lt;word list&gt;)

	*  If the &lt;word&gt; argument is omitted this function returns the empty string.
	*  The return value of this function is &lt;word list&gt; with the first occurrence of the literal word &lt;word&gt; removed.
	*  One space surrounding &lt;word&gt; is removed; additional spaces will remain.
	*  Historically &lt;word list&gt; does not support double-quoted words. This may change in the future.  Try using /xdebug extractw.
	*  &lt;word&gt; and &lt;w…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/remws?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>remws</title>
        <link>http://www.epicsol.org/help/remws?rev=1155967649</link>
        <description># $EPIC: remws.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$remws(&lt;lwords&gt; / &lt;rwords&gt;)

	*  The first literal slash character found in the input acts as the separator between &lt;lwords&gt; and &lt;rwords&gt;.  This means that &lt;lwords&gt; must not contain any slashes, but &lt;rwords&gt; may.  If you do not put in a slash somewhere, the empty string is returned.
	*  Any extra spaces between words in &lt;rwords&gt; will be removed.
	*  The return value of this function will be all words in &lt;rwords&gt; that are NOT also in &lt;l…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rename?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>rename</title>
        <link>http://www.epicsol.org/help/rename?rev=1172803800</link>
        <description>#$EPIC: rename.txt,v 1.3 2006/08/19 06:19:30 sthalik Exp $ 

$rename(&lt;oldpath&gt; &lt;newpath&gt;)

	*  If the &lt;oldpath&gt; or &lt;newpath&gt; arguments are omitted this function returns the empty string.
	*  The file &lt;oldpath&gt; is renamed to &lt;newpath&gt; in accordance with the rename(2) system call on your operating system.
	*  Generally speaking $rename() cannot move files between file systems, but they can be moved between directories on the same file system.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/renumber?rev=1172685000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-28T11:50:00+00:00</dc:date>
        <title>renumber</title>
        <link>http://www.epicsol.org/help/renumber?rev=1172685000</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/repeat?rev=1154402112">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-31T22:15:12+00:00</dc:date>
        <title>repeat</title>
        <link>http://www.epicsol.org/help/repeat?rev=1154402112</link>
        <description>This is a disambiguation page.  Do you mean the repeat command or the repeat function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/repeat_command?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>repeat_command</title>
        <link>http://www.epicsol.org/help/repeat_command?rev=1155967649</link>
        <description>#$EPIC: repeat_command.txt,v 1.4 2006/08/19 06:07:20 sthalik Exp $ 

repeat (&lt;count&gt;) &lt;command&gt; 
 repeat &lt;count&gt; &lt;command&gt;

This command repeatedly executes &lt;command&gt; &lt;count&gt; number of times. If &lt;count&gt; is enclosed in parenthesis, it is evaluated as a mathematical expression (ala ${...}), and if it is not, it is evaluated as regular text.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/repeat_function?rev=1152593863">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-10T23:57:43+00:00</dc:date>
        <title>repeat_function</title>
        <link>http://www.epicsol.org/help/repeat_function?rev=1152593863</link>
        <description># $EPIC: repeat_function.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$repeat(&lt;count&gt; &lt;text&gt;)

This function returns a string composed of the input text concatenated to itself the specified number of times.

This function has many potential uses.  For example, it would be used to format output from a script such that it is always the width of the current window.  This has the side bonus of removing the need to hard- code formatting devices (table headers and such), which tend to look rather…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rest?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>rest</title>
        <link>http://www.epicsol.org/help/rest?rev=1155967649</link>
        <description># $EPIC: rest.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$rest(&lt;text&gt;) 
 $rest(&lt;num&gt; &lt;text&gt;)

	*  If the &lt;num&gt; argument is not provided, 1 is the default value.
	*  The return value is &lt;text&gt; with the first &lt;num&gt;th characters removed.
	*  If you think that the first word in &lt;text&gt; may be a number, better to be safe than sorry; specify an explicit “1” for &lt;num&gt;.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/restart?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>restart</title>
        <link>http://www.epicsol.org/help/restart?rev=1155967649</link>
        <description>restart

This command is used to completely restart the server.  A side effect of this is that the configuration file will be read again.  However, it is generally more useful for clearing out internal buffers and other wasted memory.

This command is limited to irc operators on the server to be RESTARTed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/restw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>restw</title>
        <link>http://www.epicsol.org/help/restw?rev=1172803800</link>
        <description># $EPIC: restw.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$restw(&lt;count&gt; &lt;word list&gt;)

	*  If the &lt;count&gt; argument is omitted the empty string is returned.
	*  This function returns the complement of $leftw(); that is,
	*  This function returns &lt;word list&gt; with the first &lt;count&gt; words removed.
	*  Historically &lt;word list&gt; does not support double-quoted words. This may change in the future.  Try using /xdebug extractw.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/return?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>return</title>
        <link>http://www.epicsol.org/help/return?rev=1156876398</link>
        <description>return  
 return &lt;arguments&gt;

Return terminates processing of the current 

	*  alias (command or function) call,
	*  defer command, 
	*  exec callback,
	*  load, 
	*  on hook callback,
	*  queue command, 
	*  timer command, 
	*  wait -cmd callback,
	*  wait %proc -cmd callback, or
	*  {...} math operator.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/revdcc?rev=1171945200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T22:20:00+00:00</dc:date>
        <title>revdcc</title>
        <link>http://www.epicsol.org/help/revdcc?rev=1171945200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/reverse?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>reverse</title>
        <link>http://www.epicsol.org/help/reverse?rev=1155967649</link>
        <description># $EPIC: reverse.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$reverse(&lt;text&gt;)

	*  This function returns a copy of &lt;text&gt; with all of the characters in reverse order, to wit:
	*  Let the characters in &lt;text&gt; be numbered from 0 to &lt;L&gt;:
 Index in &lt;word list&gt;  Index in return value  0                     &lt;L&gt;                    1                     &lt;L-1&gt;                  2                     &lt;L-2&gt;                  ...                   ...                    &lt;L-2&gt;                 2              …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/revw?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>revw</title>
        <link>http://www.epicsol.org/help/revw?rev=1155967649</link>
        <description># $EPIC: revw.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$revw(&lt;word list&gt;)

	*  This function returns a copy of &lt;word list&gt; with all of the words in reverse order, to wit:
	*  Let the words in &lt;word list&gt; be numbered from 0 to &lt;L&gt;:
     Index in &lt;word list&gt;      Index in return value    0                             &lt;L&gt;                      1                             &lt;L-1&gt;                    2                             &lt;L-2&gt;                    ...                           ...          …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rfilter?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>rfilter</title>
        <link>http://www.epicsol.org/help/rfilter?rev=1155967649</link>
        <description># $EPIC: rfilter.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$rfilter(&lt;word&gt; &lt;pattern list&gt;)

	*  If the &lt;word&gt; argument is omitted the empty string is returned.
	*  This function returns a space separated pattern list of all of the patterns in &lt;pattern list&gt; that DO NOT match &lt;word&gt;.
	*  This is the complement to $rpattern(), and the inverse of $filter().
	*  Double quoted words are honored, but the double quotes will be lost in the return value.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/right?rev=1155968522">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:22:02+00:00</dc:date>
        <title>right</title>
        <link>http://www.epicsol.org/help/right?rev=1155968522</link>
        <description># $EPIC: right.txt,v 1.4 2006/08/19 06:21:24 sthalik Exp $ 

$right(&lt;count&gt; &lt;text&gt;)

	*  If &lt;count&gt; is omitted, this function returns the empty string.
	*  If &lt;text&gt; is omitted, this function returns the empty string.
	*  If &lt;count&gt; is less than 0, this function returns the empty string.
	*  If &lt;text&gt; is more than &lt;count&gt; characters long, then this function will return a copy of the last &lt;count&gt; characters in &lt;text&gt;.
	*  If &lt;text&gt; is less than or exactly &lt;count&gt; characters long, then this functi…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rightw?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>rightw</title>
        <link>http://www.epicsol.org/help/rightw?rev=1172803800</link>
        <description># $EPIC: rightw.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

$rightw(&lt;count&gt; &lt;word list&gt;)

	*  If the &lt;count&gt; argument is omitted the empty string is returned.
	*  If the &lt;count&gt; argument is less than 1, the empty string is returned.
	*  This function returns the last &lt;count&gt; words from &lt;word list&gt;.
	*  Historically &lt;word list&gt; does not support double-quoted words. This may change in the future.  Try using /xdebug extractw.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rindex?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>rindex</title>
        <link>http://www.epicsol.org/help/rindex?rev=1172803800</link>
        <description># $EPIC: rindex.txt,v 1.1.1.1 2006/07/11 04:57:43 jnelson Exp $ 

$rindex(&lt;characters&gt; &lt;text&gt;)

	*  If the &lt;characters&gt; argument is omitted the empty string is returned.
	*  &lt;characters&gt; may contain any number of different characters.  If you want to include the space character, enclose it in double quotes.  If you want to include the double quote character, put some other character before the double-quote.
	*  If the first character in &lt;characters&gt; is the caret (”^”), then the list of &lt;char…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rmatch?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>rmatch</title>
        <link>http://www.epicsol.org/help/rmatch?rev=1156876398</link>
        <description># $EPIC: rmatch.txt,v 1.5 2006/08/29 18:22:56 sthalik Exp $ 

$rmatch(&lt;word&gt; &lt;pattern list&gt;)

	*  If the &lt;word&gt; argument is omitted the empty string is returned.
	*  &lt;pattern list&gt; contains zero or more space separated “extended words”
	*  Each pattern in &lt;pattern list&gt; is taken as a wildcard pattern, which is matched against &lt;word&gt;, which is taken as literal text.
	*  If none of the patterns in &lt;pattern list&gt; match &lt;word&gt;, then the return value of $rmatch() is 0 (zero).
	*  Otherwise, the r…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rmatchitem?rev=1172553600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-26T23:20:00+00:00</dc:date>
        <title>rmatchitem</title>
        <link>http://www.epicsol.org/help/rmatchitem?rev=1172553600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rmdir?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>rmdir</title>
        <link>http://www.epicsol.org/help/rmdir?rev=1172803800</link>
        <description># $EPIC: rmdir.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$rmdir(&lt;directory&gt; [&lt;directory&gt; ...])

This function unlinks the specified directories from the filesystem.  As with the normal shell mechanism, the directory must be empty before it can be removed.  Tilde-expansion is permitted.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rpattern?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>rpattern</title>
        <link>http://www.epicsol.org/help/rpattern?rev=1155967649</link>
        <description># $EPIC: rpattern.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$rpattern(&lt;word&gt; &lt;pattern list&gt;)

	*  If the &lt;word&gt; argument is omitted the empty string is returned.
	*  This function returns a space separated pattern list of all of the patterns in &lt;pattern list&gt; that match &lt;word&gt;.
	*  This is the complement to $rfilter(), and the inverse of $pattern().
	*  Double quoted words are honored, but the double quotes will be lost in the return value.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rping?rev=1155967649">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T01:07:29+00:00</dc:date>
        <title>rping</title>
        <link>http://www.epicsol.org/help/rping?rev=1155967649</link>
        <description>rping &lt;server&gt;

This command works like the PING command (CTCP PING), except it is used on a server instead of a client.  As with PING, it is used to test the relative distance another server is from you across the irc network.

This command is limited to irc operators.  Additionally, it is limited to the Undernet, and servers using recent ircu server code.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/rsubstr?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>rsubstr</title>
        <link>http://www.epicsol.org/help/rsubstr?rev=1172803800</link>
        <description># $EPIC: rsubstr.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

$rsubstr(&lt;substring&gt; &lt;search string&gt;)

This function searches for &lt;substring&gt; from the end of  &lt;search string&gt; and returns the $index() to it.

They can be used to search for specific things in output from a server, or as an alternative to $match(*substring* searchstring).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ruby?rev=1154062800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-07-28T00:00:00+00:00</dc:date>
        <title>ruby</title>
        <link>http://www.epicsol.org/help/ruby?rev=1154062800</link>
        <description>This is a disambiguation page.  Do you mean the ruby command or the ruby function?</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ruby_command?rev=1171945200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-19T22:20:00+00:00</dc:date>
        <title>ruby_command</title>
        <link>http://www.epicsol.org/help/ruby_command?rev=1171945200</link>
        <description>#$EPIC: ruby_command.txt,v 1.2 2006/08/19 06:07:20 sthalik Exp $ 

ruby {ruby statement}

If EPIC was linked with an embedded ruby interpreter, the ruby statement shall be executed by ruby.  If EPIC was not linked against ruby, then no action shall take place.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/ruby_function?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>ruby_function</title>
        <link>http://www.epicsol.org/help/ruby_function?rev=1156876398</link>
        <description># $EPIC: ruby_function.txt,v 1.2 2006/08/29 18:22:56 sthalik Exp $ 

$ruby(ruby statement)

If EPIC was linked with an embedded ruby interpreter, the ruby statement shall be executed by ruby.  If EPIC was not linked against ruby, then no  action shall take place.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/sar?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>sar</title>
        <link>http://www.epicsol.org/help/sar?rev=1155979560</link>
        <description># $EPIC: sar.txt,v 1.2 2006/08/19 09:25:52 sthalik Exp $ 

$sar([i][g][r]/&lt;search&gt;/&lt;replace&gt;/&lt;text&gt;)

The arguments are composed of:

	*  zero or more of the options ‘i’, ‘g’, and ‘r’,
	*  a delimiter which can be any character other than ‘i’, ‘g’, or ‘r’, and is customarily a forward-slash,
	*  some text (”&lt;search&gt;”) that may not contain the delimiter to be removed,
	*  a delimiter; the same as (2),
	*  some text (”&lt;replace&gt;”) that may not contain the delimiter t…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/save?rev=1171738200">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-17T12:50:00+00:00</dc:date>
        <title>save</title>
        <link>http://www.epicsol.org/help/save?rev=1171738200</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/say?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>say</title>
        <link>http://www.epicsol.org/help/say?rev=1156876398</link>
        <description># $EPIC: say.txt,v 1.3 2006/08/29 18:22:56 sthalik Exp $ 

say &lt;text&gt;

This command sends a message to the current window’s current channel. This is useful when you want to send a message to the current channel  of a window that has a QUERY active.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/scan?rev=1172121600">
        <dc:format>text/html</dc:format>
        <dc:date>2007-02-21T23:20:00+00:00</dc:date>
        <title>scan</title>
        <link>http://www.epicsol.org/help/scan?rev=1172121600</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/screen?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>screen</title>
        <link>http://www.epicsol.org/help/screen?rev=1155979560</link>
        <description># $EPIC: screen.txt,v 1.2 2006/08/19 09:25:52 sthalik Exp $ 

load screen

This script allows ircII windows to be manipulated muck like with the screen program.  It creates a number of key bindings: 
    Key                     Function                                                    ^X1 ... ^X0  swap windows 1 to 10.                                          ^Xa          goes to the last window..                                          ^Xc , ^X^C   creates a new window                       …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/security?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>security</title>
        <link>http://www.epicsol.org/help/security?rev=1155979560</link>
        <description>EPIC is an extremely flexible client.  To borrow a phrase from many a C programmer, it gives you enough rope to hang yourself.  With caution and some common sense, this isn’t a problem.

By far, the most potentially dangerous facility is ON. Because hooks can be set to activate on any arbitrary input, and because they can perform most any action when activated, they are often used for malicious purposes. Consider the following:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/sedcrypt?rev=1155980147">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:35:47+00:00</dc:date>
        <title>sedcrypt</title>
        <link>http://www.epicsol.org/help/sedcrypt?rev=1155980147</link>
        <description># $EPIC: sedcrypt.txt,v 1.2 2006/08/19 09:35:40 sthalik Exp $ 

$sedcrypt(&lt;flag&gt; &lt;from&gt; &lt;text&gt;)

This is a debugging function.  It should not be used unless you are debugging.  They encrypt and decrypt &lt;text&gt; using the current crypt  settings for the peer &lt;from&gt;.  Ciphertext is always CTCP enquoted.  That does not mean it is /echo‘able, only tha it can be sent in a PRIVMSG.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/send?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>send</title>
        <link>http://www.epicsol.org/help/send?rev=1155979560</link>
        <description>send &lt;text&gt;

This command provides a convenient mechanism for scripts, aliases, key bindings, etc. to send a line of text to the current channel or query. It is also useful for chatting while COMMAND_MODE is off.  Other than the ability to send a message to a query, SEND is identical to SAY.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/sendline?rev=1159748400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-01T19:20:00+00:00</dc:date>
        <title>sendline</title>
        <link>http://www.epicsol.org/help/sendline?rev=1159748400</link>
        <description>sendline &lt;text&gt;

The sendline command submits &lt;text&gt; to the command processor without any further $-expansion (as contrasted with eval)

If &lt;text&gt; begins with a slash (”/”), then &lt;text&gt; is taken to be a command.   If &lt;text&gt; does not begin with a slash, then &lt;text&gt; is taken to be a message that should be sent to the current window’s current target.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/serial_numbers?rev=1155980147">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:35:47+00:00</dc:date>
        <title>serial_numbers</title>
        <link>http://www.epicsol.org/help/serial_numbers?rev=1155980147</link>
        <description>One of the neat things about ON hooks is that multiple hooks of the same type may be given different priorities.  A serial number may be any number, positive or negative; zero is the default and should not be used directly. The numbers themselves don’t really matter, rather their relation to other serial numbers is what’s important.  For example:</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/server?rev=1160095114">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-05T19:38:34+00:00</dc:date>
        <title>server</title>
        <link>http://www.epicsol.org/help/server?rev=1160095114</link>
        <description># $EPIC: server.txt,v 1.5 2006/09/02 00:38:26 jnelson Exp $ 

server 
 server [&lt;server description&gt;|&lt;server refnum&gt;] 
 server [+|-][&lt;server name&gt;] 
 server [-add] &lt;server description&gt;       [see below] 
 server [-delete &lt;server refnum&gt;]

The nexus of irc is the server, also known as “ircd”, which comes in  different classes, such as “irc2.8”, “irc2.9”, “EFNext”, “ircu2.8” “ircu2.9”, “hybrid5”, “hybrid6”, “hybrid7”, “dreamforge”, “bahamut”, and a huge l…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/server_description?rev=1164302400">
        <dc:format>text/html</dc:format>
        <dc:date>2006-11-23T11:20:00+00:00</dc:date>
        <title>server_description</title>
        <link>http://www.epicsol.org/help/server_description?rev=1164302400</link>
        <description># $EPIC: server_description.txt,v 1.2 2006/09/19 03:17:58 jnelson Exp $ 

A server description is the way you give the client enough information about an irc server for it to be added to the server list and used.

Any place you are supposed to provide a “server”, you can provide either a server refnum, or the server description.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/server_list?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>server_list</title>
        <link>http://www.epicsol.org/help/server_list?rev=1155979560</link>
        <description>There are several ways to set a predefined list of servers for EPIC to use. In general, though, they all use the same basic format: 
 server:port:password:nickname
 The server is the name of the server to connect to.  The port is the port number on the server’s host to connect on.  The password is only required for servers that require one to connect.  The nickname is the nick to use once connected to the server.  Only the server name is required.  The remaining parameters may be specified as …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/server_numerics?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>server_numerics</title>
        <link>http://www.epicsol.org/help/server_numerics?rev=1155979560</link>
        <description>In addition to the numerous named hooks provided by the client (refer to the ON command in Section 5), EPIC can hook any numeric reply sent by a server. They are treated no differently from named hooks.  Space constraints prevent a full discussion of all server numerics, not to mention that they tend to differ from network to network.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/server_state?rev=1158664800">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-19T06:20:00+00:00</dc:date>
        <title>server_state</title>
        <link>http://www.epicsol.org/help/server_state?rev=1158664800</link>
        <description># $EPIC: server_state.txt,v 1.5 2006/09/19 10:52:37 sthalik Exp $ 

Each server in your server list has a state that it is in. The valid states are:
 Name        Description  CREATED     The initial state while it is being added to the server list  RECONNECT   Ready to be used: will be connected to when window points at it  DNS         Server being brought up: Nonblocking DNS lookup in progress  CONNECTING  Server being brought up: Nonblocking connect in progress  SSL_CONNECTING  Server being br…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/serverctl?rev=1179193800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-05-14T20:50:00+00:00</dc:date>
        <title>serverctl</title>
        <link>http://www.epicsol.org/help/serverctl?rev=1179193800</link>
        <description># $EPIC: serverctl.txt,v 1.8 2006/09/01 23:29:58 jnelson Exp $ 

$serverctl(REFNUM &lt;server refnum&gt;) 
 $serverctl(REFNUM &lt;name&gt;) 
 $serverctl(REFNUM &lt;name&gt;:&lt;port&gt;) 
 $serverctl(OMATCH &lt;pattern&gt;) 
 $serverctl(IMATCH &lt;pattern&gt;) 
 $serverctl(GMATCH &lt;pattern&gt;) 
 $serverctl(LAST_SERVER) 
 $serverctl(FROM_SERVER) 
 $serverctl(MAX) 
 $serverctl(GET &lt;refnum&gt; &lt;param&gt;) 
 $serverctl(SET &lt;refnum&gt; &lt;param&gt; &lt;val&gt;)</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/serverwin?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>serverwin</title>
        <link>http://www.epicsol.org/help/serverwin?rev=1155979560</link>
        <description># $EPIC: serverwin.txt,v 1.2 2006/08/19 09:25:52 sthalik Exp $ 

$serverwin() 
 $serverwin(&lt;server refnum&gt;)

	*  If the &lt;server refnum&gt; argument is omitted, the current server’s refnum is taken as the default value.
	*  If &lt;server refnum&gt; is not a valid server refnum, -1 is returned.
	*  If there are no windows connected to the server (which should never happen, but hey, you never know), -1 is returned.
	*  Otherwise, the refnum of the last window to recieve the input focus that is connected t…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/servlist?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>servlist</title>
        <link>http://www.epicsol.org/help/servlist?rev=1155979560</link>
        <description># $EPIC: servlist.txt,v 1.2 2006/08/19 09:25:52 sthalik Exp $ 

servlist [&lt;name&gt; [&lt;type&gt;]]

This query asks the server for the list of services that are available to you right now.  You use the squery command to talk to the service.

Usually a network server will be used to perform some administrative task for the network, such as a channel service, a nickname service, or a note service.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/servports?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>servports</title>
        <link>http://www.epicsol.org/help/servports?rev=1155979560</link>
        <description># $EPIC: servports.txt,v 1.2 2006/08/19 09:25:52 sthalik Exp $ 

$servports(&lt;server name/refnum&gt;)

This function returns the remote and local port assignments for the connection to the specified server.

the remote and local port assignments for the specified server connection, separated by a space</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set?rev=1173324000">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-07T21:20:00+00:00</dc:date>
        <title>set</title>
        <link>http://www.epicsol.org/help/set?rev=1173324000</link>
        <description>set [&lt;variable&gt; [&lt;value&gt;]] set [-]&lt;variable&gt;

This command is used to set the value of one of EPIC’s numerous internal variables.  These variables affect all aspects of the client’s behavior, from enabling special text highlighting to enforcing strict security features.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_allow_c1_chars?rev=1155979560">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T04:26:00+00:00</dc:date>
        <title>set_allow_c1_chars</title>
        <link>http://www.epicsol.org/help/set_allow_c1_chars?rev=1155979560</link>
        <description># $EPIC: set_allow_c1_chars.txt,v 1.3 2006/08/19 09:25:52 sthalik Exp $ 

set allow_c1_chars [on|off|toggle]

When ON: Characters from 128 to 159 (inclusive) are permitted to be sent to your display.  This can be really bad if you’re using GNU Screen or a terminal that doesn’t understand 8 bit characters. When OFF: Characters from 128 to 159 (inclusive) are always stripped and  not sent to your display.  This can be bad if your font uses characters in that range to represent characters that …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_always_split_biggest?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_always_split_biggest</title>
        <link>http://www.epicsol.org/help/set_always_split_biggest?rev=1155982633</link>
        <description>set always_split_biggest [on|off|toggle]

When you use window new or window show to split the screen into multiple windows, one of the windows on the screen has to be split in half to make room for the new window.  This value controls which window is  selected to be split.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_banner?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_banner</title>
        <link>http://www.epicsol.org/help/set_banner?rev=1155982633</link>
        <description>set banner &lt;text&gt;

Changes the default “***” in front of informational messages. The banner is used internally for “say” messages, and by xecho -b. You will want to set banner_expand to ON if the banner contains expandos  that need to be expanded each time.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_banner_expand?rev=1155982946">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:22:26+00:00</dc:date>
        <title>set_banner_expand</title>
        <link>http://www.epicsol.org/help/set_banner_expand?rev=1155982946</link>
        <description>set banner_expand [on|off|toggle]

If ON: The value of set banner is run through expando-substution every  time it is used. If OFF: The value of set banner is taken as a literal string.

This is useful if you like to display the current time ($Z) in your banner.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_beep?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_beep</title>
        <link>http://www.epicsol.org/help/set_beep?rev=1155982633</link>
        <description>set beep [on|off|toggle]

When turned off, this suppresses any audible beeps the client may try to use. Any ^G processed by the client will be printed as a ^VG^V. This setting will override the BEEP_ON_MSG and BEEP_WHEN_AWAY settings, and will effectively disable the BEEP command.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_channel_name_width?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_channel_name_width</title>
        <link>http://www.epicsol.org/help/set_channel_name_width?rev=1155982633</link>
        <description>set channel_name_width [&lt;number&gt;]

This variable sets the maximum width a channel’s name may use on the client’s status bar.  If set to 0 (zero), there is no limit on the length of the channel’s name.  This variable also affects the default display of LIST and NAMES output.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_client_information?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_client_information</title>
        <link>http://www.epicsol.org/help/set_client_information?rev=1155982633</link>
        <description>set client_information [&lt;text&gt;]

The contents of this variable are appended to the client’s default CTCP VERSION reply.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_clock?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_clock</title>
        <link>http://www.epicsol.org/help/set_clock?rev=1155982633</link>
        <description>set clock [on|off|toggle]

When turned on, the system clock runs and updates every minute.  This is reflected in the STATUS_CLOCK status bar expando, and $Z. If you turn the clock off, STATUS_CLOCK shows nothing.

It is a BAD IDEA to turn the clock off if you use $Z.  If you  don’t want to see the clock in your status bar, take %T out of your  STATUS_FORMAT.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_clock_24hour?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>set_clock_24hour</title>
        <link>http://www.epicsol.org/help/set_clock_24hour?rev=1156876398</link>
        <description>set clock_24hour [on|off|toggle]

When turned on, this setting causes EPIC’s clock to display time in 24-hour format.  When off, EPIC displays time in 12-hour format, using “AM” and “PM”.

The EPIC clock is shown in the status bar by the %T expando, and is available to scripts in the $Z special variable.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_clock_format?rev=1159743837">
        <dc:format>text/html</dc:format>
        <dc:date>2006-10-01T18:03:57+00:00</dc:date>
        <title>set_clock_format</title>
        <link>http://www.epicsol.org/help/set_clock_format?rev=1159743837</link>
        <description>set clock_format &lt;text&gt;

The client uses strftime(3) to create the system clock (%T on your  status bar or $Z.  The value is normally “%R” if set clock_24hour is ON and “%I:%M%p” if it is OFF.

You can overrule set clock_24hour and choose your own strftime(3) format  with this variable.  If you unset this variable, then the appropriate value based on set clock_24hour is used.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_clock_interval?rev=1155982946">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:22:26+00:00</dc:date>
        <title>set_clock_interval</title>
        <link>http://www.epicsol.org/help/set_clock_interval?rev=1155982946</link>
        <description>set clock_interval [&lt;seconds&gt;]

This setting controls how often the client’s status bar clock gets updated. The default value is 60 (at the top of every minute).

Previously, this value was not configurable and the client would just update the clock (and $T inline expando, /ON TIMER, and /ON IDLE) at the top of every minute. For some people, this was not nearly often enough. Now you can control exactly how often the clock is updated with this /SET.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_cmdchars?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_cmdchars</title>
        <link>http://www.epicsol.org/help/set_cmdchars?rev=1155982633</link>
        <description>set cmdchars [&lt;characters&gt;]

This variable sets all characters that may be used as a command character on the input line.  Any number of characters may be specified, and the slash ‘/’ will always be assumed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_comment_hack?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_comment_hack</title>
        <link>http://www.epicsol.org/help/set_comment_hack?rev=1155982633</link>
        <description>set comment_hack [on|off|toggle]

This variable determines how the client will handle C-style comments in loaded scripts.  When turned on, it causes the client to only recognize such comments when they start at the beginning of a line.  When off, the comments may begin anywhere.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_continued_line?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_continued_line</title>
        <link>http://www.epicsol.org/help/set_continued_line?rev=1155982633</link>
        <description>set continued_line [&lt;text&gt;]

The text in this variable, if any, will be prepended to any lines printed that are wider than the display.  This is to provide a visual indicator that the line is part of the previous line, and not a new message.  This variable may be set in conjunction with the INDENT variable.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_cpu_saver_after?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_cpu_saver_after</title>
        <link>http://www.epicsol.org/help/set_cpu_saver_after?rev=1155982633</link>
        <description>set cpu_saver_after [&lt;minutes&gt;]

This triggers CPU Saver mode after &lt;minutes&gt; without a keypress.

When CPU Saver is enabled, the status bar isn’t updated and the notify list isn’t checked. If either this value or set(4) cpu_saver_every is 0, CPU Saver mode will not activate.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_cpu_saver_every?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_cpu_saver_every</title>
        <link>http://www.epicsol.org/help/set_cpu_saver_every?rev=1155982633</link>
        <description># $EPIC: set_cpu_saver_every.txt,v 1.2 2006/08/19 10:15:16 sthalik Exp $ 

set cpu_saver_every [&lt;seconds&gt;]

This determines how often the client will update status bar, check the time, and check the notify list if CPU saver mode is active.

When CPU Saver is enabled, the status bar isn’t updated and the notify list isn’t checked. If either this value or set cpu_saver_every is 0, CPU Saver mode will not activate.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_current_window_level?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_current_window_level</title>
        <link>http://www.epicsol.org/help/set_current_window_level?rev=1155982633</link>
        <description>set current_window_level [&lt;lastlog levels&gt;]

This variable takes a lastlog level description (eg. “MSGS,PUBLIC,CRAP”) which defines which levels are redirected to the current window. This means all output with the levels in this variable are *NOT* sent to their regular window, but the current window instead.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dcc_auto_send_rejects?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_dcc_auto_send_rejects</title>
        <link>http://www.epicsol.org/help/set_dcc_auto_send_rejects?rev=1155982633</link>
        <description># $EPIC: set_dcc_auto_send_rejects.txt,v 1.2 2006/08/19 10:15:16 sthalik Exp $ 

set dcc_auto_send_rejects [on|off|toggle]

This variable controls whether DCC REJECTs will be sent to the remote peer whenever you /DCC CLOSE a dcc connection before it is opened by  either you or the other person.  This tells the other person that the offer has been revoked and they should not expect to use it.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dcc_dequote_filenames?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_dcc_dequote_filenames</title>
        <link>http://www.epicsol.org/help/set_dcc_dequote_filenames?rev=1155982633</link>
        <description># $EPIC: set_dcc_dequote_filenames.txt,v 1.2 2006/08/19 10:15:16 sthalik Exp $ 

set dcc_dequote_filenames [on|off|toggle]

When ON: Attempt to graciously deal with malformed DCC SEND requests from other clients that enclose filenames in double quotes when there is a space in the filename.  You may not be able to recieve files with a  double quote in it if you set this on.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dcc_long_pathnames?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_dcc_long_pathnames</title>
        <link>http://www.epicsol.org/help/set_dcc_long_pathnames?rev=1155982633</link>
        <description>set dcc_long_pathnames [on|off|toggle]

When turned on, this variable will cause the client to display the full pathnames of all files being transferred to or from the client via DCC.  When off, only the filenames are shown, not their parent directories.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dcc_sliding_window?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_dcc_sliding_window</title>
        <link>http://www.epicsol.org/help/set_dcc_sliding_window?rev=1155982633</link>
        <description>set dcc_sliding_window [&lt;number&gt;]

The DCC specification requires that data cannot be sent via a  DCC SEND connection until all previous data have been acknowledged by the receiver.  For high latency/high bandwidth connections (ie, anything faster than 28.8k), this can have serious consequences on throughput because at least half of the time the connection is idle waiting for an acknowledgement to be returned.  Although strict conformance to the DCC specification requires that this value be set …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dcc_store_path?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_dcc_store_path</title>
        <link>http://www.epicsol.org/help/set_dcc_store_path?rev=1155982633</link>
        <description>set dcc_store_path [&lt;path&gt;]

This sets the default directory to store files retrieved with DCC GET. Naturally, the client must have write permissions in the chosen directory for it to work properly (the client will not warn if it has insufficient access).  The default is to save the file to the current directory.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dcc_use_gateway_addr?rev=1155982946">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:22:26+00:00</dc:date>
        <title>set_dcc_use_gateway_addr</title>
        <link>http://www.epicsol.org/help/set_dcc_use_gateway_addr?rev=1155982946</link>
        <description># $EPIC: set_dcc_use_gateway_addr.txt,v 1.3 2006/08/19 10:22:21 sthalik Exp $ 

set dcc_use_gateway_addr [on|off|toggle]

This variable sets the IP address that is used in DCC requests.  If dcc_use_gateway_addr is on, the client will use the IP address of the userhost sent by the server, otherwise it will use the local IP address.  Having dcc_use_gateway_addr on may be useful in an environment where Linux IP Masquerading or NAT is used.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_debug?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_debug</title>
        <link>http://www.epicsol.org/help/set_debug?rev=1155982633</link>
        <description>set debug [&lt;level&gt;]

When turned on, this variable enables various degrees of debugging while the client is running.  It is useful for seeing precisely where a particular alias or function is failing, what variables are being assigned what values, etc.  There are three general classes of debug output, each assigned a unique number.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_dispatch_unknown_commands?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_dispatch_unknown_commands</title>
        <link>http://www.epicsol.org/help/set_dispatch_unknown_commands?rev=1155982633</link>
        <description>set dispatch_unknown_command [on|off|toggle]

When this is set ON, all commands unknown to the client will be sent to the server.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_display?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_display</title>
        <link>http://www.epicsol.org/help/set_display?rev=1155982633</link>
        <description>set display [on|off|toggle]

When turned off, this setting will cause the client to suppress all messages from being displayed (though it can still act on them internally. However, ECHO can still be used to explicitly print messages to the display.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_do_notify_immediately?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>set_do_notify_immediately</title>
        <link>http://www.epicsol.org/help/set_do_notify_immediately?rev=1156876398</link>
        <description>set do_notify_immediately [on|off|toggle]

When this is set ON, the notify list is checked on every /notify command. Else, it will wait until the top of the minute to update. This was added primarily to speed up server connects, since so many people have huge notify lists which slow down an initial connection.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_floating_point_math?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_floating_point_math</title>
        <link>http://www.epicsol.org/help/set_floating_point_math?rev=1155982633</link>
        <description>set floating_point_math [on|off|toggle]

When turned on, EPIC becomes capable of handling floating-point math operations.  In truth, all math is done in floating-point, except the normal behavior is to convert everything to integers before actually displaying them.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_floating_point_precision?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_floating_point_precision</title>
        <link>http://www.epicsol.org/help/set_floating_point_precision?rev=1155982633</link>
        <description># $EPIC: set_floating_point_precision.txt,v 1.2 2006/08/19 10:15:16 sthalik Exp $ 

set floating_point_precision [number]

This sets the number of decimal places that each floating point operation is rounded to.  Setting it to 0 is not necessarily the same thing as  turning floating_point_math off.  The default is 6.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_after?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_flood_after</title>
        <link>http://www.epicsol.org/help/set_flood_after?rev=1155982633</link>
        <description>set flood_after [&lt;number&gt;]

This setting specifies how many messages must be received before triggering the FLOOD hook.  Naturally, the hook is only triggered if the message rate meets or exceeds the FLOOD_RATE setting.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_ignore?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>set_flood_ignore</title>
        <link>http://www.epicsol.org/help/set_flood_ignore?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_maskuser?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>set_flood_maskuser</title>
        <link>http://www.epicsol.org/help/set_flood_maskuser?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_rate?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>set_flood_rate</title>
        <link>http://www.epicsol.org/help/set_flood_rate?rev=1172803800</link>
        <description>set flood_rate [&lt;number&gt;]

This variable sets the message rate (per second) that will trigger the FLOOD hook, if the total message count exceeds the FLOOD_AFTER setting at the given rate.  Thus, if messages from a remote client outpace the FLOOD_RATE for at least FLOOD_AFTER messages, the FLOOD hook is caught. If FLOOD_RATE is larger than FLOOD_AFTER, the client will not trigger the hook until at least FLOOD_RATE messages have been received.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_rate_per?rev=1172803800">
        <dc:format>text/html</dc:format>
        <dc:date>2007-03-01T20:50:00+00:00</dc:date>
        <title>set_flood_rate_per</title>
        <link>http://www.epicsol.org/help/set_flood_rate_per?rev=1172803800</link>
        <description></description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_users?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_flood_users</title>
        <link>http://www.epicsol.org/help/set_flood_users?rev=1155982633</link>
        <description>set flood_users [&lt;number&gt;]

This variable sets the maximum number of users (unique nicknames) that the client will perform flood protection for.  Larger numbers may start to affect client performance, so experiment with this value as needed.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_flood_warning?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_flood_warning</title>
        <link>http://www.epicsol.org/help/set_flood_warning?rev=1155982633</link>
        <description>set flood_warning [on|off|toggle]

When turned on, the client will display a message to the user to that effect (who is flooding, what type, etc.).  If off, the client does not warn the user that flood protection has kicked in, unless a custom message is returned from within the FLOOD hook.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_hide_private_channels?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_hide_private_channels</title>
        <link>http://www.epicsol.org/help/set_hide_private_channels?rev=1155982633</link>
        <description>set hide_private_channels [on|off|toggle]

When turned on, the client will not display the name of any current channel in the status bar if that channel is +p or +s.  Instead, it will display “*private*”.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_high_bit_escape?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_high_bit_escape</title>
        <link>http://www.epicsol.org/help/set_high_bit_escape?rev=1155982633</link>
        <description>#$EPIC: set_high_bit_escape.txt,v 1.2 2006/08/19 10:15:16 sthalik Exp $ 

set high_bit_escape [0|1|2]

Controls how EPIC treats characters with the high bit set:

When 0: The character is accepted as-is.  However, the character is still subject to the value of set eight_bit_characters. If you need to input 8 bit characters, make sure that set high_bit_escape is 0 and set
eight_bit_characters is ON. This is the preferred setting for non-english users who expect the &lt;meta&gt; key to input 8-bit latin…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_hold_interval?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_hold_interval</title>
        <link>http://www.epicsol.org/help/set_hold_interval?rev=1155982633</link>
        <description>set hold_interval [&lt;lines&gt;]

This controls how many lines must be added to a window’s hold buffer before your status line is forcibly refreshed.  The default is 10, which is the traditional value.  The number of lines must be at least 1.  This command sets the default for all windows.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_hold_mode?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_hold_mode</title>
        <link>http://www.epicsol.org/help/set_hold_mode?rev=1155982633</link>
        <description>set hold_mode [on|off|toggle]

When turned on, this setting causes the client to pause the held window after each screenful of data, unless there is interaction by the user. If the user does not issue a command of some sort within one screenful, EPIC will buffer all further incoming messages.  An issued command or a simple carriage return will cause the display to advance another screenful, and so on, until the display is up to date again.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_hold_slider?rev=1155982633">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-19T05:17:13+00:00</dc:date>
        <title>set_hold_slider</title>
        <link>http://www.epicsol.org/help/set_hold_slider?rev=1155982633</link>
        <description># $EPIC: set_hold_slider.txt,v 1.2 2006/08/19 10:15:16 sthalik Exp $ 

set hold_slider &lt;number&gt;

This sets the value of HOLD_SLIDER for the current window, and the default value for any future windows you create.  You should read the help file  for WINDOW HOLD_SLIDER for more info.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_indent?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_indent</title>
        <link>http://www.epicsol.org/help/set_indent?rev=1156081883</link>
        <description>set indent [on|off|toggle]

When turned on, long lines will be wrapped such that they are indented to the same position as the second word on the first line.  Subsequent wrapping of the same line will be indented to the same place.

If CONTINUED_LINE is also set, the client will pad the wrapped portions of the line with the CONTINUED_LINE contents, unless CONTINUED_LINE happens to be longer than the indented space.  CONTINUED_LINE will not be truncated in this event; it is either displayed in fu…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_input_prompt?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_input_prompt</title>
        <link>http://www.epicsol.org/help/set_input_prompt?rev=1156081883</link>
        <description>set input_prompt [&lt;string&gt;]

This setting allows the user to add a custom string the the beginning of the input line (for display purposes).  Much like the various Unix shells, the prompt can contain any string desired.

It is generally used for displaying information about the current target (such as a channel or queried nickname).  Any variables used in the prompt are re-evaluated after each command issued from the input prompt.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_insert_mode?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_insert_mode</title>
        <link>http://www.epicsol.org/help/set_insert_mode?rev=1156081883</link>
        <description>set insert_mode [on|off|toggle]

When this setting is on, text typed on the input line in the middle of a text string will shift the text to the right, making room for the text being typed.  If it is off, the typed text overwrites anything ahead of it.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_key_interval?rev=1157221669">
        <dc:format>text/html</dc:format>
        <dc:date>2006-09-02T13:27:49+00:00</dc:date>
        <title>set_key_interval</title>
        <link>http://www.epicsol.org/help/set_key_interval?rev=1157221669</link>
        <description># $EPIC: set_key_interval.txt,v 1.3 2006/09/02 18:27:47 sthalik Exp $ 

set key_interval [&lt;number&gt;]

This sets the timeout in milliseconds for the key input disambiguator.

You are permitted to create ambiguous keybindings, for example:
/BIND ^[ PARSE_COMMAND {echo You pressed Escape!}
/BIND ^%%[[%%11~ PARSE_COMMAND {echo You pressed F1!}
Now when you press &lt;escape&gt;, EPIC does not know if you actually pressed the &lt;escape&gt; key, or if you pressed &lt;f1&gt;, and it should wait for more  characters.  It …</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_lastlog?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_lastlog</title>
        <link>http://www.epicsol.org/help/set_lastlog?rev=1156081883</link>
        <description>set lastlog [&lt;number&gt;]

This option sets the size of the client’s lastlog buffer.  It can be disabled if set to 0 (zero).</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_lastlog_level?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_lastlog_level</title>
        <link>http://www.epicsol.org/help/set_lastlog_level?rev=1156081883</link>
        <description>set lastlog_level -]&lt;level&gt; [[-]&lt;level&gt; ...

This setting controls the type(s) of information that EPIC will store in its lastlog buffer.  Any single message type, or any combination, may be used.  If a type is prepended with a ‘-’, messages of that type are explicitly not saved (useful with the ALL type).  Message types may be abbreviated unambiguously.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_load_path?rev=1156876398">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-29T13:33:18+00:00</dc:date>
        <title>set_load_path</title>
        <link>http://www.epicsol.org/help/set_load_path?rev=1156876398</link>
        <description>set load_path [&lt;directory&gt;[:&lt;directory&gt; ...]]

This setting is used primarily by LOAD and WHICH (and thus the $which() function).  If the client tries to access a file and cannot find it, it searches through each directory listed in the LOAD_PATH.  It operates much like the PATH statement in Unix shells.  The directories are searched sequentially.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_log?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_log</title>
        <link>http://www.epicsol.org/help/set_log?rev=1156081883</link>
        <description>set log [on|off|toggle]

This variable globally sets whether the client saves its lastlog buffer to an external file.  The actual buffer itself isn’t saved, rather anything that is saved to the buffer is also saved to the file.

If multiple windows are in use, this setting will affect all of them, and will make no distinction in the log file as to which messages are from which window.  In this case, WINDOW LOG should be used.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_log_rewrite?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_log_rewrite</title>
        <link>http://www.epicsol.org/help/set_log_rewrite?rev=1156081883</link>
        <description># $EPIC: set_log_rewrite.txt,v 1.2 2006/08/20 13:51:17 sthalik Exp $ 

set(4) log_rewrite

If this /SET is defined (by default, it is un-set), then every time a LOGICAL line of output is about to be sent to a window, the /SET value is expanded, and the result of that expansion is substituted for the original text.  The expansion is parsed in the context that: $0      The window refnum the output is going to $1-     The text itself.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_logfile?rev=1156082475">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T09:01:15+00:00</dc:date>
        <title>set_logfile</title>
        <link>http://www.epicsol.org/help/set_logfile?rev=1156082475</link>
        <description>set logfile [&lt;filename&gt;]

This variable sets the name of the file the client will log to when the LOG variable is on.  This setting can be overridden by a logfile setting for a specific window.</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_mail?rev=1156081883">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T08:51:23+00:00</dc:date>
        <title>set_mail</title>
        <link>http://www.epicsol.org/help/set_mail?rev=1156081883</link>
        <description># $EPIC: set_mail.txt,v 1.2 2006/08/20 13:51:17 sthalik Exp $ 

set mail [&lt;0|1|2|3&gt;]

This setting affects how the client checks for new mail.  When set to 0 (zero), mail checking is disabled.  When set to 1 (one), the client will periodically report how many new messages have arrived since the last check, and the total message count.  When set to 2 (two), the client shows the sender and subject of each new message as well. When set to 3 (three), the client does everything it does when set to 2,…</description>
    </item>
    <item rdf:about="http://www.epicsol.org/help/set_mail_interval?rev=1156082475">
        <dc:format>text/html</dc:format>
        <dc:date>2006-08-20T09:01:15+00:00</dc:date>
        <title>set_mail_interval</title>
        <link>http://www.epicsol.org/help/set_mail_interval?rev=1156082475</link>
        <description>set mail_interval [&lt;seconds&gt;]

This setting controls how often the client checks your mbox for new mail. The default value is 60 (at the top of every minute).

Previously, this value was not configurable and the client would just check for new mail at the top of every minute. For some people, this was far too often, and for others, it was not nearly often enough. Now you can cont