help/0040755000014400001440000000000010215704217011374 5ustar jnelsonusershelp/CVS/0040755000014400001440000000000010215704220012021 5ustar jnelsonusershelp/CVS/Root0100644000014400001440000000002507215323637012700 0ustar jnelsonusers/home/cvs/repository help/CVS/Repository0100644000014400001440000000000507215323637014132 0ustar jnelsonusershelp help/CVS/Entries0100644000014400001440000000033010215704220013346 0ustar jnelsonusersD/1_General//// D/2_Queries//// D/3_Operators//// D/4_Misc//// D/5_Programming//// D/6_Functions//// D/7_Docs//// D/8_Scripts//// /README_FIRST/1.7/Mon May 5 14:46:25 2003// /Makefile/1.7/Wed Mar 16 01:14:55 2005// help/README_FIRST0100644000014400001440000000360307655474501013240 0ustar jnelsonusers# $EPIC: README_FIRST,v 1.7 2003/03/21 00:32:23 kitambi Exp $ How to use the EPIC help system ++ New users should use "/help 7 New_User" before proceeding further. ++ The basic system has not changed from previous releases of the client. What has changed is the structure of the helpfiles, and the helpfiles themselves. Helpfiles are now organized in logical groups of commands, similar to the Unix manual system. Section 1: General Commands Section 5: Programming EPIC Section 2: Server Queries Section 6: Builtin Functions Section 3: IRC Operator Commands Section 7: Documentation Section 4: Miscellaneous Commands Section 8: Script Library The implication of this, however, is that HELP can't work the same way as it used to. In order to read a helpfile now, its section number must also be given. Thus, where one previously obtained help on WHOIS with "/help whois", one must now use "/help 2 whois". To be able to locate helpfiles without having to know the section number, you may load the "man" script, which is documented under "/help 8 man". Another change is the references to related topics in individual help- files, which is another similarity to Unix man pages. To better help users ease into the new format, all topic references in the "See Also" sections will include a Unix-ish section reference, such as "whois(2)". ++ If you have not yet read "/help 7 New_User", please do so now. ++ VERY IMPORTANT! PLEASE READ THIS! These help files are a work-in-progress. Many of the files may contain incomplete or incorrect information. Some of the files may be entirely empty (which means that feature has not been documented yet.) Some features may not have a help file at all. Please be patient with us. If you would like to help us maintain the help files, send an email to jnelson@prbh.org. help/1_General/0040755000014400001440000000000010215704217013171 5ustar jnelsonusershelp/1_General/CVS/0040755000014400001440000000000010215704217013624 5ustar jnelsonusershelp/1_General/CVS/Root0100644000014400001440000000002507215323637014475 0ustar jnelsonusers/home/cvs/repository help/1_General/CVS/Repository0100644000014400001440000000001707215323637015732 0ustar jnelsonusershelp/1_General help/1_General/CVS/Entries0100644000014400001440000000211210215704217015151 0ustar jnelsonusersD/ctcp//// D/dcc//// /1_General/1.4/Fri Jul 20 18:24:18 2001// /bye/1.7/Fri Jul 20 18:24:18 2001// /disconnect/1.3/Fri Jul 20 18:24:18 2001// /help/1.3/Fri Jul 20 18:24:18 2001// /invite/1.3/Fri Jul 20 18:24:18 2001// /kick/1.3/Fri Jul 20 18:24:18 2001// /me/1.2/Fri Jul 20 18:24:18 2001// /nick/1.4/Fri Jul 20 18:24:18 2001// /notice/1.3/Fri Jul 20 18:24:18 2001// /notify/1.3/Fri Jul 20 18:24:18 2001// /query/1.2/Fri Jul 20 18:24:18 2001// /quit/1.2/Fri Jul 20 18:24:18 2001// /reconnect/1.3/Fri Jul 20 18:24:18 2001// /say/1.4/Fri Jul 20 18:24:18 2001// /topic/1.3/Fri Jul 20 18:24:18 2001// /channel/1.6/Sun Dec 2 13:32:18 2001// /describe/1.5/Sun Dec 2 13:32:18 2001// /join/1.6/Sun Dec 2 13:32:18 2001// /msg/1.4/Sun Dec 2 13:32:18 2001// /ping/1.4/Sun Dec 2 13:32:18 2001// /silence/1.4/Sun Dec 2 13:32:18 2001// /part/1.5/Sat Jul 27 02:25:20 2002// /mode/1.13/Wed Jan 8 18:49:10 2003// /away/1.10/Mon Dec 8 05:31:39 2003// /lastlog/1.6/Mon Dec 8 06:13:00 2003// /ignore/1.6/Thu Jun 17 00:03:24 2004// /server/1.6/Thu Jun 17 00:03:34 2004// /license/1.2/Wed Mar 9 22:59:01 2005// help/1_General/1_General0100644000014400001440000000116407326073522014717 0ustar jnelsonusers# $EPIC: 1_General,v 1.4 2001/05/03 21:00:51 jnelson Exp $ Section 1: General-Purpose Commands  This section contains the most basic commands of EPIC. You will not have much success with IRC until you become familiar with these commands. This section will show you how to connect and disconnect to servers, join and leave channels, change your nickname, send messages to other people, and other fundamental irc operations. You will also want to read the help files in section 2. Most of the problems that new users have are solved by reading the help files in these two sections. help/1_General/away0100644000014400001440000000461207765006273014072 0ustar jnelsonusers# $EPIC: away,v 1.10 2003/12/05 12:16:13 brian Exp $ Synopsis: away [[] ] Description: When you leave your client, you will want to let the server know you are gone so it can tell anyone who tries to send you a message that you are not paying attention to irc. You can tell the server that you have returned by not giving an away message. While you are away: * The STATUS_AWAY expando (%A) will be displayed in your status bar using the value of /SET STATUS_AWAY (which is "(away)" by default). * If someone sends you a message, the server will send them your away message. * If someone WHOISes you, the server will include your away message in the reply. * If someone WHOs you or a channel you are on, your "away" status will be "G" (for Gone), instead of "H" (for Here). * If /SET BEEP_WHEN_AWAY is ON, your display will be beeped each time someone sends you a message. * If /SET AUTO_UNMARK_AWAY is ON, and you send a message or notice to someone else, the AWAY command will be run automatically to let the server know that you have returned. Remember to execute the AWAY command with no arguments when you return, so the server will know that you are back! If you get tired of seeing other people's away messages each time you send them a message, you can load the newaway script (/LOAD newaway) and you will see each person's away message only once. Options: -one send away message to only your current server (default) -all send the away message to all servers you are connected to -- literal; disabled argument parsing for all text to the right of the double hyphens. Examples: To mark yourself away: /away I'm not here right now, I'll be back soon To mark yourself away on all servers: /away -all I'm in the shower, back in 10 minutes To remove your away status: /away See Also: load(5) newaway; set(4) beep_when_away, status_away; who(2); whois(2); newaway(8) Portability concerns: Some networks do not send your AWAY message to other servers after a net.split has healed. Once a net.split occurs, your AWAY status and message are lost on the other side of the net.split. Most servers restrict your AWAY message length. Try to keep your away message under 80 characters. help/1_General/bye0100644000014400001440000000063407326073522013702 0ustar jnelsonusers# $EPIC: bye,v 1.7 2001/05/03 21:00:51 jnelson Exp $ Synopsis: bye [] Description: The bye command is equivalent quit. See the help file for quit for more information. Examples: To quit from IRC with a message: /bye I'll be back soon! See Also: bind(4) quit_irc; disconnect(1); on(5) channel_signoff, quit, signoff; set(4) quit_message help/1_General/channel0100644000014400001440000001164207402426542014533 0ustar jnelsonusers# $EPIC: channel,v 1.6 2001/11/27 22:06:33 anders Exp $ Synopsis: channel [-invite| []] window channel "-invite| []" About channels: 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 every other network. You can join a channel with the JOIN (or CHANNEL) command. The JOIN command takes one argument, which is the name of the channel that you want to join. If you do not know the name of a channel, then you can try joining the #irchelp channel to get started. Channels "exist" as long as there is one person in them. When the last person leaves a channel, the channel "goes away". When the first person join a channel, the channel is "created". The creator of a channel becomes the channel operator. Whenever you join a channel, you become a "member" of that channel. Channel operator privilege can be shared amongst all of the members of the channel. Network channel names always begin with the # character. Channels that exist only on your server always begin with the & character. Some networks have channels that do not allow the MODE command and those channels always begin with the + character. Channel names can be up to 200 characters in length (though most channel names are 1 to 10 characters long), and can contain any character except SPACE, BELL, NUL, CR, LF, and the comma. Some networks permit you to restrict your channel to only users from a certain host pattern. On those networks, you append to the channel name the colon character (':') followed by a hostmask. Only users with hostnames that match the hostmask will be permitted to join your channel. You may join more than one channel at a time by separating the list of channels you want to join with commas. If a channel requires a "key" to enter, provide the channel key as the second argument to the JOIN command. Try to avoid joining more than one channel at a time if any of the channels have a key, as not every server can handle this correctly. Joining each channel with a key separately will work the best. You cannot always join every channel all of the time. A channel's mode may restrict you from joining it. If the +k mode (key) is set, then you must use the key (password) to join. If the +i mode (invite-only) is set, then you must be INVITEd by a channel operator to join. If the +l mode (limited membership) is set, and the number of members in the channel has reached the limit, then you cannot join. If a +b mode (ban) has been set for your hostmask, then you cannot join. On some networks, if a +e mode (exception to ban) has been set for your hostmask, you can join even if there is a +b mode for your hostmask. Please read the MODE help file for more detailed information about channel modes. Description: If you do not use any arguments, the JOIN command will show you a list of all of the channels you have joined and the information that is known about those channels. If you do use arguments, the first argument must be a comma separated list of channels you want to join. If any of your channels require a key (the channel mode +k is set) then you must specify that key as the second argument. Care should be taken when joining multiple channels with keys at the same time because not all networks do it the same way. If you specify one channel, then that channel will be made the current channel in the window you do the /JOIN in (as if you did a /WINDOW CHANNEL). CAUTION! If you specify more than one channel, none of them will be made the current channel. Options: -invite You will join the last channel to which you were INVITEd. Examples: To join channel #irchelp (or create it if it does not exist): /channel #irchelp To join channel #blah that has the key "foobar": /channel #blah foobar To join more than one channel at once: /channel #foo,#bar,&blah To join a channel that only German users may join: (on some networks) /channel #blah:*.de To join channel #blah if you have been invited to it (either will work, although the first is better, since channel names may contain characters that your terminal can't display): /channel -invite /channel #blah Aliases: CHANNEL and //JOIN are identical to WINDOW CHANNEL when provided an argument. CHANNEL and //JOIN are identical. The JOIN alias is a friendly front end to the CHANNEL command. See Also: bind(4) switch_channels; invite(1); mode(1); on(5) join; window(4) channel help/1_General/describe0100644000014400001440000000236107402426542014701 0ustar jnelsonusers# $EPIC: describe,v 1.5 2001/11/27 22:06:33 anders Exp $ Synopsis: describe Description: 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. DESCRIBE is identical to CTCP ACTION. When sending an action to a channel, it functions identically to the ME command. Because this makes use of CTCP (Client To Client Protocol), it is not guaranteed that the person to whom you send the description will see it properly. If the person's client does not properly handle it, you may receive an error message back. This is normal and may be safely ignored. Examples: If your nickname is foobar, and you want to send an action to your friend whose nickname is booya: /describe booya is eating pizza To send an action to channel #blah: /describe #blah is eating pizza Anyone receiving an action from you will see something like this: * foobar is eating pizza Aliases: See Also: ctcp(1) action; load(5) action, mudlike; me(1); on(5) action, send_action help/1_General/disconnect0100644000014400001440000000111607326073522015250 0ustar jnelsonusers# $EPIC: disconnect,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: disconnect [ []] Description: This command disconnects you from your server, but does not actually make the client quit. If you are connected to multiple servers in multiple windows, the client will only close the connection to the server in the current window. Examples: To disconnect from your current server: /disconnect To disconnect from server 2 in your server list: /disconnect 2 I'll be back later! See Also: reconnect(1); server(1) help/1_General/help0100644000014400001440000000372007326073522014052 0ustar jnelsonusers# $EPIC: help,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: help [ [ ...]] Description: The HELP command is your interface to the online help system in EPIC. The EPIC help system divides the various help documents into logical groups, and each group is given a unique section number. Help files are arbitrarily structured. Each file should include, at the very least, a synopsis and description (such as this file). Some files also include a description of options supported by the command, a list of aliases to the command, warnings of bugs, or other information. Some also include a list of related help topics. These references are usually followed by a number in parentheses. This number is the help section that the command is listed under. Help file names are not sensitive to case (e.g. "HELP" is the same as "help"), and they may be abbreviated unambiguously (e.g. "hel" is the same as "help", but "wh" is ambiguous because it matches "who", "whois", "whowas", etc.). The HELP command can peruse any arbitrary hierarchy of text documents. Some scripts document their features by way of HELP documents and use SET HELP_PATH to point to them. The HELP command may not be terribly useful on its own because you have to know the section headers ahead of time. Use the /MAN alias (LOAD man) for a friendly interface to the EPIC help files. Options: -wait The command shall not return for as long as the help system is in use. If the help system is not active, it shall return immediately. Examples: To get help on the WHOIS command (in section 3): /help 3 whois To list all of the help files in section 3 (server queries): /help 3 ? To list all help sections: /help See Also: Introduction(7); New_User(7); on(5) help; set(4) help_pager, help_path, help_prompt, help_window help/1_General/ignore0100644000014400001440000000765010064157714014412 0ustar jnelsonusers# $EPIC: ignore,v 1.6 2004/06/11 02:27:32 jnelson Exp $ Synopsis: ignore [] [[-|+|^]] ignore [] [[-|+|^]] ignore [] [[-|+|^]] ignore [] [[-|+|^]] ignore [] [[-|+|^]] ignore [] [] [REASON ""] ignore [] [] [REASON ""] Description: The IGNORE command is a client-side filtering mechanism. You can use it to avoid seeing messages you would rather not see. This does not stop someone from flooding you, but it does stop your screen from being flooded. If someone attacks you with a floodnet, you can still be knocked off of irc even if you IGNORE it. Messages can be filtered based on any nick!user@host pattern, (which can be abbreviated to just a nick, or just a user@host) or on any channel. Messages are filtered by context type. This allows you to ignore only certain types of messages from someone without having to ignore every message from that person. For example, you could ignore INVITEs from someone who is annoying you without having to ignore his MSGs. IGNORE will apply a filter based on the best possible match. Thus, if you are ignoring *!*@*.net and *!*foobar@*.slurpee.net, and someone with an nick!user@host mask of BigFoob!foobar@grape.slurpee.net sends you a message, IGNORE will use *!*foobar@*.slurpee.net to determine how to filter the message. This will prove useful, as shown in the example below. Using IGNORE with no arguments displays your ignore list. This will include an ignore reference number, the pattern being ignored/highlighted, and the type of messages that shall be ignored/highlighted. Optionally, a ignore reason and timeout may be included. Most, but not every ignore level works with channels. When you are trying to remove an ignore, you must specify the pattern exactly as it appears in your ignore list. "Approximate" patterns will be treated as NEW patterns and will not supersede existing patterns. Message Types: ctcps filter in/out all CTCPs received invites filter in/out all INVITEs received msgs filter in/out all MSGs received (but not CTCPs) notes filter in/out all NOTEs received notices filter in/out all NOTICEs received public filter in/out public channel conversation wallops filter in/out operator WALLOPS topics filter in/out all TOPIC changes nicks filter in/out all NICK changes joins filter in/out all channel JOINs parts filter in/out all channel PARTs crap filter QUIT, MODE, KICK and PONG all everything listed above none remove pattern from list of filtered patterns Special Message Types: These are not really message types, but they can be used in your message types list. REASON "" Set a reason you're ignoring the person. TIMEOUT Automatically cancel the message after seconds. Examples: To ignore everything from foobar: /ignore foobar all To ignore everything except public conversation from foobar: /ignore foobar all -publics To highlight all private messages from foobar (it is displayed highlighted with whatever you have set HIGHLIGHT_CHAR to): /ignore foobar +msgs To ignore all NOTICEs except those from foobar's site: /ignore * notices /ignore *!*@*.slurpee.net ^notices To remove *!*foobar@*.slurpee.net from your ignore list: /ignore *!*foobar@*.slurpee.net none To highlight people joining and leaving, mode changes, etc. for a channel: /ignore #channel +crap See Also: set(4) highlight_char, send_ignore_msg; silence(1); igmask(6); rigmask(6); igtype(6); rigtype(6) help/1_General/invite0100644000014400001440000000122007326073522014411 0ustar jnelsonusers# $EPIC: invite,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: invite Description: 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. Examples: To invite foobar to channel #blah: /invite foobar #blah To join the last channel you were INVITEd to: /join -invite See Also: join(1); mode(1); on(5) invite help/1_General/join0100644000014400001440000000370107402426542014057 0ustar jnelsonusers# $EPIC: join,v 1.6 2001/11/27 22:06:33 anders Exp $ Synopsis: //join [-invite| []] join (join channel you were invited to) join [,] (comma separate multiple channels) [keys do not work with commas] join channel (will auto-prepend a # for you) join #channel (join a network channel) join &channel (join a local server channel) join !channel (join an IRCNet "id" channel) join +channel (join an IRCNet "modeless" channel) join 0 (part all channels) Description: When prefixed with two /'s, the JOIN command is the same as CHANNEL whose help file you should refer to. When not prefixed with two /'s, the JOIN command is a friendly script alias that is loaded in the 2.8script script that is automatically loaded each time you use epic. You may delete or override this JOIN alias in your ~/.ircrc file if you so choose. If you do not specify an option, the JOIN command will join the last channel to which you were invited. If you have not been invited to a channel, you will be told so. You may specify a comma-separated list of one or more channels to join; each channel name so listed is treated as such: A channel starting with #, (eg, #channel) will be joined A channel starting with &, (eg, &channel) will be joined A channel starting with !, (eg, !channel) will be joined A channel starting with +, (eg, +channel) will be joined The channel 0 will part all your channels Any other channel name will be prefixed with a # and will be joined (eg, "foo" becomes "#foo") You may not specify more than one channels and channel keys at the same time. This may be fixed in future JOIN aliases, but for now, you must use the CHANNEL command to join more than one channel at the same time that you specify a channel key. It may just be easier to join your keyed channels separately. help/1_General/kick0100644000014400001440000000315307326073522014043 0ustar jnelsonusers# $EPIC: kick,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: kick *| [] Description: 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. Again, you must be a channel's operator in order to remove other members from the channel. On some networks (notably the undernet), some users (users with user mode +k turned on, such as the channel service) may not be removed with the KICK command. From a purely technical point of view, any channel operator may remove any channel member (including themselves) at any time for any reason whatsoever. Notwithstanding this, some channels may have structure and rules governing the discretionary use of the KICK command by its operators. Failure to obey these rules would constitute a breach of trust and you may find your friends no longer op you when you join. This is, as we say, "tough luck". You should be old enough that we don't have to tell you that others will treat you in the same way you treat them, and picking fights with others is rude. Examples: To remove foobar from channel #blah: /kick #blah foobar Go away! To remove foobar from your current channel: /kick * foobar I said go away!! See Also: ignore(1); load(5) autokick; mode(1); on(5) kick help/1_General/lastlog0100644000014400001440000000503207765013154014567 0ustar jnelsonusers# $EPIC: lastlog,v 1.6 2003/12/08 06:11:26 brian Exp $ Synopsis: lastlog [-] [-] [--] [] [ []] Description: 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. For backwards compatibility reasons, up to three non-option arguments are acceptable: * If the first option specified is not a number, then it is treated as if it were the argument to the -LITERAL option. This MUST be the first non-option argument. See gotcha #1 below. * The first number is the number of lines to look at. * The second number is the position in the lastlog to start at. Options: - Do not display the "Lastlog:" and "End of Lastlog" lines. -literal Show lines that contain this literal string. See gotcha #2. -max Show only the first lines that match. -reverse Show all lines in reverse order; from the END to the BEGINNING. -file Write output to . -LASTLOG_LEVEL Where LASTLOG_LEVEL is one of the lastlog levels listed in SET LASTLOG_LEVEL; show messages of this type. --LASTLOG_LEVEL Where LASTLOG_LEVEL Is one of the lastlog levels listed in SET LASTLOG_LEVEL; do not show messages of this type. -target Show only lines with this display target. Examples: To list all private messages from JoeBob: /lastlog -msg joebob To list all public messages from JoeBob in the last 100 lines /lastlog -public joebob 100 To list all occurrences of the phrase "ircII-EPIC is cool" from 100 to 600 lines ago: /lastlog "ircII-EPIC is cool" 100 500 To list everything *except* messages: /lastlog -all --msgs To write everything containing "foo" to "lastlog.out": /lastlog -file lastlog.out foo To list only public messages to #epic: /lastlog -target #epic -public See Also: set(4) lastlog, lastlog_level, log, logfile; window(4) lastlog_level, log, logfile Gotchas: #1) If you do specify more than one non-option non-number leading arguments, the last one will be used. THIS MAY CHANGE IN THE FUTURE #2) You cannot specify more than one of these; the second and subsequent instances will be ignored. help/1_General/me0100644000014400001440000000217307326073522013524 0ustar jnelsonusers# $EPIC: me,v 1.2 2001/05/03 21:00:51 jnelson Exp $ Synopsis: me Description: 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. Examples: To perform an action: /me doesn't want to go to work today Anyone on the channel you sent the action to will see something like this: * foobar doesn't want to go to work today Aliases: ME functions identically to using DESCRIBE to send an action to your current channel, as well as to CTCP ACTION. See Also: ctcp(1) action; load(5) action, mudlike; describe(1); on(5) action, send_action Restrictions: This command makes use of CTCP (client-to-client protocol), which is not part of the IRC protocol. Most modern IRC clients understand CTCP, but not all do, while others might not support the same CTCP commands that ircII-EPIC supports. If you receive an error of some sort, then the client on the receiving end is unable to properly handle your CTCP message. help/1_General/mode0100644000014400001440000006271007607071246014055 0ustar jnelsonusers# $EPIC: mode,v 1.13 2002/10/05 02:56:57 kitambi Exp $ Synopsis: mode [<+|-> []] # 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 will be explained. # After this, a description of channel modes, with each channel mode explained. # Each network will get a section where its deviant channel modes will be # explained. # After all of this, will be a description of how to use the /mode command, # complete with examples. The first part of this help file should be put # in an external document at some point, but for now it's going to be in # here until we move it. About Modes: A mode is an irc attribute which describes the current state of a channel or irc user. These are called "channel modes" and "user modes". Modes are traditionally single characters, usually lower case letters, and are manipulated with the MODE command. You can turn on ("set") a mode by prefixing the character with a plus sign ('+') and turn off ("unset") a mode by prefixing the character with a minus sign ('-'). You can set or unset multiple modes at a time. User Modes: You can set and unset your user modes to change certain attributes about your irc session. User modes are lost when your server connection ends. You may be given a set of "default" user modes by your server when you initially connect to it. You may be given a set of extra user modes when the OPER command is successful. Some user modes are "privileged" which means that you cannot turn them on yourself; the server has to turn them on for you. You may not change or query the mode of any other user. Standard User Modes: i "Invisible mode". Everybody is permitted to ask for a list of members on a channel, or a detailed list of members on a channel with the NAMES or WHO request. If the requester is a member of the channel he requests, he will see the full details of all other members on the channel. However, if the requester is NOT a member of the channel he requests, any channel members who have this user mode set will NOT be shown in the list. They will be "invisible" to those who are not channel members. This same effect occurs if you are a member of a secret channel (channel mode +s, see below). o "Operator mode". This user mode is privileged. Some irc commands (relating to the administration of the irc server and network) may not be executed by those who do not have this user mode set. This mode must be enabled through the sucessful use of the OPER command, however, it can be removed with the MODE command s "Server Notices mode". The server sends out special information that is not generally useful to non-techie irc users when you turn this user mode on. Not every user receives every server notice just because they have +s turned on. Some server notices require more than one user mode to be turned on (particularly +o). The types and number of messages you receive varies from server to server. w "Wallops mode". Whereas server notices generally are of interest to local users, WALLOPS ("Write ALL OperatorS") are of interest to all privileged users on all servers. You will receive WALLOPS when you turn this user mode on. Some networks restrict WALLOPS only for server use. Other networks permit operators to send WALLOPS. Still other networks permit everybody to send WALLOPS. As with all other output modes, everything varies from server to server. Non-standard User Modes: Undernet (ircu2.9.x): d "Deaf mode". The server will not send public message to this client for any channels it is a member of. This mode is primarily intended for services, and may or may not be accessible to clients. k "No-kick mode". This user mode is privileged. All servers on the network will reject any attempt to KICK this client from any channel it is a member of. There is no way to the server to set this mode for you. DALnet (ircu2.9.x+DAL, DAL4.x, Bahamut, Dreamforge) g All will see nickname collisions. Those with user mode +o will also see all uses of the OPER command and all failed/aborted server connection attempts. h "Help mode". This user mode is privileged. The server will show you all uses of the HELP protocol command. All who WHOIS you will get the 310 server numeric indicating your +h status. IRCNet (irc2.9.x): r "Restricted mode". The server will not permit this client to become a channel operator either through the MODE command or through the JOIN command. The server will not permit this client to use the NICK command. You cannot unset this mode. (s) These servers do not have the +s user mode. EFnet [Comstud] (irc2.8.x+CSr27 and beyond): b When enabled, shows connects from potential bots, and attempts with invalid usernames. c When enabled, shows all clients connecting and disconnecting from your server. Limited to irc operators. d When enabled, shows connects where the username given and the client's ident response differ. f When enabled, shows all "Fake MODE" and "Nickname Collision" notices. k When enabled, shows all global and local operator kills. l When enabled, shows connect attempts from clients that exceed their connect class (Y:line) limit. (r) Replaced by +bdl after CSr25. s When enabled, it shows any miscellaneous server notices that are not shown with modes bcdfklu (even if they are not enabled). u When enabled, shows all unauthorized connect attempts, as well as connect attempts when the server has reached its maximum connection limit. EFnet [/th] servers (irc2.8/th): User Modes: c When enabled, shows all clients connecting and disconnecting from your server. Limited to IRC operators. d Debug mode, displays miscellaneous messages. Limited to irc operators. k When enabled, shows all server kills n Shows all local nickname changes. Limited to irc operators. r When enabled, shows all rejected connections. s When enabled, it shows any miscellaneous server notices that are not shown with modes ckr, including operator kills y Spy mode, informs operators of all LINKS, STATS, and TRACE commands issued, and of any failed MSG commands. EFnet Hybrid 6 servers (2.8/hybrid-6): User Modes: O Designates this client is a local IRC Operator. o Designates this client is a global IRC Operator. w Can see server wallops. May be irc operator only depending on server configuration. z Can see oper wallops. No function unless irc operator. s Can see generic server messages and oper kills. c Can see client connections and exits. No function unless irc operator. r Can see 'rejected' client notices. No function unless irc operator. k Can see server kill messages. f Can see 'I-line is full' notices. No function unless irc operator. y Can see stats/links/admin requests to name a few. No function unless irc operator. d Can see server debug messages. Note that if the server was compiled with DEBUG defined, this information can potentially be an invasion of user privacy. Limited to irc operators with D flag. n Can see client nick changes. Limited to irc operators with N flag. b Can see bot detection notices. No function unless irc operator EFnet Hybrid 7 servers (2.8/hybrid-7): All modes for EFNet Hybrid 6 Servers apply, and the following additional modes are available, or are changed in meaning. User Modes: (O) Obsolete. Hybrid-7 does not support local operators. a Server administrator flag. Automatically set by server in conjunction with the OPER command, not usable by normal users. g Reject all PRIVMSG/NOTICE not addressed to a channel, unless the sender has been authorized by the ACCEPT protocol command (presently you must use /quote for this) AnotherNet servers User Modes: c Show all [dis]connections, possible clones, and invalid logins f Show all DCC handshakes (mnemonic: file transfers) h Makes operator completely invisible to all normal users; mainly meant for channel services (mnemonic: hidden) UnderNet servers Server notice masks: Under ircu servers the +s usermode can optionally take a numeric argument prefixed by + or - This argument is used to show only specific types of server messages. 1 unsorted old messages 2 server kills (nick collisions) 4 oper kills 8 desyncs (hack2) 16 temporary desyncs (hack3) 32 unauthorized connections 64 common TCP or socket errors 128 too many connections 256 services actions on channels (hack4) 512 glines 1024 net join/break, etc 2048 IP mismatches 4096 host throttle add/remove notices 8192 old oper-only messages (Oper Only) 16384 client connect/exit messages (Oper Only) To set a server notice mask (allowing you to see that type of notice) /mode +s +mask Only one number may be specified, and it is added to your current server notice mask. However you can combine values before passing them to the mode command. To clear a server notice mask (preventing you from seeing that type of notice) /mode +s -mask Default server notice mask for users who just set +s usermode is 1540 (4+512+1024) Default server notice mask for opers is 1799 (1+2+4+256+512+1024) Channel Modes: You can set and unset your user modes to change certain attributes about a channel. Channel modes are lost when the last person leaves a channel (the channel is destroyed). Channels may be given a set of "default" channel modes by the server when you create it. The first person to join a channel creates it and becomes the channel operator. The mode of a channel may only be changed by one of its operators. The operatorship may be shared among any of the channel's members. be set and unset by channel operators. "prinitially nnect to it. You may be given a set of extra user modes when the OPER command is successful. Some user modes are "privileged" turn them on for you. You may not change or query the mode of any other user. Standard Channel Modes: b When enabled, this prevents the specified nick!user@host mask from entering the channel. If only the @host portion is specified, "*!*" is prepended; if only user@host is specified, "*!" is prepended; if the mask does not contain a "@", it is assumed to be a nickname, and a !*@* is appended. When used with no arguments, the channels list of "bans" is displayed. On some servers, this also prevents any users matching the specified nick!user@host mask from speaking on the channel or changing nicks. i When enabled, users may only join the channel if INVITEd. k When enabled, users may only join the channel if they specify the proper "key" (which is specified when +k is set). l When enabled, only the specified number of users may enter the channel. m When enabled, only users with +o or +v may speak on the channel. n When enabled, public messages from outside the channel are not allowed. o When enabled, grants the specified nickname channel operator status. p When enabled, the channel is made private. The channel name will not show up in WHO, WHOIS, NAMES, or LIST replies (though users who are not +i will still be shown in NAMES, the channel name is simply masked as "Private"). This no longer works as expected on all servers, as some have given +p other meanings. s When enabled, makes the channel secret. This is the same as +p, except the channel will not show up in any WHO/WHOIS/etc. queries from a person not on the channel. Anyone who is on a +s channel is effectively invisible, as per user mode +i. t When enabled, only channel operators may set a topic. v When enabled, grants the specified nickname voice status. IRCNet Channel Modes: a When enabled, this makes the channel anonymous. Nicknames are hidden (and thus nick changes are not shown), and no other channel modes are permitted. Note that this can seriously confuse the client... I Invite exemption. This takes a hostmask like a ban would, and acts as a perminant invite. e Ban exemption. Same format as +b, except user matching a ban exemption can join regardless of bans. Hybrid6 Channel Modes: e Ban exemption. Same format as +b, except users matching a ban exemption can walk through any bans matching them. The server may remove ban exemptions automatically when a ban-exempt client is kicked shortly after joining through a ban. p Paranoid. Channel operators will see when another channel operator invites someone. (this differs from the old chanmode p, which was formerly used for "private" mode) Beware that this will not have the desired effect in a mixed hybrid-6/hybrid-7 network, as +p is redefined to mean knock disable in hybrid-7. Hybrid7 Channel Modes: a Anonymous channel operators. Channel operators will not be identified as channel operators, and channel operator commands will not reveal the identity of a channel operator. e Ban exemption. Same format as +b, except users matching a ban exemption can walk through any bans matching them. The server may remove ban exemptions automatically when a ban-exempt client is kicked shortly after joining through a ban. p Knock Disable - This differs yet again from previous uses for the +p channel mode, which previously meant "private" or "paranoid". Setting this mode on a channel will prevent KNOCK from being used on hybrid-7 servers. This will not have the expected results on a mixed hybrid-6/hybrid-7 network! I Invite exemption. This takes a hostmask like a ban would, and acts as a perminant invite. Description: Both channels and users have modes associated with them. For channels, they determine who is a channel operator, the number of people who may join the channel, who may not enter the channel, and myriad other things. For users, they determine whether the user will is an IRC operator, whether the user will receive special server notices, etc. Modes are enabled when prepended with a "+", and disabled when with a "-". Modes may be clustered as well. When clustering modes, all mode changes are specified first, then their parameters (see the examples below). Examples: To receive operator WALLOPS and server notices (both examples are equivalent): /mode your_nick +sw /mode your_nick +s+w To set a channel limit (the number is arbitrary): /mode #channel +l 35 To make someone a channel operator: /mode #channel +o theirnick To set a ban, a key, and to remove chanop status from someone: /mode #channel +bk-o *!*some@*.ban.com Secret_Key foobar See Also: chanmode(6); deop(4); invite(1); key(6); kick(1); on(5) mode, mode_stripped; oper(4); set(4) mode_stripper; usermode(6); wallops(4) Restrictions: Only channel operators may set modes for a channel (though anyone may view them), and only you may set or view your personal user modes. Additionally, the user mode +o may NOT be set with MODE, you must use the OPER command. However, it may be removed with -o (see DEOP as well). Also note that some server variants do not allow for redundant mode changes, such as "+oo foobar foobar". This shouldn't cause too many problems though, since you can easily reverse a mode if you wish to set it again, such as "-o+o foobar foobar", which is allowed. Finally, note that mode changes are limited to a maximum of 4 total parameters. Thus you could give +o to 3 people and set +l, but you could not do those and set +k as well, since that would involve 5 parameters. Other Notes: On Undernet servers, the maximum number of parameters for MODE is 6. Additionally, some server versions have extra modes that may be used. Keep in mind that these do not apply everywhere, so you should check what software version your server is using to be sure (see VERSION). Undernet servers (ircu2.9.x): User Modes: d When enabled, your client does not receive any public messages from any channel you are on. (mnemonic: deaf mode) k No-kick mode. Any client with this mode may not be kicked from any channel it applies to. Limited to services. DALnet servers (ircu2.9.x+DAL, DAL4.x) User Modes: g Allows operators to see all OPER attempts, and failed server connects. Allows all users to see nickname collisions. h Shows operators the arguments to any protocol HELP command issued. Server numeric 310 is returned in WHOIS to denote +h users. IRC 2.9 servers (irc2.9.x): User Modes: r When enabled, the client cannot be a channel operator (even if it is the first to join), nor can it change nicknames. This mode is automatic if the connecting client has a matching i: line. This mode cannot be reversed once enabled. (s) Version 2.9 servers do not have a +s user mode. Channel Modes: a When enabled, this makes the channel anonymous. Nicknames are hidden (and thus nick changes are not shown), and no other channel modes are permitted. Note that this can seriously confuse the client... EFnet +CS servers (irc2.8.x+CSr27 and beyond): User Modes: b When enabled, shows connects from potential bots, and attempts with invalid usernames. c When enabled, shows all clients connecting and disconnecting from your server. Limited to irc operators. d When enabled, shows connects where the username given and the client's ident response differ. f When enabled, shows all "Fake MODE" and "Nickname Collision" notices. k When enabled, shows all global and local operator kills. l When enabled, shows connect attempts from clients that exceed their connect class (Y:line) limit. (r) Replaced by +bdl after CSr25. s When enabled, it shows any miscellaneous server notices that are not shown with modes bcdfklu (even if they are not enabled). u When enabled, shows all unauthorized connect attempts, as well as connect attempts when the server has reached its maximum connection limit. EFnet /th servers (irc2.8/th): User Modes: c When enabled, shows all clients connecting and disconnecting from your server. Limited to IRC operators. d Debug mode, displays miscellaneous messages. Limited to irc operators. k When enabled, shows all server kills n Shows all local nickname changes. Limited to irc operators. r When enabled, shows all rejected connections. s When enabled, it shows any miscellaneous server notices that are not shown with modes ckr, including operator kills y Spy mode, informs operators of all LINKS, STATS, and TRACE commands issued, and of any failed MSG commands. EFnet Hybrid 6 servers (2.8/hybrid-6): User Modes: O Designates this client is a local IRC Operator. o Designates this client is a global IRC Operator. w Can see server wallops. May be irc operator only depending on server configuration. z Can see oper wallops. No function unless irc operator. s Can see generic server messages and oper kills. c Can see client connections and exits. No function unless irc operator. r Can see 'rejected' client notices. No function unless irc operator. k Can see server kill messages. f Can see 'I-line is full' notices. No function unless irc operator. y Can see stats/links/admin requests to name a few. No function unless irc operator. d Can see server debug messages. Limited to irc operators with D flag. n Can see client nick changes. Limited to irc operators with N flag. Channel Modes: e Ban exemption. Same format as +b, except users matching a ban exemption can walk through any bans matching them. p Paranoid. Channel operators will see when another channel operator invites someone. (this differs from the old chanmode p, which was formerly used for "private" mode) EFnet Hybrid 7 servers (2.8/hybrid-7): All modes for EFNet Hybrid 6 Servers apply, and the following additional modes are available, or are changed in meaning. User Modes: a Server administrator flag. Automatically set by server in conjunction with the OPER command, not usable by normal users. g Reject all PRIVMSG/NOTICE not addressed to a channel, unless the sender has been authorized by the ACCEPT protocol command (presently you must use /quote for this) Channel Modes: a Anonymous channel operators. Channel operators will not be identified as channel operators, and channel operator commands will not reveal the identity of a channel operator. I Standing Invitation. Format is the same as a ban. Users matching will be able to join regardless of the +i mode, as if they had been given an INVITE by one of the ops. AnotherNet servers User Modes: c Show all [dis]connections, possible clones, and invalid logins f Show all DCC handshakes (mnemonic: file transfers) h Makes operator completely invisible to all normal users; mainly meant for channel services (mnemonic: hidden) UnderNet servers Server notice masks: Under ircu servers the +s usermode can optionally take a numeric argument prefixed by + or - This argument is used to show only specific types of server messages. 1 unsorted old messages 2 server kills (nick collisions) 4 oper kills 8 desyncs (hack2) 16 temporary desyncs (hack3) 32 unauthorized connections 64 common TCP or socket errors 128 too many connections 256 services actions on channels (hack4) 512 glines 1024 net join/break, etc 2048 IP mismatches 4096 host throttle add/remove notices 8192 old oper-only messages (Oper Only) 16384 client connect/exit messages (Oper Only) To set a server notice mask (allowing you to see that type of notice) /mode +s +mask Only one number may be specified, and it is added to your current server notice mask. However you can combine values before passing them to the mode command. To clear a server notice mask (preventing you from seeing that type of notice) /mode +s -mask Default server notice mask for users who just set +s usermode is 1540 (4+512+1024) Default server notice mask for opers is 1799 (1+2+4+256+512+1024) help/1_General/msg0100644000014400001440000000605707402426542013715 0ustar jnelsonusers# $EPIC: msg,v 1.4 2001/11/27 22:06:33 anders Exp $ Synopsis: msg msg msg = msg % msg / Description: The /msg command is how you send a message to someone else. You can send a message to another nick on irc, to a channel, to someone you have a DCC CHAT connection open with, to an /exec'd process, or to an EPIC command. You may use a comma-separated list (no spaces) to send a single message to more than one recipient at a time. You may freely mix and match each of the types of targets in any way you want. There are three "magic" recipients. The comma (',') recipient is the last person to send you a message. The period ('.') recipient is the last person you sent a message to. The asterisk ('*') recipient is the current channel in your current window. These "magic" recipients may not be included with any other recipients in a comma-separated list; they must be used alone. There are never any restrictions on sending a /msg to an /EXEC target, a /DCC CHAT target, or an /ALIAS target. However, from within an /ON MSG, /ON PUBLIC, /ON DCC_OFFER, or any other /ON that occurs because of a "PRIVMSG", the /MSG command (and other commands that send PRIVMSGs, such as /SAY, /SEND, /CTCP, and /DCC) sends your message with a "NOTICE". The effect of this is that you cannot properly use /DCC CHAT or /DCC SEND from within these /ON's. This requirement is specified by the irc protocol and is intended to prevent infinite message loops between clients. You may not always be able to send a message to a channel. If the channel mode is +n, you must be a member of the channel to send a message to it. If the channel mode is +m, you must be a member of the channel and also must either be a channel operator (+o) or a channel voice (+v) to send a message to it. The MODE help page talks about this in more detail. You may not always be able to send a message to multiple irc targets. Because of the spread of spambots/floodbots, some servers restrict the number of irc targets you can send a message to in any one message. As with every server restriction, what happens if you exceed this limit varies from server to server. Examples: To send a private message to your friend Buddha: /msg buddha hi there! To send a message to your current channel: /msg #channel how is everyone today? To send a message to the running EXECed process with id 2: /msg %2 exit To send a message to your friends buddha, booya (with whom you have a DCC CHAT running), and channel #foobar: /msg buddha,=booya,#foobar see you later! To send a message to an EXECed process named "mail": /msg %mail x See Also: dcc(1) chat; exec(5); load(5) nicks; notice(1); on(5) msg, public_msg, send_msg; query(1); say(1); send(5); set(4) beep_on_msg help/1_General/nick0100644000014400001440000000336307326073522014051 0ustar jnelsonusers# $EPIC: nick,v 1.4 2001/05/03 21:00:51 jnelson Exp $ Synopsis: nick [] Description: 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. If you do not specify a new nickname, your current one is displayed. The maximum length of nicknames is determined by the server you are using. The traditional nickname length is 9 characters. On dalnet type servers the length is 30 characters. As with all server features, it varies from server to server. The protocol defines as alphabetical characters the ascii characters from 65 ('A') through 125 ('}'). Characters 65 through 93 are equivalent to the corresponding characters 97 through 125, as such: ABCDEFGHIJKLMNOPQRSTUVWXYZ[\] abcdefghijklmnopqrstuvwxyz{|} The [, \, ], (upper case) and {, |, } (lower case) letters are used as the 7-bit ascii substitutes of some european national characters, particularly scandanavian characters. It is important to note that the two nicknames "[testnick]" and "{testnick}" are, in fact, the SAME nickname in irc, just as "testnick" and "TESTNICK" are the same. A nickname shall be composed of an alphabetical character (as defined) followed by some number of alphanumeric characters, the total number of characters not to exceed the server's maximum nickname size (as defined). Examples: To change your nick to foobar: /nick foobar To display your current nickname: /nick See Also: on(5) channel_nick, nickname; set(4) auto_new_nick help/1_General/notice0100644000014400001440000000201007326073522014372 0ustar jnelsonusers# $EPIC: notice,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: notice notice notice = notice % notice / Description: The syntax, form, and argument list of the NOTICE command is precisely the same as the /MSG command. See the /MSG help file for information regarding how to use the /NOTICE command. There are never any restrictions on sending a /notice to an /EXEC target, a /DCC CHAT target, or an /ALIAS target. However, It is never permitted to send a message (either a /MSG or a /NOTICE or a /DCC or a /CTCP, or any other message-sending command) to an irc target in response to a NOTICE (ie, inside an /ON NOTICE). If you attempt to do so, EPIC will display an error message and your message will not be sent to any irc targets. See Also: msg(1); on(5) notice, public_notice, send_notice help/1_General/notify0100644000014400001440000000372107326073522014433 0ustar jnelsonusers# $EPIC: notify,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: notify notify - notify [[+] [[+] ...]] notify [[-] [[-] ...]] Description: 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. When given no arguments, the /NOTIFY command will show you all of the nicknames in your list that are on that network, and all of the nicknames in your list that are NOT on that network. When given just a single '+' as an argument, it will show only those who are on the network (and not those who are not). When given just a single '-' as an argument, your notify list will be cleared. There is no way to automatically recreate your notify list once you clear it. When given a list of nicknames, each of which is prefixed either by a plus ('+'), a minus ('-') or neither, each nickname that is prefixed by a plus or by neither will be added to your notify list, and each nickname that is prefixed by a minus will be removed from your notify list. The notify command can only work on exact nickname matches. Wildcards are not supported and do not work. The notify command cannot track user or hosts; only exact nickname matches will work. You must not suppress the 303 numeric (with an /on raw_irc) or /notify will irreparably break. You cannot recover from this, so don't try it. Examples: To add your friends scuba and diver to your notify list: /notify scuba diver To remove your ex-friend buddha from your notify list: /notify -buddha To clear your notify list: /notify - To show your friends that are current logged on irc: /notify + See Also: ison(2); notify(6); set(4) notify_handler help/1_General/part0100644000014400001440000000247507520402220014061 0ustar jnelsonusers# $EPIC: part,v 1.5 2002/07/05 12:26:38 wd Exp $ Synopsis: part |* [] Description: 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. The "magic" channel star ("*") is a substitute for your current window's current channel. You may part more than one channel at a time, by separating each channel name with commas. You may not specify the magic star channel with any other channel names; it must be used alone. The LEAVE alias that is provided by 2.8script does not have this restriction. When you part a channel, all other members of the channel are notified. Some servers permit you to give a "part message" which will be shown to the other members of the channel. As with all server extension, whether or not you can do this varies from server to server. Examples: To leave channel #foobar with a reason: /part #foobar I'm going to #fubar, it's cooler! To leave your current channel: /part * To leave channels #foo and #bar at the same time: /part #foo,#bar See Also: 2.8script(8); join(1); on(5) leave help/1_General/ping0100644000014400001440000000316607402426542014062 0ustar jnelsonusers# $EPIC: ping,v 1.4 2001/11/27 22:06:33 anders Exp $ Synopsis: ping ping Description: 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 receive the message back, you can then measure the amount of time it took to come back and that will tell you how much lag there is to that person. This command uses the CTCP PING command to do its work. This command actually sends a message to the other person who will then send another message back. If the server (or network) is already overloaded with traffic, this will only add to the burden. PINGing people frequently will make the lag worse, so be reasonable. Not every client will respond to a PING request. You are not guaranteed to receive a reply to a PING command. Some clients will mangle the PING request rendering the results invalid. You are not guaranteed to receive an accurate reply to a PING command. The PING command uses the CTCP command and so will not work from within an /ON MSG, /ON PUBLIC, /ON PUBLIC_OTHER, /ON NOTICE, or the like. Examples: To see how far away your friend booya is from you: /ping booya To see how far away everyone in channel #blah is: /ping #blah See Also: ctcp(1) ping help/1_General/query0100644000014400001440000000101507326073522014262 0ustar jnelsonusers# $EPIC: query,v 1.2 2001/05/03 21:00:51 jnelson Exp $ Synopsis: query query query query = query % query / Description: The QUERY command is exactly the same as WINDOW QUERY. See the help file for WINDOW QUERY(4) for details. Examples: To start a private conversation with your significant other: /query sweetypie To cancel a running query: /query See Also: window query(4) help/1_General/quit0100644000014400001440000000136507326073522014107 0ustar jnelsonusers# $EPIC: quit,v 1.2 2001/05/03 21:00:51 jnelson Exp $ Synopsis: quit [] Description: When you are all done using EPIC, you can use the QUIT command to exit from IRC and go back to your shell. If a quit message is supplied, it will be sent to the server who will send it to each person who is on all of the channels that you are on. If you do not provide a quit message, then epic will use the value of /SET QUIT_MESSAGE. Examples: To quit from IRC with a message: /quit I'll be back soon! Aliases: BYE, EXIT and SIGNOFF are identical in operation to QUIT. See Also: bind(4) quit_irc; disconnect(1); on(5) channel_signoff, quit, signoff; set(4) quit_message help/1_General/reconnect0100644000014400001440000000252007326073522015077 0ustar jnelsonusers# $EPIC: reconnect,v 1.3 2001/05/03 21:53:30 jnelson Exp $ Synopsis: reconnect [] Description: There are times when your server connection gets "stuck" and things just are not working correctly. Sometimes this is due to lag, sometimes this is due to a server bug, and sometimes this is (gasp, horror) due to a bug in EPIC. Sometimes you want to change your REALNAME or your IRCNAME. No matter what the cause, whenever you need to disconnect from the server and immediately reconnect again, use the RECONNECT command. If you provide a "reason" it will be used as your QUIT message. This command behaves in a way very similar to doing a DISCONNECT followed by an appropriate SERVER. EPIC will (attempt to) rejoin your channels after the reconnection succeeds. EPIC does not guarantee that non-current channels will be put back in the same window as before the reconnection. This is not a bug, but is a limitation of EPIC. Only current channels (and bound windows) will go back to the same window. RECONNECT always reconnects to the server of the current window. You cannot RECONNECT to a server other than your current window's server. This may be changed in the future. See Also: discon(1); disconnect(1); realname(4); server(1); set(4) realname help/1_General/say0100644000014400001440000000203007326073522013707 0ustar jnelsonusers# $EPIC: say,v 1.4 2001/05/07 15:48:41 jnelson Exp $ Synopsis: say Description: 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. This is the command that you would use an a BIND, ALIAS, ON, or other commands to send a message to the current channel. The SEND command sends a message to the current target, which may be different than the current channel! SAY can only send a message to the current channel of a window. To send a message to a non-current channel, either use the MSG command, or use the SWITCH_CHANNELS key binding to make the desired channel the current channel. Examples: To send a message to the current channel: /say hello all! To someone else on irc, your message may appear like this: hello all! To you, your message may appear like this: > hello all! See Also: msg(1); send(5); help/1_General/server0100644000014400001440000001611210064157726014431 0ustar jnelsonusers# $EPIC: server,v 1.6 2004/06/17 00:03:34 jnelson Exp $ Synopsis: server server [|] server [+|-][] server [-add] [see below] server [-delete ] About irc servers: 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 list of others. The above list classifies the most likely types of servers you will encounter. There are some irc-like implementations, most of which have been devised for microsoft windows operating systems. EPIC does not promise to work on any server that diverges significantly from traditional irc (which these servers usually do) and so we will not consider these servers at all in this discussion. At the most basic level, all unix irc servers in widespread use have a direct lineage to one common ancestor, ircd2.8. Therefore, the features provided by ircd2.8 are portable to all irc servers. This includes the ability to join channels, to send messages to other users, to set topics, channel and user modes, to kick users from channels, and the like. How- ever, through the course of time many extensions have been added to the ircd software, and a particular set of extensions to ircd are distributed as a software package and typically are used by an entire network. Each server "class" defines a loose set of extended functionality that is available to the user whenever you use that class of server. That server's extensions may not be available on other servers, or it may be available in a different way. How EPIC gets your server list: How does EPIC know what servers you want to use? EPIC always tries to keep a server list, even if it contains only one server. The contents of the server list will always contain: * All servers, if any, you list on the command line. * The value, if any, of the IRCSERVER environment variable. If the server list is still empty *or* if you use the -a command line option, then EPIC will read the "servers file", which is: * The value of the IRC_SERVERS_FILE environment variable, if any. * Otherwise the value of #define SERVERS_FILE (usually ircII.servers) The "servers file" can be an absolute path or start with a tilde (for home directory expansion), but if it is neither, then the file will be looked for in the IRCLIB directory, which is: * The value of the IRCLIB environment variable, if any * The value of #define IRCLIB in config.h If all of the above fails, EPIC will use the value of #define DEFAULT_SERVER_LIST which is there only as a failsafe and not as a useful default server list. About server descriptions: A server description is a colon-separated list of several data items that changes from time to time. At the time of this writing, the current list was: host The hostname or IP address of the server port The port the server is running on password The PASSword (if necessary) to log on with nick The NICKname to log on with group The server group this belongs to protocol The protocol to use, either "IRC" (the default) or "IRC-SSL" (for ssl server connections) If you want to omit a field, just leave it blank. About server refnums: Each entry in the server list contains the server's hostname, the server's port, the password (if any) the server requires for you to connect, and the nickname to use on the server. This set of information is called a "server specification" and each server specification is associated with a "server refnum" which is a small integer value starting with 0. When you see "server refnum" or "servref", that refers to the "server refnum" which is in the first column when you run the SERVER command with no options. About servers and windows: Windows and servers have a many-to-one relationship. Each window is always connected to exactly one server at a time; no more and no less. You can have as many windows connected to a server as you want. You can have as many servers open as you want. A server is automatically opened when the first window is connected to it. There is always one window connected to every open server; a server is automatically closed when the last window is disconnected from it. Description: The SERVER command manages EPIC's server list, letting you add, remove, connect, or disconnect servers as you need to. Options: [none] If you specify no options, SERVER will show you the current server list and the status of each server. The first field is the "server refnum". + Is an alias for window(4) server. - Disconnects you from that server; inferior in function to the DISCONNECT command, which you should use instead. -add Add the given server specification to the server list. -delete Delete the given server from the server list. You may not delete an open server. You may not delete the last server from the server list. + Connect to the "next" server (the next higher refnum, or if the current server is the highest refnum, then connect to server 0), and move all windows connected to this server over to the "next" server once the connection is complete. - Connect to the "previous" server (the previous higher refnum, or if the current server is refnum 0, then connect to the highest server refnum), and move all windows connected to this server over to the "previous" server once the connection is complete. Note: As the colon is already used by EPIC as an argument seperator, IPv6 adresses need to be surrounded in square brackets [] to prevent the colons from being interpeted. Examples: To change to a new server, irc.foobar.com, on port 6668: /server irc.foobar.com 6668 /server irc.foobar.com:6668 To change to a new server and register with the nickname "JoeBob": /server irc.foobar.com:::JoeBob To switch to the next, or previous, server in your list /server + /server - To associate a new server, irc.booya.net, to your current window: /server +irc.booya.net To delete server 5 from your list: /server -delete 5 To add server "irc.foo.com" on port 6667 with nick "blah" to your list: /server -add irc.foo.com:6667::blah To connect to an SSL server: /server irc.foobar.com:::::IRC-SSL See Also: disconnect(1); on(5) connect, disconnect; reconnect(1); window(4) server help/1_General/silence0100644000014400001440000000443407402426542014546 0ustar jnelsonusers# $EPIC: silence,v 1.4 2001/11/27 22:06:33 anders Exp $ Synopsis: silence [[+|-]] silence [] Description: SILENCE is a server extension available on undernet servers. Its purpose is similar to IGNORE, and acts as a complement, and not a replacement to IGNORE. When you SILENCE_ someone, every server on the network is told that you do not want to receive any messages from that person. Whenever that person tries to send you any more messages, his local server will drop the message directly at the source. This saves you the trouble of having to receive the message and process it with IGNORE, and it saves the network the resources of sending a message that you do not want. This technique can be very effective against flooders. If you do not provide an argument to SILENCE your current silence list will be shown. The argument of SILENCE may be a plus ('+') or a minus ('-') followed by a full nick!user@host pattern which is of the same composition as a ban (MODE +b), except that at least one '*' wildcard must be used. If the prefix is a plus, the pattern is added to your silence list. If the prefix is a minus, the pattern is removed from your silence list. The argument of SILENCE may be the nickname of another irc user. You will be shown that user's silence list. This can be useful in case you wanted to know if you or someone else are being silenced by that person. This command will only work on servers with the SILENCE extension (mostly undernet servers) and the number of entries in your SILENCE list is limited, usually to 5 entries. SILENCE is not a replacement for IGNORE since IGNORE offers finer-grained control and is not limited in size. Options: + add a pattern to your silence list - remove a pattern from your silence list Examples: To add someone to your silence list: /silence +*!*jerk@*.moron.org To remove someone from your silence list: /silence -*!*friend@*.bestbuds.com To see the silence list for FooBar: /silence foobar See Also: ignore(1); on(5) silence Restrictions: This command is limited to Undernet-based servers (i.e. it won't work on EFnet). help/1_General/topic0100644000014400001440000000366207326073522014245 0ustar jnelsonusers# $EPIC: topic,v 1.3 2001/05/07 15:48:41 jnelson Exp $ Synopsis: topic (to query topic in current channel) topic (to query topic in stated channel) topic - (to unset topic in current channel) topic - (to unset topic in stated channel) topic (to set topic in current channel) topic (to set topic in stated channel) Description: Each irc channel may have a "topic of discussion" which is displayed to new channel members when they join. The "topic" may be anything at all, it does not have to actually be the topic of discussion. The first two usage forms query the topic for a channel; generally you must be a member of a channel to query that channel's topic. The second two usage forms unset the topic for a channel; this is nothing more than setting the topic of a channel to the empty string. The channel "has no topic" after the topic is unset. The last two usage forms set the topic for a channel. The maximum length of channel topics is a server setting and as such, varies from server to server. A common limit is 80 characters. If a channel has mode +t set, you must be a channel operator to set or unset the channel topic. All channel members can query the topic of a channel at all times. Networks that support the TS (TimeStamp) protocol or TS-workalikes keep the nick!user@host of the person who set the topic, and the time that the topic was set. This is provided in a 333 server numeric. Examples: To set a new topic on your channel: /topic #blah Welcome to #blah, a very serious channel. or /topic Welcome to #blah, a very serious channel. To view the current topic for your channel: /topic #blah or /topic To unset the topic for your channel: /topic -#blah or /topic - See Also: mode(1); on(5) topic help/1_General/ctcp/0040755000014400001440000000000007752535773014147 5ustar jnelsonusershelp/1_General/ctcp/CVS/0040755000014400001440000000000007752535773014602 5ustar jnelsonusershelp/1_General/ctcp/CVS/Root0100644000014400001440000000002507215323637015426 0ustar jnelsonusers/home/cvs/repository help/1_General/ctcp/CVS/Repository0100644000014400001440000000002407215323637016661 0ustar jnelsonusershelp/1_General/ctcp help/1_General/ctcp/CVS/Entries0100644000014400001440000000060407752535773016133 0ustar jnelsonusers/action/1.4/Fri Jul 20 18:24:18 2001// /echo/1.3/Fri Jul 20 18:24:18 2001// /finger/1.3/Fri Jul 20 18:24:18 2001// /ping/1.4/Fri Jul 20 18:24:18 2001// /time/1.3/Fri Jul 20 18:24:18 2001// /userinfo/1.3/Fri Jul 20 18:24:18 2001// /version/1.4/Fri Jul 20 18:24:18 2001// /ctcp/1.4/Sun Dec 2 13:32:18 2001// /utc/1.4/Sun Dec 2 13:32:18 2001// /clientinfo/1.4/Thu Nov 6 21:24:11 2003// D help/1_General/ctcp/action0100644000014400001440000000060207326073522015324 0ustar jnelsonusers# $EPIC: action,v 1.4 2001/05/07 16:00:30 jnelson Exp $ Synopsis: ctcp [=]| action Description: This is the command that implements the functionality of the DESCRIBE and ME commands. This command should not be used directly. See Also: describe(1); load(5) action, mudlike; me(1); on(4) action, send_action help/1_General/ctcp/clientinfo0100644000014400001440000000153207752535773016222 0ustar jnelsonusers# $EPIC: clientinfo,v 1.4 2003/09/23 01:00:18 nsx Exp $ Synopsis: ctcp [=]| clientinfo [] Description: 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. Examples: To find out which CTCP requests john's client supports: /ctcp john clientinfo To get more information on CTCP VERSION from joebob: /ctcp joebob clientinfo version Other Notes: Not every supported CTCP command is meant to be used. Avoid direct use of CTCP DCC, CTCP ERRMSG, and CTCP SED. Not every client implements the CTCP CLIENTINFO request. help/1_General/ctcp/ctcp0100644000014400001440000000473307402426542015010 0ustar jnelsonusers# $EPIC: ctcp,v 1.4 2001/11/27 22:06:33 anders Exp $ Synopsis: ctcp [=]| [] Description: 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. You, the user, have complete control over EPIC's CTCP implementation. You may change how EPIC responds to CTCP requests, you may suppress certain CTCP requests from answering, and you can create new CTCP commands for others' use. To find out what CTCP commands that your version EPIC understands, run /CTCP CLIENTINFO The CTCP protocol is transport-neutral. What that means is that CTCP requests do not have to be sent across an irc server. EPIC currently can send and accept CTCP requests sent through the irc server, and through DCC CHAT connections. To send a CTCP request over a DCC CHAT connection, prefix the nickname with an equals-sign ('='). To end a CTCP request to your current channel, send the CTCP request to "star" ('*'). You cannot send CTCP requests in an ON that was generated by a message from an irc server (such as ON MSG, ON PUBLIC, or ON NOTICE), because the IRC protocol does not permit it. You can send CTCP requests in an ON that was generated by a DCC CHAT connection. Not all CTCP implementations are equal. Other clients will support mor or less requests than this client does. There is no way to guarantee that any CTCP request will succeed. Examples: To request the version of another client: /ctcp version nickname To ping a client that you have a DCC CHAT connection to: /ctcp =nickname ping To make a client echo back the the arguments you send it: /ctcp nickname echo send this back See Also: ctcp(1) clientinfo; on(5) ctcp, ctcp_reply; load(5) sound; set(4) no_ctcp_flood, verbose_ctcp Technical Note: When you begin an entropic conversation with the /CRYPT command, all messages sent to the target will be sent using CTCP SED requests. This client can add entropy to CTCP requests (many other clients cannot) and will do so transparently. Thus, some sensitive CTCP requests (such as CTCP DCC SEND) can be shrouded from snooping by the server if you use the /CRYPT command. help/1_General/ctcp/echo0100644000014400001440000000062307326073522014770 0ustar jnelsonusers# $EPIC: echo,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: ctcp [=]| echo [] Description: 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. help/1_General/ctcp/finger0100644000014400001440000000101507326073522015320 0ustar jnelsonusers# $EPIC: finger,v 1.3 2001/05/03 21:00:51 jnelson Exp $ Synopsis: ctcp [=]| finger Description: 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. See Also: load(5) finger help/1_General/ctcp/ping0100644000014400001440000000045107326073522015006 0ustar jnelsonusers# $EPIC: ping,v 1.4 2001/05/07 16:00:30 jnelson Exp $ Synopsis: ctcp [=]| ping Description: This command implements the underlying support for the PING command. It is not intended to be used directly. See Also: load(5) oldping; ping(1) help/1_General/ctcp/time0100644000014400001440000000054507326073522015013 0ustar jnelsonusers# $EPIC: time,v 1.3 2001/05/07 16:00:30 jnelson Exp $ Synopsis: ctcp [=]| time Description: 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. See Also: time(2); time(6) help/1_General/ctcp/userinfo0100644000014400001440000000056007326073522015704 0ustar jnelsonusers# $EPIC: userinfo,v 1.3 2001/05/07 16:00:30 jnelson Exp $ Synopsis: ctcp [=]| userinfo Description: 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. See Also: set(4) user_information help/1_General/ctcp/utc0100644000014400001440000000173207402426542014646 0ustar jnelsonusers# $EPIC: utc,v 1.4 2001/11/27 22:06:33 anders Exp $ Synopsis: ctcp [=]| utc