Indeed! When using 2>&1 the filtered output comes out as errors (black bkg and red text). Is there anyway to correct that?
________________________________
De: Pd-dev pd-dev-bounces@lists.iem.at em nome de Christof Ressi info@christofressi.com Enviado: domingo, 24 de maio de 2020 18:30 Para: pd-dev pd-dev@lists.iem.at Assunto: Re: [PD-dev] Filter PD debug output in Powershell
Hi,
your problem is that Pd writes the messages to stderr, but the pipe operator reads from stdout. You can redirect stderr to stdout with "2>&1" before filtering the output (should also work in modern Powershell).
Christof
On 24.05.2020 22:50, Henri Augusto Bisognini wrote: Hey list! Hope you're all well!
I'm debugging communication between the core and the gui with "-d 3" and i want to filter out all those mouse "motion" and "coords" events in PowerShell.
I'm trying
./pd.com -d 3 | ? {$_ -notlike "*motion*"}
But it doesn't work. Interestingly this one does work:
"abc", ".x695480 motion 208.0 124.0 0;", "efg" | ? {$_ -notlike "*motion*"}
Whats wrong?
Cheers, Henri.
_______________________________________________ Pd-dev mailing list Pd-dev@lists.iem.atmailto:Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev