II(1) General Commands Manual II(1)

ii - irc it or irc improved

ii is a minimalistic FIFO and filesystem based IRC client. It creates an irc directory tree with server, channel and nick name directories. In every directory a FIFO file (in) and normal file (out) is placed. This will be for example ~/irc/irc.freenode.net/. The in file is used to communicate with the servers and the out files includes the server messages. For every channel and every nick name there will be new in and out files. The basic idea of this is to be able to communicate with an IRC server with basic command line tools. For example if you will join a channel just do echo "/j #channel" > in and ii creates a new channel directory with in and out file.

ii <-s servername> [-p port] [-k environment variable] [-i prefix] [-n nickname] [-f realname] <-u sockname>

server to connect to, for example: irc.freenode.net
connect to a UNIX domain socket instead of directly to a server.
lets you override the default port (6667)
lets you specify an environment variable that contains your IRC password, e.g. IIPASS="foobar" ii -k IIPASS. This is done in order to prevent other users from eavesdropping the server password via the process list.
lets you override the default irc path (~/irc)
lets you override the default nick ($USER)
lets you specify your real name associated with your nick

~/irc
In this directory the irc tree will be created. In this directory you will find a directory for your server (default: irc.freenode.net) in which the FIFO and the output file will be stored. If you join a channel a new directory with the name of the channel will be created in the ~/irc/$servername/ directory.

/a [<message>]
mark yourself as away
/j #channel/nickname [<message>]
join a channel or open private conversation with user
/l [reason]
leave a channel or query
/n nick
change the nick name
/q [reason]
quit ii
/t topic
set the topic of a channel

Everything which is not a command will be posted into the channel or to the server. So if you need /who just write /WHO as described in RFC#1459 to the server in FIFO.

For TLS/SSL protocol support you can connect to a local tunnel, for example with stunnel or socat.

Subscribe to the mailinglist and write to dev (at) suckless (dot) org for suggestions, fixes, etc.

ii engineers, see LICENSE file

echo(1), tail(1)

Please report them!

ii-1.8