Re: [dwm] using slock from d

From: Anselm R. Garbe <arg_AT_suckless.org>
Date: Thu, 1 Feb 2007 14:01:36 +0100

On Thu, Feb 01, 2007 at 01:46:53PM +0100, Tuncer Ayaz wrote:
> On 2/1/07, Antoni Grzymala <antoni_AT_chopin.edu.pl> wrote:
> >Tako rzecze Tuncer Ayaz (w e-mailu datowanym 2007-02-01, 10:56):
> >
> >> I'm not sure it's the same problem Alex Elide had
> >> back in October but I'm not able to start slock
> >> from neither dwm's internal keygrabber nor an
> >> external one. Actually IIRC it may be so that I
> >> managed to start it once with an external grabber
> >> with dwm also running after pressing the key combo
> >> several times but repeating the key combo all the
> >> time does nothing else the seemingly refresh or
> >> redraw the screen.
> >>
> >> I tried both with or without "exec "
> >> { Mod4Mask, XK_l, spawn, { .cmd = "exec slock" } }, \
> >> { Mod4Mask, XK_l, spawn, { .cmd = "slock" } }, \
> >
> >Hi,
> >
> >I had a similar problem with xtrlock some time ago, arg suggested that I
> >add a pause before the command. The following works for me:
> >
> >{ MODKEY|ControlMask, XK_l, spawn, { .cmd = "sleep 1 && exec xtrlock"
> >} }, \
>
> thanks that works.

Well I pushed a patch of slock using longer usleep() pauses to
hg tip.
Please tell me if this works without sleep 1.

Regards,

-- 
 Anselm R. Garbe >< http://suckless.org/~arg/ >< GPG key: 0D73F361
Received on Thu Feb 01 2007 - 14:01:36 UTC

This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 14:35:43 UTC