AcidWeb/CurseBreaker

Running in headless mode forcibly clears my terminal

Closed this issue · 3 comments

When running in Headless mode, I find that my terminal output has been forcibly cleared. The stdout output from my script from before invoking CurseBreaker is all lost as a result. I was expecting that when running in headless mode that there would just be some details logged in stdout/stderr but instead all my previous output is gone.

In particular I am rolling this into my script to update both classic and retail addons, so I can only see in the output whichever update runs second. Instead I would expect to see the output from both CurseBreaker runs in sequence in my output.

I will take look later.

This can be reproduced without even using the wow directory as the terminal seems to always be reset
cursebreaker-issue-demo.sh.txt

Works great in the fixed build (v3.18.2) thanks!