Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ Logs
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Olli
(1 post) Bio
|
| Date
| Mon 03 Mar 2008 05:16 AM (UTC) |
| Message
| 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 | | Top |
|
| Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Mon 03 Mar 2008 06:08 AM (UTC) |
| Message
| It would help to know which version of MUSHclient you are using, as you are asked to provide when submitting bug reports.
Quote:
I managed to set the automatic log feature to "...\logs\%m\%d.txt"
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. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Isthiriel
(113 posts) Bio
|
| Date
| Reply #2 on Tue 04 Mar 2008 05:26 AM (UTC) |
| Message
| 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. | | Top |
|
| Posted by
| Shaun Biggs
USA (644 posts) Bio
|
| Date
| Reply #3 on Tue 04 Mar 2008 04:38 PM (UTC) |
| Message
| 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. |
It is much easier to fight for one's ideals than to live up to them. | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
15,799 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top