Hi Dan,

It just seemed like the 'systemd' way to lock the session is with `loginctl lock-session` and I wasn't sure whether there were any side effects that would be skipped if `i3lock` were run directly.

Also, it seemed to me that the `&& sleep 1` looks hackish.

So since upstream i3 included the `xss-lock` config line I ran with it.

Cheers,
Casey

On Sun, May 9, 2021 at 4:30 PM Dan Čermák <dan.cermak@cgc-instruments.com> wrote:
Hi Casey,

Casey Witt <kcwitt@gmail.com> writes:

> 3. install `xss-lock` (this is already included in the default i3
> config file) to enable auto start of i3lock when the display is locked;
> and add a keybinding (mod+shift+p - but use a keycode since I am using
> Dvorak keyboard layout (which maps this to mod+shift+l in Dvorak)) to
> lock the screen
>
>    ```
>    sudo dnf install xss-lock
>    echo 'bindcode $mod+Shift+33 exec --no-startup-id loginctl
> lock-session' >> ~/.config/i3/config
>    ```

Out of curiosity, why don't you use:
--8<---------------cut here---------------start------------->8---
bindcode $mod+Shift+33 exec --no-startup-id i3lock && sleep 1
--8<---------------cut here---------------end--------------->8---
as upstream suggests?


Cheers,

Dan