Skip to content

Conversation

@walshb
Copy link

@walshb walshb commented Feb 23, 2012

Hi

I added some code to write a log file in the output directory. This makes it easier to see what's going on.

Cheers

Ben

@rastersoft
Copy link
Owner

Currently you can have something simmilar using devede-debug: it writes all the output to the file "devede.debug" at your HOME directory.

@walshb
Copy link
Author

walshb commented Mar 4, 2012

Hi Sergio

Sure, but this keeps the logging right next to the output, so you have a
permanent record. And it happens anyway, so you don't have to type
"devede_debug.sh" at the command line. (devede-debug appears to write to
the current directory, not $HOME).

Also, as you can see, I tidied up the way the "subprocess" module is being
called, so you don't need so many batch files and so on.

Cheers

Ben

On Sat, 3 Mar 2012, Sergio Costas wrote:

Currently you can have something simmilar using devede-debug: it writes all the output to the file "devede.debug" at your HOME directory.


Reply to this email directly or view it on GitHub:
https://github.com/devede/Devede/pull/9#issuecomment-4306716

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants