It's a lot more sensible than dialog.
Usage (from 2007-03-05) ∞
Example ∞
KDIALOG=`kdialog --title "Main title" \ --inputbox "Enter your text"` if [ $? = 1 ]; then clear echo "Aborted.." exit 0 fi echo $KDIALOG
An example, using Subversion ∞
xterm -fn 9x15 -bg black -fg gray -sl 10000 -geometry 113x46+0+0 -title 'SVN Commit' -e \ svn commit -m "`kdialog --title "SVN Commit" \ --inputbox "Enter your comment"`"
You can give it input to begin with, like this:
kdialog --inputbox "Enter your comment" "default"
Another example ∞
xterm can take multiple commands:
cd /path/to/dir nohup \ xterm -fn 9x15 -bg black -fg gray -sl 10000 -geometry 113x46+0+0 -title 'SVN Update' -e \ $SHELL -c "\ svn commit -m "`kdialog --title 'SVN Commit' --inputbox 'Enter your comment'`" ; \ echo 'exiting in 5' ; \ sleep 5 \ " >> /dev/null&
As an application launcher ∞
kdialog --inputbox "Run program"
bbkeys ∞
With bbkeys (editing its .bbkeysrc) I did this:
[Execute] (Mod1-Control-R) {exec `kdialog --inputbox "Run program"`}
I wonder if it supports reading in a history file for a dropdown box of previous commands. At a glance I don't think it does.
But if KDE libraries have to load every time, that's rather stupid! =/
openbox ∞
With Openbox (editing its hotkeys) I did this:
<keybind key="W-r"> <action name="Execute"> <command> sh -c '`kdialog --inputbox "Run program"`' </command> </action> </keybind>
Last updated 2021-05-15 at 17:17:46
ported