On 14:01 Thu 01 Feb , Anselm R. Garbe wrote:
> On Thu, Feb 01, 2007 at 01:46:53PM +0100, Tuncer Ayaz wrote:
> > On 2/1/07, Antoni Grzymala <[EMAIL PROTECTED]> 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.
No it doesn't work for me, without sleep 1.
Regards
