trying to output to file results in empty file about goswifty HOT 6 CLOSED

Hey, sorry for making you crazy 🤯.
I did test it too fast when I tried on my last answer. I didn't compile and test the same build, i mixed them!!! 😬
So using commit 9af4d107676f780c481f04c62a7224d2a407319d, piping works as expected. 🎉
Thanks for the work!

from goswifty.

Hi :)

I might be wrong, but isn't the command supposed to look like this?
/usr/local/bin/goswifty analyze $PATH >> result.txt

I saw in replies in Twitter that people were able to run it in the CI. Can you try some other command line tool and see if it can produce the output?

If it doesn't work I'll try to reach out to someone who managed to set it up on CI.

from goswifty.

For this problem, there is no real difference in > or >>, the modifier just affects to resulting file (fresh content or append to existing).
Pipes are also not working:
/usr/local/bin/goswifty analyze $PATH | less
Is some kind of problem with with output buffer, I don't understand what's going on. I suspect from TerminalController, but that's all I can guess at the moment.

Could you test it yourself in your command line/terminal of choice? And tell me if it works for you?
I've the same problem using zsh and bash.

from goswifty.

@raid5 has just updated the output library in #6.
@kikeenrique could you please check if the issue is solved for you?

from goswifty.

Seems like on my computer the issue is still there.

from goswifty.

Yeah, I'm still reproducing it.

from goswifty.