2004-11-29 - compilable for AMD64 and new glibc 2003-05-01 - bugfix: some odd bug where you were not able to switch to the mumps environment anymore 2002-12-18 - bugfix: submitted by Elestir '2002/06/13 14:43, Elestir: #error: bad action pattern `You intercept &1'&2' #missing digit after `$' This is not error in your client setup. This is error in powwow, that might sometimes even cause crash.... 2002-07-19 - bugfix: POWWOWPAGER was ignored for some reason, and the POWWOWEDITOR used instead. Tht is fixed now -> if POWWOWPAGER is not defined less will be used 2002-06-19 - bugfix: latin1-convertion when powwow variables got imported into mumps 2002-06-17 - after using \; in an action pattern, the action was unescaped and then stored. Thanks to Alexander Piskunov (MUME: Utu), who found and fixed that bug 2002-06-10 - fixed latin-1 stuff 2002-06-06 - the internal lines variable (height of the screen) in now imported to mumps 2002-02-23 - fixed an overflow bug regarding last_command 2002-02-19 - new command #xed [filename] will use the specified local editor settings to edit the given file. if no filename is specified, an ls will be issued. if no DISPLAY variable is set, just 'vi' will be used as editor. 2002-02-15 - new option: #option +lastcmd (default: -lastcmd) if active and only RETURN without input is pressed, the last command will be repeated. only data longer than 1 char will qualify as 'last command'. that way (most) directions are filtered out. 2002-02-14 - bugfix: overflow bug, since mumps variables can only handle 256 chars per node :/ - some speedups when switching between powwow and mumps 2002-02-12 - bugfix: #save - bugfix: lost input chars when you use #mumps a lot (e.g. triggering on Exits..) it was possible that occasionally input was lost - most likely when spamming bindings - I think I found the bug and fixed it 2002-01-17 - on certain occasions (very rarely) the mumps environment gets bugged. it happens sometimes when my online swedish->english translation triggers - does not happen when i do not use that. I played mortal 23h in a row without restarting and without problems, so its safe. Anyways, I did add a new command #mi (mumps-env-reset), so if an error occured just add the #mi at the end of the script or before or whereever to work-around. 2002-01-10 - misc fixes regarding intercommunication between powwow and freem - output fixes 2002-01-03 - fixed the old mumps-script-reroad bug (means: you do not have to restart powwow once you changed a mumps script) 2001-12-28 - if a line starts with // it will be treated as a comment - new command #me - without argument it will show what mumps scripts exist in the current directory - with argument it will edit the given script (using vi) 2001-11-20 - disabled direct database access changes -> was bugged :/ - added a new command #di[splay] - display : set the DISPLAY environment variable e.g.: display 192.168.5.1:0.0 - display - unsets DISPLAY in the shell environment - local-edit view command works again 2001-07-30 - added direct database access which means: - you get a new variable type for database-access '^' so you can issue commands like: #var ^test("temp",1)=($room) #var $room=^test("temp",1) 2001-07-13 - bugfix: after editing a routine using the integrated editor it didnt correctly reload