Hey @dascandy
I hadn't noticed when I was looking at it the other day that the compile errors I was seeing were output by evoke. I thought it was the compiler being noisy and interrupting.
Therefore I've added the \e[K to the end of each of those lines as well. I removed a few newlines that looked to me like they'd been added as a hackish way of clearing the line (what \e[K does now). If you prefer the newlines present, just put them back ;)
Also, I took the liberty of changing the print device from stdout to stderr in alignment with the error message from ReportUnknownHeaders
Finally I added the <cstring> include. I hope you find it a harmless add in your build. Without it, it wouldn't build here
Hope you're enjoying the weekend, and thanks for poking me the other day. It was fun to troubleshoot it :)
dascandy
commented
2 years ago
Hey @dascandy I hadn't noticed when I was looking at it the other day that the compile errors I was seeing were output by evoke. I thought it was the compiler being noisy and interrupting.
Therefore I've added the
\e[Kto the end of each of those lines as well. I removed a few newlines that looked to me like they'd been added as a hackish way of clearing the line (what\e[Kdoes now). If you prefer the newlines present, just put them back ;)Also, I took the liberty of changing the print device from
stdouttostderrin alignment with the error message fromReportUnknownHeadersFinally I added the
<cstring>include. I hope you find it a harmless add in your build. Without it, it wouldn't build hereHope you're enjoying the weekend, and thanks for poking me the other day. It was fun to troubleshoot it :)
Cheers!