verve-plugin is primarily supposed to be a command line, right? Using package xfce4-verve-plugin 0.3.6-1 on Xubuntu 9.10 ... Entering a command such as: killall gmplayer kills my player. However, the command: kill -9 `pidof audacious2` doesn't appear to execute in verve, because if I run it in terminal, it does its job, and in verve it does not. Also, the command: echo "Do you see me?" | xmessage -file - -buttons NO:0 -center does not display a simple dialog as I would expect it to, neither does echo "Whatever" > /home/user/some.file write anything to some.file. Neither Enter nor Ctrl+Enter do properly execute any of above or similarly complex chain of commands. No error alert is thrown. Reproducible. What am I doing wrong and where does my interpretation of a command line deviate from verve's current implementation? Thanks, :)
Simple answer: no, Verve is not a shell. Shells do substitution for many stuff, which Verve doesn't. Think of Verve as a replacement for xfrun4.
And why wouldn't Verve wrap a shell? I don't know how xfrun4 works, but couldn't Verve like fork() and then execve() a `bash -c "USER_SUPPLIED_COMMAND_LINE"`? That would work as I expect it, wouldn't it?
(In reply to comment #2) > And why wouldn't Verve wrap a shell? > > I don't know how xfrun4 works, but couldn't Verve like fork() and then execve() > a `bash -c "USER_SUPPLIED_COMMAND_LINE"`? > > That would work as I expect it, wouldn't it? That's only my POV, but I think if you run commands through a simple GtkEntry “complex” commands without any visual output, you might do more harm than any good. Think of a typo, a unclosed sub-shell, or whatever, and you get stuck. You may better refer to a Quake-like terminal for these cases.
Your arguments are valid. I'm having great fun with Tilda Quake-like terminal. This issue is resolved. Thanks! :)