Re: Execute command and wait until it's execution finishes

2015-08-10 Thread Bruno Ferreira
Hi Jayson,

Using pipes seems to me like a great way to do it, why don't you want to
use pipes?

2015-08-10 17:15 GMT+01:00 Jayson Willson jaysonwillson...@gmail.com:

 Hello! I need the following: execute some command and go to the next
 command of the function only when the first command is finished.
 What I have now:

 awful.key({}, XF86AudioMute,
 function ()
 awful.util.spawn(amixer set Master toggle)
 update_volume(volume_widget)
 end)

 Thus update_volume takes place earlier, than amixer set Master toggle
 finishes it's execution, and I do not get required result.

 One guy suggested using popen:
 function ()
 local f = io.popen(amixer set Master toggle)
 f:close()
 update_volume(volume_widget)
 end)
 It works fine, but I wonder if there is a way to implement it without
 pipes. Could you please help me? Thank you.

 --
 To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.



Execute command and wait until it's execution finishes

2015-08-10 Thread Jayson Willson
Hello! I need the following: execute some command and go to the next 
command of the function only when the first command is finished.

What I have now:

awful.key({}, XF86AudioMute,
function ()
awful.util.spawn(amixer set Master toggle)
update_volume(volume_widget)
end)

Thus update_volume takes place earlier, than amixer set Master 
toggle finishes it's execution, and I do not get required result.


One guy suggested using popen:
function ()
local f = io.popen(amixer set Master toggle)
f:close()
update_volume(volume_widget)
end)
It works fine, but I wonder if there is a way to implement it without 
pipes. Could you please help me? Thank you.


--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.


Re: Execute command and wait until it's execution finishes

2015-08-10 Thread Jayson Willson
Actually, there is no reason not to use them. I just do not know, if 
this way is the correct and the optimal one. And, really, I do not know 
what pipe is.. :-)


--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.


Re: Execute command and wait until it's execution finishes

2015-08-10 Thread Elv1313 .
Hello,

You can use my async module located here
https://github.com/Elv13/awesome-configs/blob/master/utils/fd_async.lua

It has lots of non-blocking async functions to do things like you
want. However be warned many people report it segfault Awesome in some
situations. This seem to be caused by various LGI bugs and maybe a few
introduced by my code too. It is stable enough for my use case, but I
totally acknowledge some corner cases can cause segfaults.

On 10 August 2015 at 14:06, Jayson Willson jaysonwillson...@gmail.com wrote:
 Actually, there is no reason not to use them. I just do not know, if this
 way is the correct and the optimal one. And, really, I do not know what
 pipe is.. :-)


 --
 To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.


(KDE) Plasma 5 and Awesome

2015-08-10 Thread Max Görner
Hey there,
I updated my Debian Stretch to Plasma 5 now. With KDE 4 I used KDE as a window 
manager for KDE. Now thats not possible anymore.

One main problem is that I can't choose Awesome as a window manager from the 
settings as it was possible in KDE 4. There may be ways around it (see 
https://barlog.rusu.info/valentin/blog/?p=292 for example), though.

I'm a bit anxious to try thoose since I would prefere to not alter basic 
configuration files. I also would like to have a solution which is easily 
reversed. Has anyone combined Plasma 5 and Awesome already and some 
experiences to share?

Also, can anyone tell how good Plasma 5 and Awesome go together? I tried to 
kill kwin_x11 and to start awesome afterwards but the result was not promising 
since Awesome's task bar was missing.

Thanks alot,
Max Görner

signature.asc
Description: This is a digitally signed message part.


Re: (KDE) Plasma 5 and Awesome

2015-08-10 Thread Max Görner
Thank you for that instant reply.

Option 1 is what I used and what I like. Since the KDE-Prefix changed, I had 
to copy the awesome.desktop file to reenable that solution.

Unfortunately, Awesome and Plasma 5 seem to not go well together. Awesome's 
bar did not appear, as in my first try. More severe is that I cant enter text 
anywhere and basic window managment as changing virtual desktops or windows 
does not work.

Has anyone experienced or even solved these problems?

signature.asc
Description: This is a digitally signed message part.


Re: (KDE) Plasma 5 and Awesome

2015-08-10 Thread Jayson Willson
Please have a look at this article: 
http://awesome.naquadah.org/wiki/KDE_and_awesome


If you do not want to change anything in your system, Option 2 may be 
useful. However, if you decide to use Option 1, it is totally harmless, 
as you do not change anything, but add an additional option, which suits 
your needs.


--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.