Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=9514

           Summary: Better internal debugging for sorcery
           Product: Sorcery
           Version: Untargetted future release
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unknown
        AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
        ReportedBy: dmlb2000 AT gmail.com


I think it'd be nice to have a better system of debugging than 'all or none'.

Some ideas:
1) debug levels, So from a very high level debug output to a very specific low
level output (set -x for some of it is what I'm thinking)

2) Easy to use filters on the compiled debug log... so we can pick specifics 
out
of a potentially very large debug log. I was thinking on prepending some
variables like the following.

<script-run>:<script-arguments>:<file-name>:<function-name>:<function-arguments>:<debug
message>

With awk sed and grep one could easily get the specific information they are
looking for when debugging sorcery.

Any other thoughts or ideas would be great ;)

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.