Cool color output interferes with Pry

[e2]

It updates on top of the Pry console in Guard.

The workaround:

guard 'zeus', cli: '> /dev/null' do

I'm wondering if there's a better way than just mentioning this in the README.

[qnm]

Hi @e2

You should probably expose it as a specific option, perhaps pry_workaround: true or similar?

You should be able to hook in around

guard-zeus/lib/guard/zeus/runner.rb

Line 128 in 44ac8a4

def zeus_serve_options

.

What do you think?

[e2]

Actually my second message was supposed to be an issue in Zeus - but I got confused.

Anyway, this should be fixed in Zeus - the problem with '/dev/null' trick is that it silences errors (I'm not sure it even actually works!).

I considered logging as well. As another idea, I was wondering about capturing the Zeus output continuously, filtering it ("uncolorize") and every time a guard plugin action is triggered, it would dump the captured output.

On the other hand - I think Guard should actually be doing this. Guard could just support long-running processes internally, capture the output and dump it before and after every task.

I'm just thinking out loud here, because even if zeus would be fixed, some plugins need e.g. web servers running - and it would be nice to control their output from Guard as well.

It also seems too much work, since it's only a UI bug and doesn't prevent actually doing anything (while there is lots more important and urgent stuff to fix). That's why I thought about the README.

[luizcarvalho]

Great! This solve my problem! Thanks