1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
naim(1) AIM/ICQ/IRC/Lily Communication Client naim(1)
NAME
naim - console mode chat client
SYNOPSIS
naim
nicq
nirc [nickname [server]]
nlily
DESCRIPTION
naim is the original ncurses AIM client. It uses the TOC
protocol, and features many commonly-requested features
found nowhere else, while still providing an intuitive
chat interface.
OPTIONS
If a `.naimrc' file exists in your home directory, naim
executes that and ignores all command line options. Other-
wise...
When invoked as `naim', naim will create a connection of
type AIM/TOC and will display some helpful information to
the screen (but won't actually try to sign you on).
When invoked as `nicq', naim will create a connection of
type ICQ/TOC and will display some helpful information to
the screen (but won't actually try to sign you on).
When invoked as `nirc', naim will create a connection of
type IRC and will attempt to sign you on using the nick-
name and server, if provided.
When invoked as `nlily', naim will create a connection of
type Lily/SLCP and will display some helpful information
to the screen (but won't actually try to sign you on).
ADDITIONAL CONNECTIONS
Once you have naim started, you can easily create addi-
tional connections by using the /newconn command. For
example, to visit me on the EFnet IRC network, you might
type:
/newconn EFnet IRC
/connect naimuser irc.servercentral.net
/join #naim
(note that if you start naim as `nirc' it will run the
previous commands automatically)
If you wanted to sign on to AIM more than once, you might
type:
/newconn AIM2 AIM
/connect othername
If you start naim as `naim' it will issue `/newconn AIM
TOC' automatically. If you start naim as `nicq' it will
issue `/newconn ICQ TOC' automatically. If you start naim
as `nlily' it will issue `/newconn Lily SLCP' automati-
cally. The first argument to /newconn is the connection
"name", which can be anything you dream up (it might make
sense to use your screen name if you are going to be con-
necting to the same service more than once), and the
second argument is the connection type. AIM and ICQ both
use the same connection type (TOC).
By default, the Ins and Del keys will switch between con-
nections. See `/help keys' for additional information,
including how to change your key bindings.
SETTINGS
Once you have setup naim the way you like it (see `/help
settings' and `/help keys'), use the `/save' command to
have naim create a .naimrc file in your home directory.
From then on, naim will always start up configured the way
it is currently configured, including all of your current
settings (/set), key bindings (/bind), and open connec-
tions (/newconn). Feel free to load the generated .naimrc
file in a text editor for further tweaking.
ONLINE HELP
Online help is available by typing /help at the console.
EXITING
Use the /quit command.
AUTHOR
Daniel Reed <n@ml.org>.
UPDATES
The latest version of naim will always be available from
http://naim.n.ml.org/ . If you ever use naim, you are
strongly encouraged to subscribe to the naim-announce
mailing list. This is a low-volume mailing list used
exclusively to announce new releases of naim or changes in
the AIM service that affects naim users. To subscribe,
simply send a blank email to <naim-announce-sub-
scribe@n.ml.org> and reply to the confirmation message you
will receive.
BUG REPORTS
Before reporting any bugs, please review Simon Tatham (of
PuTTY)'s wonderful essay, How to Report Bugs Effectively
at http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
To report issues with the front end (things having to do
with buddy windows, colors, .naimrc, and anything else
"user oriented") contact the naim maintainer, Daniel Reed
<n@ml.org>.
To report issues with the protocol library (problems con-
necting, error messages while connected, and anything else
not a part of the front end) contact the FireTalk main-
tainer, now also Daniel Reed <n@ml.org>.
To report issues with the FreeBSD port, contact Ryan T.
Dean <rtdean@cytherianage.net>.
FEATURE REQUESTS
If you would like to suggest new features or significant
behavior changes, subscribe to the naim-users mailing list
and suggest it there. I get a lot of mail every day, and
non-bug reports get a fairly low priority. The best way to
make sure something you want is implemented is to post it
to naim-users whenever I ask for them on the list. To sub-
scribe, send a blank email to <naim-users-sub-
scribe@n.ml.org> and reply to the confirmation message you
will receive.
PATCHES
If you would like to participate to naim's development in
a more active role, feel free to submit patches either to
myself or to the naim-users mailing list. Patches in con-
text output format are prefered. In order to work on naim,
you may wish to extract naim twice, and perform your
builds in a third directory, as in:
tar -zxvf naim-0.11.6.tar.gz
mv naim-0.11.6 naim-0.11.6,original
tar -zxvf naim-0.11.6.tar.gz
mkdir naim-0.11.6-objdir
cd naim-0.11.6-objdir
../naim-0.11.6/configure --prefix=/usr
Then you may modify the files in ../naim-0.11.6, compile,
test, modify again, recompile, test, etc. until your are
satisfied, then:
cd ..
diff -rcN naim-0.11.6,original naim-0.11.6 > \
naim-0.11.6.feature1.patch
And submit `naim-0.11.6.feature1.patch'. Do not gzip or
otherwise encode patches, so they may be reviewed from
within a mail client.
naim-0.11.6 2003-06-24 naim(1)
|
