You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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