

Hi,
I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution. - Dec 28 2013
I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution. - Dec 28 2013
Hi,
I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution. - Dec 28 2013
I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution. - Dec 28 2013
Hi,
I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution. - Dec 28 2013
I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution. - Dec 28 2013

Human-O2
Full Icon Themes by schollidesign 6 comments
Solved this issue by replacing "Type=Fixed" with "Type=Threshold" in the file "index.theme". Everything looks brilliant now.
- Oct 25 2009

Human-O2
Full Icon Themes by schollidesign 6 comments
Really nice icons. I would like to use them but I'm having a little problem.. icons in the panels and Kickoff tabs are too big and it messes up the view. Haven't noticed this with other icon themes.
Using KDE 4.3.2 - Oct 21 2009
Using KDE 4.3.2 - Oct 21 2009