got working finger print usage; update nvim

hyprlock/.config/hypr/hyprlock.conf

@@ -11,13 +11,13 @@ general {
 }
 
 # Authentication
-# Fingerprint is disabled: GDM's login worker (pam/gdm-fingerprint) holds the
-# device for the whole session, so hyprlock can never claim it -- the failed
-# claim blocked the auth thread and made unlocks appear stuck. Fingerprint is
-# still available at the GDM login screen; hyprlock is password-only.
+# Fingerprint via hyprlock's native fprintd support. PAM is password-only
+# (/etc/pam.d/hyprlock) so typing a password never fights hyprlock for the
+# fingerprint sensor. The device is not held by GDM for the user session, so
+# the old stuck-unlock issue no longer applies.
 auth {
   fingerprint {
-      enabled = false
+      enabled = true
       ready_message = Scan fingerprint to unlock
       present_message = Scanning...
       retry_delay = 250 # in milliseconds

hyprlock/.local/bin/hyprlock

@@ -4,15 +4,23 @@
 # If the real hyprlock dies, this restarts it so the session doesn't end up in a
 # "lockscreen app died" state. Requires misc:allow_session_lock_restore = true
 # in Hyprland config for the replacement lock to be accepted.
+#
+# --immediate-render: present the first frame as soon as the background is up
+# instead of waiting for every resource (labels run scripts like weather.sh).
+# Assets pop in when ready, so the "lock screen took seconds to appear" stalls
+# (Hyprland "Lockdead frames") don't happen.
 
 set -u
 
 REAL_HYPRLOCK=/usr/bin/hyprlock
 MAX_RESTARTS=20
+# hyprlock logs to stdout/stderr; capture them so the last lock cycle is
+# readable for debugging (fprint claim/verify, auth results).
+LOGFILE="${XDG_RUNTIME_DIR:-/tmp}/hyprlock.log"
 
 restart=0
 while true; do
-    "$REAL_HYPRLOCK" "$@"
+    "$REAL_HYPRLOCK" --immediate-render "$@" >"${LOGFILE}" 2>&1
     code=$?
 
     # 0: exited cleanly (e.g. unlocked) -- done.