Should wob really exit due to invalid input? about wob HOT 4 CLOSED

Implemented in #67

from wob.

I would also rethink behaviour for inputs out of range [0;100]. It is not something unimaginable that I want to set my volume to 150%... Ultimate solution would be displaying the bar as if it were set to 100% with the text in the middle 150. Displaying text is also handy for values below 100.

Of course all of these would be set via flags so I'm proposing:

• accept values above 100 (default allow)
• ignore invalid input (default true)
• display text (default true)

Temporary solution

some_command | grep -P '^([0-9]{1,2}|100)$' > /path/to/wob.fifo

from wob.

You can set maximum value via -m flag to allow values above 100. I think there is always some kind of maximum value - sound/brightness doesn't go up to +inf. I have not come across situation where it wasn't possible to feed wob only valid values. Maybe you provide some examples where this might happen.

One thing I want to add is to print input that caused wob to exit. With startup command like this, it should give you some hints about what went wrong.

exec mkfifo $SWAYSOCK.wob && tail -f $SWAYSOCK.wob | wob 2> ~/.wob.log

from wob.

Temporary solution

some_command | grep -P '^([0-9]{1,2}|100)$' > /path/to/wob.fifo

My solution is this: $(($volume > 100 ? 100 : $volume))

from wob.