You need to sign in or sign up before continuing.
- 21 Aug, 2002 2 commits
-
-
Unknown User authored
-
Justin Mitchell authored
If a caps char is found, adds '1;' to string to select bold. if it wasnt it added '0;' which resets all the colour settings. This leads to inconsitant colour rendering.
-
- 07 Aug, 2002 2 commits
-
-
Finn Wilcox authored
Removed a couple of debugging functions I left in wrappers.c by mistake.
-
Finn Wilcox authored
which adds guard values before and after every malloc'ed block. The values are verified when the block is freed. These functions are in a separate file since technically they do not depend on any of the wrapper functions, though they do need some way to find the size of an existing block. The sentinels have not revealed any new errors so far. The next task is to test them with huge lines of text (and IPC data, etc) on the talker.
-
- 03 Aug, 2002 4 commits
-
-
Finn Wilcox authored
-
Chris Fry authored
Added useridle help to main trunk too Chris
-
Finn Wilcox authored
Note: this is a slight change to the numbering scheme. See my e-mail for more info.
-
Chris Fry authored
Same changes/fixes to the main trunk Chris
-
- 02 Aug, 2002 2 commits
-
-
Finn Wilcox authored
w_rl_filename_completion_function()
-
Chris Fry authored
Standardised a few of the log messages to make it easier to grep for stuff Chris
-
- 01 Aug, 2002 5 commits
-
-
Chris Fry authored
Updated - removed a couple of ideas that wouldnt work out, or are fixed Chris
-
Chris Fry authored
Fixed two more memory leaks Chris
-
Chris Fry authored
Added "w_rl_filename_completion_traced" or whatever its called to wrappers.h to stop a warning in script.c. Removed the "-exitinfo" flag, since if you are running wrappers, there is no sane reason you wouldnt ever want the exitinfo disabled - especially now finnw's hashtable code makes it *alot* faster. Chris
-
Finn Wilcox authored
Added a return to malloc_change(). The compiler apparently doesn't realise abort() never returns, so this silences a warning.
-
Finn Wilcox authored
speed, & made some of the support functions static.
-
- 31 Jul, 2002 6 commits
-
-
Chris Fry authored
Changed the description on "eq" slightly to give more accurate info Chris
-
Chris Fry authored
Fixed a grammical error ("user has just left talker" now ends "the talker"). Fixed zods so that the "user has just left the talker" message is suppressed if the victim is in quiet mode, so it now comes in line with all the other login/outs and mrod. Chris -
Chris Fry authored
Added new ideas Chris
-
Chris Fry authored
Fixed a possible issue in frl.c that sits noticed, and updated stringcmp with a fix of sits that caused a small memory problem. Removed the "credits" string from bb.h Chris
-
Chris Fry authored
Removed the credits file since it is now unnecessary again Chris
-
Justin Mitchell authored
They are supposed to be in the source code because a seperate file is far too easily lost, deleted, ommitted, changed, or generally fscked with.
-
- 30 Jul, 2002 3 commits
-
-
Denis Walker authored
Added new "L" flag to list\
-
Denis Walker authored
Changed credits to use file "credits" rather than hardcoded printf's
-
Denis Walker authored
Fix of moronic bug I introduced by not sticking "); at the end of the line
-
- 29 Jul, 2002 2 commits
-
-
Denis Walker authored
Added myself to the credits at finnw's suggestion
-
Chris Fry authored
Fixed a problem in IPC and RPC messages that stopped them from being received from the board. Added 'boardfunc' board initialisation functions as well as 'initfunc' ones that execute on first entrance to the talker, since scripts now work from the board. These can be used for any initialisation that is necessary before checkonoff messages get recieved. Most people will not use them but if you need to they are "boardfunc", and "lboardfunc" (visible and local respectively). Fixed a problem in MUDEXITS that stopped you getting any exits. Updated script functions to now have a 'flags' property rather than lots of seperate ones like 'hidden' and 'autoinit' etc.. Chris
-
- 28 Jul, 2002 14 commits
-
-
Chris Fry authored
Fixed a memory leak in the new checkonoff code Chris
-
Chris Fry authored
Oops. removed a debug message Chris
-
Denis Walker authored
Modified checkonoff help to reflect structure change ($6 added)
-
Chris Fry authored
Added reason codes to checkonoff broadasts, so mrod and zod reasons can be propagated through. Chris
-
Chris Fry authored
Removed the warnings from the wrappers Chris
-
Denis Walker authored
Added help for linewrap command
-
Finn Wilcox authored
readline v4.2, the version installed on silver (was written for 4.3).
-
Denis Walker authored
Fixed another typo introduced when fixing the last one... :-/
-
Denis Walker authored
Fixed a typo
-
Denis Walker authored
Reformatted to match the man-page style of help. Needs more work.
-
Finn Wilcox authored
- rl_completion_matches() ( replaces completion_matches() ) - rl_filename_completion_function() - rl_attempted_completion_function ( hook ) - rl_directory_rewrite_function ( hook ) This appears to fix the phantom memory leak in dupstr() Removed rl_malloc() & rl_free() Removed a lot of garbage collection code from hash.c, that was never used. Removed the numeric key types from hash.h, also never used. Added script file tab completion for .load Added duplicate tab completion entry for .sa Moved tab completion table to new file completion.c
-
Chris Fry authored
Updated 'todo' list. Chris
-
Chris Fry authored
First edition of the 'checkonoff' help. Dez, I dont suppose could neaten this could you? ;) Chris
-
Chris Fry authored
Changed the way scripts work slightly, so that they will quite happily run off the talker - although output from SAY etc.. are ignored, and WHEREAMI always returns "-1" - that sort of thing. --- Changed checkonoff's to use this ability, so you can receive checkonoff codes while on the board (ie, if you leave the talker, you will get your own checkonoff code). Normal scripts of course, still cant be run from the BBS, and IPC/RPC messages are currently ignored if off the talker. --- Radically, completely rewrote the entire checkonoff system to give more information, and a much more logical code system. Scripts executed using this method now recieve certain arguments: $0 = "CheckOnOff" $1 = <code> $2 = <method> $3 = <is_quiet> $4 = <sourceuser> $5 = <version> Where <code> can be one of: 0 - leave the talker 1 - enter the talker 2 - leave the board 3 - enter the board This keeps backwards compatibility the same - users can still detect each of these settings, although the extra features - such as detecting zods - will never occur using this code alone For each of the <code> values, <method> has several meanings: for leaving the board (2): 0 - normal (by user) 1 - timeout 2 - connection dropped M 3 - get mrodded S 4 - get banned S 5 - crash / error S 6 - deleted for leaving the talker (0): 0 - normal (by user) Z 1 - zodded S 2 - chatmode -c 3 - straight to shell (!quit etc...) for joining the board (3): 0 - normal (by user) 1 - straight to talker (-autochat) for joining the talker (1): 0 - normal (by user) U 1 - summoned S 2 - chatmode +c The extra letters in front of the <method> indicate certain privs are needed: M - needs mrod priv to detect S - needs SU to detect U - needs summon to detect Z - needs zod to detect So, for example, if a user were to log on using "-autochat", two messages would be created: <code=3> <method=1> <code=1> <method=0> These are the main two values that most people will use - along with "USER <variable" to get the user that caused the checkonoff message. Added to these two values, <is_quiet> simply returns: 0 - user logged on normally 1 - user logged on with -quiet to supress messages This allows script writers to only display their own messages if a user is logged on quietly if they so wish. <sourceuser> is more tricky. This is the person that caused the initiation of the checkonoff code in the first place. ie, for most messages, it is the same as the user the broadcast came from. However, in cases such as zod, mrod, or chatmode +/-c alteration, <sourceuser> will be the person that performed that operation. ie, SUPERUSER bans USER <code=0> <method=3> <code=2> <method=4> <user=USER> <sourceuser=SUPERUSER> and finally, <version> is mainly for being able to work out which version of checkonoff is used. this ranges from "1" to "3" currently, but if you wish, you can simply check if any of the arguments is left blank "" and work out what needs to be done from there. --- Added a "force_status" to incoming.c, and moved the 'ban' and 'delete' detection code to there instead of in the main loop - necessary for the new checkonoff information. --- Fixed a bug with 'ExecEvent2' where it only accepted up to 3 arguments --- Removed the now-obsolete "zodded" script Chris
-