Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

Bug ID	16165
Summary	overwritten printouts for triggers
Product	Sorcery
Version	Untargetted future release
Hardware	x86
OS	Linux
Status	NEW
Severity	normal
Priority	P2
Component	Cast
Assignee	sm-sorcery-bugs AT lists.ibiblio.org
Reporter	sobukus AT sourcemage.org
Classification	Unclassified

19:57 <+sobukus> wich: a data point, apparently not involved in this issue, but
something to consider … the only difference I get for my debugging outputs (the
Dropping lines) is such:
19:57 <+sobukus> < ESC[0mESC[36mDropping
ESC[37mESC[1mESC[40mautomakeESC[0mESC[36m because of grey dependency loop on
ESC[37mESC[1mESC[40mperlESC[0m.
19:57 <+sobukus> ---
19:57 <+sobukus> > ESC]0;[smgl-fhs]: checking triggers^GESC]0;[smgl-fhs]:
success!^GESC[0mESC[36mDropping ESC[37mESC[1mESC[40mautomakeESC[0mESC[36m
because of grey dependency loop on 
                 ESC[37mESC[1mESC[40mperlESC[0m.
19:57 <+sobukus> There's lines with checking triggers / success that get no
line end and hence overwritten?! Is that intentional?


The 'Dropping' lines are only in my debugging version of sorcery and mostly red
herrings for their intended purpose. The point here is: There's these 'checking
triggers' messages that are present on the same lines, being hidden from view.
Those should be tracked down and decided if they should get some EOLs or such.

---

      You are receiving this mail because:

• You are the assignee for the bug.