Initial import of the ircii-pana-1.1-final source tree.
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:
33
bitchx-docs/1_General/ping
Normal file
33
bitchx-docs/1_General/ping
Normal file
@@ -0,0 +1,33 @@
|
||||
Synopsis:
|
||||
ping <nickname|channel>
|
||||
|
||||
Description:
|
||||
PING is used to determine (roughly) how long messages from your side of
|
||||
the network to the recipient's take to arrive. In a sense, it allows
|
||||
you to measure how fast or slow the network is relative to you. The
|
||||
accuracy of the ping can be changed with /set ping_type.
|
||||
0 just in seconds.
|
||||
1 in seconds and millisecs.
|
||||
2 use echo instead of ping
|
||||
|
||||
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
|
||||
|
||||
Aliases:
|
||||
This command is identical to CTCP PING.
|
||||
|
||||
See Also:
|
||||
ctcp(1) uping
|
||||
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user