forked from tlily/tigerlily
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
210 lines (158 loc) · 7.4 KB
/
README
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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
# TigerLily: A client for the lily CMC, written in Perl.
# Copyright (C) 1999-2011 The TigerLily Team, <tigerlily@tlily.org>
# http://www.tlily.org/tigerlily/
#
# This program is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License version 2, as published
# by the Free Software Foundation; see the included file COPYING.
("`-/")_.-'"``-._
. . `; -._ )-;-,_`) TigerLily 2.x
(v_,)' _ )`-. ``-' "Feel Free"
_.- _..-_/ / ((.'
((,.-' ((,/
===============================================================================
Installing
----------
TigerLily requires Perl 5.6.1 or greater. You will also need
Curses.pm or Term::Readline::Gnu. (from CPAN)
You can run tlily directly from the source directory, by running
"perl tlily.PL".
To create an assortment of single file versions of tlily, run:
perl Makefile.PL
make
Pick the .plx you want to use (depends on the UI you wish to use, it's part
of the file name), and copy it wherever you wish.
To do a standard installation:
perl Makefile.PL
make
make install
And "tlily" will be installed in the directory you specify during the first
step.
Colors
------
Color preferences are specified in the config files(See 'Configuration'
below). To change a color, set that color preference in your site or
user configuration files. Color preferences are in %color_attrs, and
monochrome preferences are in %mono_attrs.
Example: To make the header on private messages red on white instead of
green on black, add the following to your config file:
%color_attrs = ('public_header' => [qw(red white normal)]);
/-command Overrides
-------------------
Tigerlily includes several client-side fixes/enhancements for existing lily
commmands, implemented by intercepting the command before it is sent
to the server:
/info Enhanced so that /info set and /info edit bring up your
editor for you to change your info.
/memo Enhanced so that /memo set and /memo edit bring up your
editor for you to change your memos.
/blurb Enhanced so that /blurb will squeeze your requested blurb
into the space available.
/oops Fixed so as to reset your sendlist correctly for ;-expansion
/also Fixed so as to append the /also'ed people to your sendlist
for ;-expansion.
To allow any of these overrides, put the command without the / in the
@slash variable in your site or user configuration files.
Example: To enable the /info override, add the following to your
user or site config files:
@slash = ('info');
To disallow an override, put the command without the / and with a leading
'-' in the @slash variable in your site or user configuration files.
Example: To disable the /also override, add the following to your
user or site config files:
@slash = ('-also');
Being concious not to override the existing behavior of lily commands, the
current default is to not override any /-commands.
There are those among the developers that want to change this default,
though, and so this default may change.
Configuration (Needs expanding)
-------------
TigerLily now has 4 levels of customization:
Level Default File Location
Description
----- ---------------------
Global /usr/local/lib/tlily/tlily.cf
Default settings for all features; please no not edit except
when developing to add defaults for new settings.
Site /usr/local/etc/tlily.cf
Site-specific settings to augment or override the global
settings. System Administrators wishing to change the
default settings for their users should edit this file.
User ~/.lily/tlily/tlily.cf
User-specific settings to override the global and site
settings.
Command <no file>
Many(not all) configuration options can be overridden at the
command line.
The format for these .cf files is
[$@%]<config_var> = <value> ;
So, to set your browser to lynx, you'd add the following lines to
~/.lily/tlily/tlily.cf:
$browser=lynx;
$browser_textmode=1;
Note that in an interactive session, this would be accomplished with:
%set browser lynx
Here is a summary of some common configuration file (CF) options:
@load
Setting this variable in a CF will change the list of
extensions to load. An extension preceeded by a - will
cause that extension to not be loaded.
# Example:
@load = ('a', 'b', '-c', 'd', '-e');
# In addition to the current extension list, extensions a, b,
# and d will be loaded, and extensions c and e will not be loaded.
The default extension list is in the global CF, and can be
changed using this method in the site and/or user CFs.
%color_attrs
%mono_attrs
Setting elements of these hashes in a cf will change the color
settings for the color and monochrome mode of an element.
@slash
Setting this variable will change the list of /-commands that are
allowed to be intercepted by tlily and other extensions in order
to add functionality to an existing command. Any extension wanting
to intercept a /-command must honor their desired command's
existence/non-existence in this list. Adding a /-command to this
list will not necessarily enable interception of the /-command;
the extension that wants to intercept it must be loaded also.
# Example:
@slash = ('-info', 'also', 'oops');
# In addition to the slash list from previous CF levels,
# allow /also and /oops to be intercepted, but do not
# allow /info to be overridden.
By default, no slash commands will be allowed to be intercepted. This
can be overridden in the site and/or user CFs using this method.
$emote_oops
If set, this specifies an oops string to use for emote discussions.
The standard lily /oops will still be used for connect discs. Note
that this only effects %oops -- you will need to add oops to @slash
to change /oops.
@prefer
This variable contains a list of destinations to "prefer" when
doing autoexpansion. If a partial destination is a prefix to
an element in this list, it will always be expanded to it.
Examples:
@prefer = ('-security');
The "security" discussion exists, as does the user "Secret Agent".
"sec" will expand to "-security".
@prefer = ('damien_clone');
The users "damien" and "damien clone" both exist.
"dam" will expand to "damien_clone". "damien" exactly matches
a user, and will not expand.
%bindings
Set %bindings to install global key bindings. For example:
%bindings = { 'M-g' => 'look' };
or
$bindings{'M-g'} = 'look';
will both set the M-g key to do the "look" function, which
provides a simple lookup mechanism to the Unix "words" file.
(Note that the look function is bound to C-g by default, and
%bindings does not change that.) Bindings set this way will
be available before you are even connected to the server,
which can't be accomplished by using %bind in a Startup file/memo.
Extensions can each have options to configure them; see the documentation
for the specific module to see what options can be set.
git access
-----------------
The TigerLily sources are stored on github, at https://github.com/coke/tigerlily
For more information on git and github, see: http://help.github.com/.