Yikes, thanks! It turns out I had the && in several execs, but hadn't really locked that in to memory. I think I missed the --no-startup-id thing because when I run i3lock I also do a "xset dpms force off".
Is the parallel exec thing in the docs anywhere? It makes sense now that you point it out, but I don't see it mentioned. Also, under what circumstances is the quoting required? Am I just lucky that the && chains I have now seem to work without quotes? Brian On Mon, Apr 8, 2013 at 12:34 AM, Michael Stapelberg <[email protected]>wrote: > Hi Brian, > > Brian Grossman <[email protected]> writes: > > Sidestepping the question a little, how about something like this in > > ~/.i3/config: > > > > bindsym $mod+Return exec i3lock -n ; exec ~/bin/bruno-returns > Beware, this does not do what you probably think: > > The semicolon separates i3 commands, so you tell i3 to start i3lock -n > and to start ~/bin/bruno-returns immediately afterwards. > > Instead, use: > > bindsym $mod+x exec --no-startup-id "i3lock -n && ~/bin/bruno-returns" > > (--no-startup-id because i3lock doesn’t support startup notifications — > it starts up fast enough ;-)) > > -- > Best regards, > Michael >
