Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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


acedit AT armory.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor
           Priority|P2                          |P3
            Summary|bug when i use ctrl-c for   |bug when i use ctrl-c to
                   |abroat sorcery commands     |abort sorcery commands




------- Additional Comments From acedit AT armory.com  2005-02-09 12:43 -------
well i think that this is just a limitation of bash and the way ctrl-c works,
there are multiple processes nested within each other and if one of the
sub-processes got the ctrl-c and exited the others have no way of knowing and
instead get broken pipe messages...maybe using trap can keep sub-processes 
from
getting the ctrl-c, i'll have to look into it.

It would be helpful if you list more explicitly the points at which programs
behave this way if you enter a ctrl-c. I would imagine that repeated errors 
only
occur when a subroutine is looping a lot of input, not during a steady state.

-- 
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.