adisbladis[m] has quit [Ping timeout: 255 seconds]
pstn has quit [Ping timeout: 248 seconds]
jtojnar has joined #nixos-chat
unlmtd has joined #nixos-chat
joepie91 has quit [Ping timeout: 240 seconds]
dtz has joined #nixos-chat
pstn has joined #nixos-chat
adisbladis[m] has joined #nixos-chat
infinisil has joined #nixos-chat
adisbladis[m] has quit [Ping timeout: 255 seconds]
pstn has quit [Ping timeout: 260 seconds]
unlmtd has quit [Ping timeout: 256 seconds]
dtz has quit [Ping timeout: 256 seconds]
unlmtd has joined #nixos-chat
pstn has joined #nixos-chat
adisbladis[m] has joined #nixos-chat
dtz has joined #nixos-chat
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-chat
MichaelRaskin has quit [Ping timeout: 256 seconds]
<sphalerite>
andi-: I'm not a major old-time vim user, only been using it for 3 years or so, but basically emacs with evil-mode = best of both worlds
<sphalerite>
that is, I'd much rather use emacs with nothing but evil-mode than plain vim/neovim
<sphalerite>
as for plugins, I haven't got very far with using them on emacs, just been using evil, markdown-mode (only the highlighting so far), nix-mode (idem), and haskell-mode (highlighting and compilation)
<sphalerite>
I added magit as well because I've heard so many good things about it, not used it yet though
<elvishjerricco>
what's the advantage of physlock over stuff like i3lock?
<sphalerite>
elvishjerricco: I think they're orthogonal to eacah other. physlock is for consoles, i3lock and friends are for X sessions
<elvishjerricco>
well they both serve the purpose of locking access via physical keyboard+mouse, no?
<sphalerite>
yes, but physlock won't work on X sessions and i3lock won't work on console sessions
<sphalerite>
AFAIK
<elvishjerricco>
sphalerite: Ah, I see.
<elvishjerricco>
I suppose I'm slightly concerned that I might accidentally leave myself logged in in the vty, such that something like i3lock doesn't prevent ctl alt f1 from giving access. Using physlock -l and i3lock together would mitigate that and provide the nice X lock screen.
<sphalerite>
yep
<elvishjerricco>
trying to figure out how to automate physlock -l though... Requires authentication.
<sphalerite>
wouldn't be surprised if it had setuid support
<sphalerite>
if you add a setuid wrapper for it it should work without auth
<elvishjerricco>
sphalerite: Actually, now I'm looking into `loginctl lock-session` as a trigger. I can run xss-lock as root and use lock-session to trigger it as a user with no auth.
<sphalerite>
whatever works :)
<elvishjerricco>
problem is that then the locker is run as root, meaning it doesn't take the right password :/
ekleog has quit [Quit: Let the fun begin]
ekleog has joined #nixos-chat
ekleog has quit [Client Quit]
ekleog has joined #nixos-chat
ekleog_ has joined #nixos-chat
ekleog has quit [Disconnected by services]
ekleog_ is now known as ekleog
ekleog_ has joined #nixos-chat
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-chat
jtojnar has quit [Remote host closed the connection]