philippelh/bitchx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial import of the ircii-pana-1.1-final source tree.

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/bitchx/code/tags/ircii-pana-1.1-final@1 13b04d17-f746-0410-82c6-800466cd88b0
This commit is contained in:
Kevin Easton
2008-02-25 09:25:32 +00:00
commit 28febcfea9
1429 changed files with 250653 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
bitchx-docs/1_General/dcc/activecount Normal file
View File

@@ -0,0 +1,9 @@
Synopsis:
dcc activecount
Description:
DCC ACTIVECOUNT displays the number of active dcc's and the number of
possible dcc sends allowed. The number allowed can be changed using /set
DCC_SEND_LIMIT

6
bitchx-docs/1_General/dcc/autoget Normal file
View File

@@ -0,0 +1,6 @@
Synopsis:
dcc autoget
Description:
DCC AUTOGET toggles on/off the automatic receive of dcc files.

7
bitchx-docs/1_General/dcc/autooverwrite Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
dcc autooverwrite
Description:
DCC AUTOOVERWRITE toggles on/off the dcc auto-overwrite of files that
exist and autoget is on.

7
bitchx-docs/1_General/dcc/autorename Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
dcc autorename
Description:
DCC AUTORENAME toggles on/off the dcc autorename of files that exist and
autoget is on.

6
bitchx-docs/1_General/dcc/autoresume Normal file
View File

@@ -0,0 +1,6 @@
BSynopsis:B
_dcc_ autoresume
BDescription:B
DCC AUTORESUME toggles on/off the dcc autoresume of files that exist and
autoget is on.

13
bitchx-docs/1_General/dcc/bot Normal file
View File

@@ -0,0 +1,13 @@
Synopsis:
dcc bot <nick>
Description:
DCC BOT initiates a direct connection to another client, allowing
the users to chat without needing to pass messages through the irc
network. This is a very secure way of communicating on irc, not
to mention that it is generally faster than sending messages across
the irc network. A BOT connection is differant from a CHAT connection.
See Also:
ctcp(1); msg(1); on(5) dcc_chat, send_dcc_chat

20
bitchx-docs/1_General/dcc/chat Normal file
View File

@@ -0,0 +1,20 @@
Synopsis:
dcc chat <nick>
Description:
DCC CHAT initiates a direct connection to another client, allowing
the users to chat without needing to pass messages through the irc
network. This is a very secure way of communicating on irc, not
to mention that it is generally faster than sending messages across
the irc network.
To send a message across the DCC CHAT connection, use MSG as you
normally would, but prefix the nickname with a "=". Additionally,
CTCP commands can be sent across a DCC CHAT connection (allowing you
to initiate a DCC SEND, for instance), if the remote client is also an
EPIC3 (or compatible) client. See the appropriate help files for more
information.
See Also:
ctcp(1); msg(1); on(5) dcc_chat, send_dcc_chat

35
bitchx-docs/1_General/dcc/close Normal file
View File

@@ -0,0 +1,35 @@
Synopsis:
dcc close <type> <nick> [<arguments>]
Description:
DCC CLOSE closes an unwanted DCC connection, or cancels a pending one.
The type, nickname, and parameters required are the same as those
shown in DCC LIST output. If no arguments are specified, the oldest
DCC record for the given type and nick is closed.
When DCC CLOSE is used on a pending incoming connection (one that has
not yet been established), it is treated as a rejected connection, and
a message to that effect is send back to the remote client. Note that
for an incoming SEND, the client actually records it as a GET, since
from a local perspective, the client will be getting something from
the remote client.
DCC CLOSE can also accept the flag '-all' or an asterisk, '*', as either
the type or the nickname. This will work as a wildcard, closing all DCC's
from that type or nickname.
Examples:
To close an existing DCC CHAT connection with joebob:
/dcc close chat joebob
To reject an incoming DCC SEND connection from joebob:
/dcc close get joebob
To close all DCC CHAT connections:
/dcc close chat *
or
/dcc close chat -all
See Also:
dcc(1) closeall, list, rename; on(5) dcc_lost

10
bitchx-docs/1_General/dcc/closeall Normal file
View File

@@ -0,0 +1,10 @@
Synopsis:
dcc closeall
Description:
This command closes every open DCC connection and clears your list of every
entry.
See Also:
dcc(1) close, list, rename; on(5) dcc_lost

28
bitchx-docs/1_General/dcc/dcc Normal file
View File

