Closed lasers closed 6 years ago
Superseded by #1169. I feel this particular moc
issue is a trivial issue that could be overcome by adjusting the seek numbers to scroll with... and that the users will not scroll like a maniac for a long period of time. I think the probability of this happening again for a different good reason may be relatively low.
The module sometimes disappears with
on_click
. I go and look now.Code.
Okay. I see try/except. We say bye to them.
I get this with
self.py3.command_output(['mocp', '--info'])
.I get this with
self.py3.command_output('mocp --info', shell=True)
.Notes: Command
m
... when exception... above withshell=True
. Why? EDIT: Due tocommand[0]
Commandmocp
returned non-zero exit status -6(State: PLAY )
. Why? I see(State: PLAY )
. That's the first line of output. Did error irly happen? Why?Output:
On_Click:
http://py3status.readthedocs.io/en/latest/configuration.html#custom-click-events
Maybe we should have
prevent
option foron_click
as I am wondering if runningmocp
seek command, then update right away (semi repeatedly) could sometimes trigger an issue inpy3status
and/or thepy3.command_*
commands. Anyhow, let me know what to try.