e72c25b0bc
Create infrastructure for input event handling and add i3bar event processing. For each event, callbacks can be registered in the input module. Modules and widgets both identify themselves using a unique ID (the module name for modules, a generated UUID for the widgets). This ID is then used for registering the callbacks. This is possible since both widgets and modules are statically allocated & do not change their IDs. Callback actions can be either callable Python objects (in which case the event is passed as parameter), or strings, in which case the string is interpreted as a shell command. see #23
21 lines
561 B
Python
21 lines
561 B
Python
import shlex
|
|
import subprocess
|
|
|
|
try:
|
|
from exceptions import RuntimeError
|
|
except ImportError:
|
|
# Python3 doesn't require this anymore
|
|
pass
|
|
|
|
def execute(cmd, wait=True):
|
|
args = shlex.split(cmd)
|
|
proc = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
|
|
|
|
if wait:
|
|
out, _ = proc.communicate()
|
|
if proc.returncode != 0:
|
|
raise RuntimeError("{} exited with {}".format(cmd, proc.returncode))
|
|
return out.decode("utf-8")
|
|
return None
|
|
|
|
# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4
|