Version: 0.19 #3100 (using KDE 3.5.2, Gentoo) Compiler: gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9) OS: Linux (i686) release 2.6.16-gentoo-r9-20060701 /exec can't run shell commands. This prevents quick little conversation helpers like "What kernel are you running?" "/exec -o uname -a" and differs from both X-Chat and irssi.
'/exec cmd', however, can. Closing.
But there's apparently no equivalent to "/exec command" (display the output, but don't send it to the channel/user)
Rename for clarity.
Why is this necessary? There is Konsole, and an embedded konsole window.
yes, there is konsole, but for quick one off commands, its often overkill. There are a lot of external commands that you'd want to run from the client... /exec host <some hostname> /exec host <some ip> /exec whois <some hostname> /exec whois <some ip> All of those are common cases, and that's not even getting into typical "power user" scenarios, such as checking a host against DNSBLs, setting up ssh/ssl tunnels, and stuff. Also, once there's scripting capability, it will be desireable to invoke and interact with shell commands from scripts.
When I tries to run /exec -o uname -a in konversation 1.2 alpha 3 on kde 4.2.4 in debian sid I got a error messege that telle me it cannot find scriptet "-o" ([14:48] [D-Bus] Fejl: Kunne ikke finde scriptet "-o") So I geuss that is still valid (even after all thoes years)
As stated above, "/exec cmd uname -a" (or just "/cmd uname -a" due to the auto-generated alias) would work just fine, assuming your intent is to send the output to the current channel or query. This entry is kept open because there's an unimplemented wish for the "cmd" script to recognize a parameter that makes it merely display the output to the user locally, rather than send it out for all to see.