1naim(1) AIM/ICQ/IRC/Lily Communication Client naim(1)
2
6 naim - console mode chat client
7
9 naim
10 nicq
11 nirc [nickname [server]]
12 nlily
13
15 naim is the original ncurses AIM client. It uses the TOC protocol, and
16 features many commonly-requested features found nowhere else, while
17 still providing an intuitive chat interface.
18
20 If a `.naimrc' file exists in your home directory, naim executes that
21 and ignores all command line options. Otherwise...
22 When invoked as `naim', naim will create a connection of type AIM/TOC
24 and will display some helpful information to the screen (but won't
25 actually try to sign you on).
26 When invoked as `nicq', naim will create a connection of type ICQ/TOC
28 and will display some helpful information to the screen (but won't
29 actually try to sign you on).
30 When invoked as `nirc', naim will create a connection of type IRC and
32 will attempt to sign you on using the nickname and server, if provided.
33 When invoked as `nlily', naim will create a connection of type
35 Lily/SLCP and will display some helpful information to the screen (but
36 won't actually try to sign you on).
37
39 Once you have naim started, you can easily create additional connec‐
40 tions by using the /newconn command. For example, to visit me on the
41 EFnet IRC network, you might type:
42 /newconn EFnet IRC
43 /connect naimuser irc.servercentral.net
44 /join #naim
45 (note that if you start naim as `nirc' it will run the previous com‐
46 mands automatically)
47 If you wanted to sign on to AIM more than once, you might type:
49 /newconn AIM2 AIM
50 /connect othername
51 If you start naim as `naim' it will issue `/newconn AIM TOC' automati‐
53 cally. If you start naim as `nicq' it will issue `/newconn ICQ TOC'
54 automatically. If you start naim as `nlily' it will issue `/newconn
55 Lily SLCP' automatically. The first argument to /newconn is the con‐
56 nection "name", which can be anything you dream up (it might make sense
57 to use your screen name if you are going to be connecting to the same
58 service more than once), and the second argument is the connection
59 type. AIM and ICQ both use the same connection type (TOC).
60 By default, the Ins and Del keys will switch between connections. See
62 `/help keys' for additional information, including how to change your
63 key bindings.
64
66 Once you have setup naim the way you like it (see `/help settings' and
67 `/help keys'), use the `/save' command to have naim create a .naimrc
68 file in your home directory. From then on, naim will always start up
69 configured the way it is currently configured, including all of your
70 current settings (/set), key bindings (/bind), and open connections
71 (/newconn). Feel free to load the generated .naimrc file in a text edi‐
72 tor for further tweaking.
73
75 Online help is available by typing /help at the console.
76
78 Use the /quit command.
79
81 Daniel Reed <n@ml.org>, with notable contributions from Ian Gulliver
82 <ian@penguinhosting.net> and Joshua Wise <joshua@joshuawise.com>.
83
85 The latest version of naim will always be available from
86 http://naim.n.ml.org/ . If you ever use naim, you are strongly encour‐
87 aged to subscribe to the naim-announce mailing list. This is a low-vol‐
88 ume mailing list used exclusively to announce new releases of naim or
89 changes in the AIM service that affects naim users. To subscribe, sim‐
90 ply send a blank email to <naim-announce-subscribe@n.ml.org> and reply
91 to the confirmation message you will receive.
92
94 Before reporting any bugs, please review Simon Tatham (of PuTTY)'s won‐
95 derful essay, How to Report Bugs Effectively at http://www.chiark.gree‐
96 nend.org.uk/~sgtatham/bugs.html.
97 To report issues with the front end (things having to do with buddy
99 windows, colors, .naimrc, and anything else "user oriented") contact
100 the naim maintainer, Daniel Reed <n@ml.org>.
101 To report issues with the protocol library (problems connecting, error
103 messages while connected, and anything else not a part of the front
104 end) contact the FireTalk maintainer, now also Daniel Reed <n@ml.org>.
105 To report issues with the FreeBSD port, contact Ryan T. Dean
107 <rtdean@cytherianage.net>.
108
110 If you would like to suggest new features or significant behavior
111 changes, subscribe to the naim-users mailing list and suggest it there.
112 I get a lot of mail every day, and non-bug reports get a fairly low
113 priority. The best way to make sure something you want is implemented
114 is to post it to naim-users whenever I ask for them on the list. To
115 subscribe, send a blank email to <naim-users-subscribe@n.ml.org> and
116 reply to the confirmation message you will receive.
117
119 If you would like to participate to naim's development in a more active
120 role, feel free to submit patches either to myself or to the naim-users
121 mailing list. Patches in context output format are prefered. In order
122 to work on naim, you may wish to extract naim twice, and perform your
123 builds in a third directory, as in:
124 tar -jxvf naim-0.11.8.tar.bz2
125 mv naim-0.11.8 naim-0.11.8,original
126 tar -jxvf naim-0.11.8.tar.bz2
127 mkdir naim-0.11.8-objdir
128 cd naim-0.11.8-objdir
129 ../naim-0.11.8/configure --prefix=/usr
130 Then you may modify the files in ../naim-0.11.8, compile, test, modify
132 again, recompile, test, etc. until your are satisfied, then:
133 cd ..
134 diff -rcN naim-0.11.8,original naim-0.11.8 > \
135 naim-0.11.8.feature1.patch
136 And submit `naim-0.11.8.feature1.patch'. Do not gzip or otherwise
138 encode patches, so they may be reviewed from within a mail client.
139naim-0.11.8 2005-10-26 naim(1)