@@ -0,0 +1,28 @@
Synopsis:
dcc [<command> [<arguments>]]
Description:
DCC stands for direct client-to-client. The DCC command handles all
such connections. There are two primary uses for DCC; bypassing the
irc network for chatting, and file transfers. However, this is not
the limit of DCC's capabilities.
DCC connections are established with CTCP handshakes. All this really
means is that connection request, connection, and rejection messages
are sent in CTCP format. This is noteworthy, as other commands that
operate based on message type will lump DCC messages in with CTCPs
(including IGNORE and the client's internal logging mechanisms).
Aliases:
Using DCC with no arguments is the same as DCC LIST.
See Also:
ctcp(1); on(5) dcc_connect, dcc_lost, dcc_request
Restrictions:
It is worth noting that users behind firewalls may have some problems
using DCC. Depending on the nature of the firewall, such users will
probably be unable to initiate a DCC SEND. Others may find that they
cannot use DCC at all. This is not a bug in ircII-EPIC, it is due
simply to matters beyond the control of the client program.

19
bitchx-docs/1_General/dcc/exempt Normal file
View File

@@ -0,0 +1,19 @@
Synopsis:
dcc exempt [+nickname] [nickname1]
Description:
DCC EXEMPT bypasses /set dcc_autoget and allows the nick to send a
file even when autoget is off.
Example
To add a nick to your exempt list:
/dcc exempt +joe
To remove a nick from your exempt list:
/dcc exempt joe
To display your exempt list:
/dcc exempt

15
bitchx-docs/1_General/dcc/ftp Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
dcc ftp hostname user password [-p port] [-b blocksize]
Description:
DCC FTP initiates a ftp connection to a host.
To send a message across the DCC FTP connection, use MSG as you
normally would, but prefix the hostname with a "-". If you have a ncftp
bookmarks file in 2.x format, you can use shortcuts from that file for
the hostname. If no user and password is specifed defaults are supplied
for a anonymous connection.
See Also:
ctcp(1); ftp(1); msg(1); on(5) dcc_chat, send_dcc_chat

24
bitchx-docs/1_General/dcc/get Normal file
View File

@@ -0,0 +1,24 @@
Synopsis:
dcc get [=]<nick> [<file>]
Description:
DCC GET initiates a file transfer with a remote client that has offered
the client a DCC SEND. Naturally, a remote client must have already
send the client a DCC SEND request in order for the client to start a
DCC GET with it. If the DCC request comes over an existing DCC CHAT
connection, a '=' must be prepended to the nickname.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest SEND request
is processed first.
Examples:
To accept a SEND from joebob:
/dcc get joebob
To accept all files offered to you by DCCbot:
/dcc get DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_store_path

26
bitchx-docs/1_General/dcc/list Normal file
View File

@@ -0,0 +1,26 @@
Synopsis:
dcc list
Description:
This displays all current and pending DCC connections in a table format.
The data listed includes the type of DCC connection, the remote client
nickname, status (whether it has actually started or not), when the
connection began (if at all), how much data has been transferred over
the link, and any extra arguments present (such as the name of a file
being transferred between clients). Two differant types of display may
be chosen for displaying the information displayed.
Examples:
To show a list of current DCC connections:
/dcc list
Aliases:
DCC LIST operates the same as DCC with no arguments.
See Also:
dcc(1) close; set(4) dcc_bar_type; on(5) dcc_list
Other Notes:
For file transfers, LIST will show the filename being transferred.
Display of the full path can be toggled with DCC SHOWPATHS.

6
bitchx-docs/1_General/dcc/quietmode Normal file
View File

@@ -0,0 +1,6 @@
Synopsis:
dcc quietmode
Description:
DCC QUIETMODE toggles on/off display of dcc output.

27
bitchx-docs/1_General/dcc/raw Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc raw <fd> <host> <message>
Description:
DCC RAW is a raw socket interface for ircII-EPIC. It allows the client
to control arbitrary TCP connections with a remote host on any port
desired.
The actual connection is established with the $connect() function. It
makes the connection and returns a file descriptor that is used by DCC
RAW to control the connection. The file descriptor will always be a
number (generally a small one). Incoming data from the remote host may
be hooked with ON DCC_RAW.
Examples:
To send a message to blah.foo.com over an existing raw DCC connection:
/dcc raw 6 blah.foo.com This is a sample message
See Also:
connect(6); listen(6); on(5) dcc_raw
Other Notes:
The applications for DCC RAW are endless. Since it allows the client
connect to any arbitrary host on any arbitrary port, a little creative
use of the scripting language can turn ircII-EPIC into a client for
most any remote service.

27
bitchx-docs/1_General/dcc/reget Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc reget [=]<nick> [<file>]
Description:
DCC REGET initiates a file transfer with a remote client that has
offered the client a DCC RESEND. Naturally, a remote client must have
already send the client a DCC RESEND request in order for the client to
start a DCC REGET with it. If the DCC request comes over an existing
DCC CHAT connection, a '=' must be prepended to the nickname.
This command resumes the file if it exists. It is not compatible with
mIRC.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest RESEND request
is processed first.
Examples:
To accept a RESEND from joebob:
/dcc reget joebob
To accept all files offered to you by DCCbot:
/dcc reget DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_dldir

25
bitchx-docs/1_General/dcc/rename Normal file
View File

@@ -0,0 +1,25 @@
Synopsis:
dccrename [<nick>] <name> [<new name>]
dccrename -chat <nick> <new nick>
Description:
This renames an incoming file from a DCC GET connection, or optionally
a nick in a DCC CHAT. For files, this is useful if one with the same name
already exists, so that it doesn't get overwritten. If the new name isn't
specified, it is assumed the name given is the new name, and it is applied
to the oldest existing DCC GET connection.
Options:
-chat rename a nick in DCC CHAT instead of a file
Examples:
To rename file foo to bar from joebob:
/dcc rename joebob foo bar
To rename joebob to jimbob in a DCC CHAT:
/dcc rename -chat joebob jimbob
See Also:
dcc(1) get, list; set(4) dcc_store_path

27
bitchx-docs/1_General/dcc/resend Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc resend [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC RESEND offers files to a remote client over DCC. The remote
client must of course acknowledge with a DCC REGET in order to begin the
file transfer.
If a DCC CHAT with the remote client already exists, the RESEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc resend joebob somefile
See Also:
dcc(1) get; set(4) dcc_block_size

30
bitchx-docs/1_General/dcc/resume Normal file
View File

@@ -0,0 +1,30 @@
Synopsis:
dcc resume [=]<nick> <file>
Description:
In the event that a DCC file transfer is interrupted, DCC RESUME can be
used to continue it where the original transfer stopped. This is
generally most useful to users with very slow connections to the
Internet transferring large files.
Examples:
To restart a transfer with joebob:
/dcc resume joebob somebigfile
See Also:
dcc(1) close, get, send
Restrictions:
This command is only available if the client was compiled with the
BROKEN_MIRC_DCC_RESUME #define enabled (in the config.h). The client
compile options string (returned when $info(o) is evaluated) will have
an 'i' in it if this option is enabled.
Other Notes:
It is very important that the user realize that use of this feature is
a blatant violation of the irc protocol (described in rfc 1459), in that
it makes the client respond to a remote PRIVMSG with another PRIVMSG.
While this may not mean much to the average user, it is nonetheless not
"the right way" to do things, and irc operators have been known to KILL
clients that violate the protocol in this manner.

27
bitchx-docs/1_General/dcc/send Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc send [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC SEND offers files to a remote client over DCC. The remote client
must of course acknowledge with a DCC GET in order to begin the file
transfer.
If a DCC CHAT with the remote client already exists, the SEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc send joebob somefile
See Also:
dcc(1) get; set(4) dcc_sliding_window

7
bitchx-docs/1_General/dcc/showpaths Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
dcc showpaths
Description:
DCC SHOWPATHS toggles on/off the display of pathnames when /dcc LIST is
used.

8
bitchx-docs/1_General/dcc/stats Normal file
View File

@@ -0,0 +1,8 @@
Synopsis:
dcc stats
Description:
DCC STATS displays various information that has been collected during
the clients running time on all dcc sends and gets

26
bitchx-docs/1_General/dcc/tget Normal file
View File

@@ -0,0 +1,26 @@
Synopsis:
dcc tget [=]<nick> [<file>]
Description:
DCC TGET initiates a file transfer with a remote client that has
offered the client a DCC TSEND. Naturally, a remote client must have
already send the client a DCC TSEND request in order for the client to
start a DCC TGET with it. If the DCC request comes over an existing
DCC CHAT connection, a '=' must be prepended to the nickname.
This method is slightly faster than a normal dcc get.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest TSEND request
is processed first.
Examples:
To accept a TSEND from joebob:
/dcc tget joebob
To accept all files offered to you by DCCbot:
/dcc tget DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_dldir

29
bitchx-docs/1_General/dcc/treget Normal file
View File

@@ -0,0 +1,29 @@
Synopsis:
dcc treget [=]<nick> [<file>]
Description:
DCC TREGET initiates a file transfer with a remote client that has
offered the client a DCC TRESEND. Naturally, a remote client must have
already send the client a DCC TRESEND request in order for the client to
start a DCC TREGET with it. If the DCC request comes over an existing
DCC CHAT connection, a '=' must be prepended to the nickname.
This command resumes the file if it exists. It is not compatible with
mIRC.
This method is slightly faster than a normal dcc get.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest TRESEND request
is processed first.
Examples:
To accept a TRESEND from joebob:
/dcc treget joebob
To accept all files offered to you by DCCbot:
/dcc treget DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_dldir

27
bitchx-docs/1_General/dcc/tresend Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc send [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC SEND offers files to a remote client over DCC. The remote client
must of course acknowledge with a DCC GET in order to begin the file
transfer.
If a DCC CHAT with the remote client already exists, the SEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc send joebob somefile
See Also:
dcc(1) get; set(4) dcc_block_size

27
bitchx-docs/1_General/dcc/tsend Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc tsend [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC TSEND offers files to a remote client over DCC. The remote client
must of course acknowledge with a DCC TGET in order to begin the file
transfer.
If a DCC CHAT with the remote client already exists, the TSEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc tsend joebob somefile
See Also:
dcc(1) get; set(4) dcc_block_size