Logs

I managed to set the automatic log feature to "...\logs\%m\%d.txt" and this appears to break it. I now get a
"MUSHclient has encountered a problem and needs to close." message when the client opens the world file, despite creating said folder manually.

Not sure how to open the file without it starting to log so that I can change it though. :P

It would help to know which version of MUSHclient you are using, as you are asked to provide when submitting bug reports.



I am not familiar with "..." as a directory, possibly that is causing the problem. The directory ".." means "one level up" - is that what you meant?

You are probably better off using a full pathname rather than a relative pathname, for example:


c:\Program Files\MUSHclient\logs\%m\%d.txt


Assuming you really had ".." as the directory, it depends on what is the "current directory" when MUSHclient starts up - maybe you did not have write permissions to whatever that directory was.

Trying your exact automatic log in my version (on Windows XP) did not cause any sort of crash, although it could not open the file, probably because there was no "logs" directory, or possibly because of the "..." bit.

Some versions of the Windows command line interpreter will parse '...' as a shorthand for '..\..' and '....' as '..\..\..' all the way up to 7 dots.

This was a 'feature' of Win95 that I don't think made it into the WinNT/XP branch.

Either way I don't think it was ever brought into the more general file io functions.

That sounds like an odd "feature" to have. It seems like would be extremely useful on a command line, but seeing "......\logs" in a code snippet just looks messy to me.

Either way, try "..\.." instead of "..." just to make sure that there are no problems with the file location. After that, I guess it is just trying to figure out if this is really a bug, or an anomaly from archaic Win95 usage.