Hey! I wanted that! (stdout problem)

[Melkor's Therapist]

I'm running 1.3.12 on Windows XP here, and have a problem.

I can't get access to the standard output, because stdout.txt is locked exclusively while the game runs and deleted when it exits. I haven't found a way to redirect the output somewhere other than stdout.txt yet either.

This is inconvenient, since I would rather like to look at some python output from the game

stderr.txt doesn't behave the same way, it isn't locked and doesn't get deleted.

I never tried to look at the standard output in a previous release, so I don't know if this behaviour is recent or not. I've not found any mention of it in the forums.

Does anyone know how I can turn off that behaviour and get stdout.txt treated the same way as stderr.txt?

[Melkor's Therapist]

Bump.

Anyone know anything about this?

[Melkor's Therapist]

Last call for anyone who can help with this, before I give up on trying to use python with the current version...?

[megane]

If you run wesnoth from the command line, it'll dump stdout to the command line window.

To do that on Windows, go to Run > cmd, then type in the path to Wesnoth (I think; I'm on Ubuntu here >.>)

When you quit out it should have sent all its messages to that window.