The issue seems to be Keysharp interfering!

Original post:


I have this set up as a startup script, but it only sometimes triggers, despite setting a 20-second delay:

#!/bin/bash
sleep 2
xmodmap -e "clear lock"
xmodmap -e "keycode 66 = Return"

I have the startup command set to bash "path/Remap_Caps_Lock_to_Enter.sh". What’s going on? It works when I press the triangle button when it doesn’t work on boot.

    • Flagstaff ( Flagstaff@programming.dev ) OP
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 months ago

      I’m a newb! How do I check boot logs? However, I’m not sure of how relevant those may be (also @Artwork@lemmy.world - I don’t know if that tagged correctly, but I hope so); I just discovered another mysterious piece of the puzzle: it initially works on login, but about 5 min in, something actually undoes the mapping and I have no idea of what; rerunning the script fixes it until the next shutdown.

      Other remapping/expansion tools I use are Keysharp and Espanso, if that helps to know, but I don’t have them interacting with Caps Lock… I would like to more easily manage this just through Keysharp, but Keysharp currently can’t seem to block the native function of Caps Lock from simultaneously occurring.

      Hmm, another thought I had is that I wish startup times would have no maximum delay; Mint Cinnamon’s max is a 100-second delay; why?.. That’s annoying. That alone could possibly solve this (even if just as a workaround).