-
I don't remember if the advanced database comes with a 'macros' file, but if not or showhelp isn't in it, just add this to the macros file:
showhelp
prog "_help" array_get_proplist me @ 1 array_make array_notify
1.
2009-11-09 01:57:57 UTC by horizord
-
I have installed the advance db but 'say' and 'pose' only return: Program not compilable. Cannot run.
I tried to compile cmd-say but it says: Error in line 139: Unrecognized word .showhelp.
And compiling cmd-pose but is says: Error in line 84: Unrecognized word .showhelp.
How do I fix these?.
2009-10-23 02:42:19 UTC by patrickchapman
-
points committed patchset 1038 of module fbmuck to the Fuzzball MUCK CVS repository, changing 1 files.
2009-10-11 06:01:38 UTC by points
-
points committed patchset 1037 of module fbmuck to the Fuzzball MUCK CVS repository, changing 3 files.
2009-10-11 05:30:43 UTC by points
-
points committed patchset 1036 of module fbmuck to the Fuzzball MUCK CVS repository, changing 11 files.
2009-10-11 05:19:18 UTC by points
-
winged committed patchset 1035 of module fbmuck to the Fuzzball MUCK CVS repository, changing 10 files.
2009-10-09 23:54:24 UTC by winged
-
Not all fopen calls have the binary flag. In particular, tune.c, interface.c, sanity.c, help.c, game.c, crt_malloc.c, and db.c all use non-binary fopen flags.
I'm more worried about the snprintf()s and fwrite()s of those buffers; if anything internally includes \r\n, we've got a problem. (I'm also a bit worried about the effect of embedded newlines in properties, if that's not been...
2009-10-09 22:27:16 UTC by winged
-
Believe it or not, this was actually addressed at one point back when Revar was handling things. We changed all the fopen calls to add the 'b' option so that on both windows and linux it'd use the binary open and avoid all of this. The problem generally seems to be that when the database files are compressed/uncompressed (not the muck itself, but using other tools) or transferred via FTP, it...
2009-10-09 22:16:22 UTC by foxbird
-
foxbird, this is going to take some coordination with me (winged). Please contact me when you get the chance. (need to figure out the different ways different string-handling routines handle end-of-line, and you're the one with the references on the Windows side of things; I don't want to mess up the UNIX code, though.)
2009-10-06 22:50:15 UTC by winged
-
The Windows build is rather annoying as far as line breaks go. The
reason why is because on UNIX (where the original server was built)
there is no difference between binary and text modes -- neither will
screw with the stream. Because it's text, it was never told to open
everything in binary mode.
On Windows, text lines end with \r\n, rather than simply \n. This
means that when things...
2009-10-06 20:05:12 UTC by dngngrndadmn
