Artem Chernyak
Artem Chernyak
Same issue here something seems to be off about how the package is distributed.
I don't think we are going to reach compatibility on this. The apis seem to have drifted too far apart. As I attempted to fix the `--uncleared` flag, I continued...
So I just saw that multiple commands needed to be updated, and couldn't just be generalized. e.g., both modes share the `-U` flag but it acts different, the `--sort` flag...
Thanks for the suggestion. I'll be sure to use that.
I was originally on `1.7.4` then I tried upgrading to `1.8.0` and still the same exact error.
@asciimoo I am on windows 10 running `Bash on Ubuntu on Windows`. It seems that they do have 256 color support and my terminal is identified as `xterm-256color` by default....
Thanks for the really quick work around on this. However, it looks like there is still an error further down the code. The error moved now. ``` panic: invalid argument...
@asciimoo It is still getting thrown in the same expression actually. `OutputNormal` seems to be throwing too. I was trying to set it to `OutputGrayscale` which seems to be supported...
@asciimoo no still no luck with it. I was not able to get it to set to `OutputGrayscale` looks like `gocui` only supports `OutputNormal` and `Output256`.
@asciimoo unfortunates it looks like I am still getting a panic there... ``` 2017/03/14 06:49:12 invalid argument panic: invalid argument goroutine 1 [running]: log.Panicln(0xc420055ec0, 0x1, 0x1) /usr/local/go/src/log/log.go:336 +0xc0 main.main() /home/achernyak/go/src/github.com/asciimoo/wuzz/wuzz.go:1630...