Introduce /exec support for running simple client-side scripts
authorManuel Nickschas <sputnick@quassel-irc.org>
Thu, 12 Mar 2009 23:56:08 +0000 (00:56 +0100)
committerManuel Nickschas <sputnick@quassel-irc.org>
Fri, 13 Mar 2009 19:03:06 +0000 (20:03 +0100)
commitdd381ac71adfcd9bcad028b277fe65e13fecaf15
tree397e300fc90b2a187683b3bc6748e75aa29a0ed8
parent6d32c3e6a04a358789c469948d044715d6fb5aed
Introduce /exec support for running simple client-side scripts

/exec myscript [param1 param2 ...] runs an executable named "myscript" in one of the acceptable
script dirs ($configdir/scripts, $datadir/scripts) and pipes its stdout into IRC. This is not much,
but enough to run stuff like infobash/inxi or the infamous now-playing stuff :P

It's recommended to use aliases for invoking scripts, e.g. /audio could expand to /exec nowplaying,
where nowplaying is your fancy script that queries your Amarok for the current song.

Now keep 'em scripts coming, good ones will be included in our repo :)
src/client/CMakeLists.txt
src/client/clientuserinputhandler.cpp
src/client/execwrapper.cpp [new file with mode: 0644]
src/client/execwrapper.h [new file with mode: 0644]