My system is Manjaro Linux. But I think this does not metter. In settings panel I cannot make CapsLock as keyboard layout changer. _Please help_.

I have a Dell Latitude 7400 laptop running Linux Mint 20.1, with Linux 5.4 and Cinnamon 4.8.6. When I log in, I run this script. 1 #!/bin/sh 2 3 /usr/bin/killall xcape 2>/dev/null 4 /usr/bin/xmodmap -e 'remove Lock = Caps_Lock' 2>/dev/null 5 /usr/bin/setxkbmap -option 'ctrl:nocaps' 6 /usr/bin/xcape Lines 4 and 5 turn the Capslock key into a Control key, and xcape (line 6) turns the left Control keys (especially the one that was just the Capslock key) into Escape keys when pressed alone, or a Control key when pressed with other keys. If I have to run the script again, the killall on line 3 ends any previous xcape instances before starting a new one. I have a Logitech USB headphones + microphone headset, and fairly generic Space Travel brand Bluetooth earbuds. Whenever I plug the headset in, or connect the earbuds to the laptop via Bluetooth, it undoes the entire effect of the script, and the Capslock key is again just a Capslock key. This has happened with Monoprice brand headphones as well, although I no longer have those headphones to test now. How can I prevent connecting audio peripherals from interfering with the way I have the keyboard set up, or how can I detect when it happens and have the script above run again? I use vim, and having an Escape key no longer work as an Escape key can be very disruptive. Thank you.

1. I want my system to ascertain the state of Caps Lock (is it on or off) by inspecting the keyboard DIRECTLY. After much searching, I understand that this can be done in Python by using the module "keyboardleds". I'm not familiar with Python, **so my main request is, can you tell me how to use the module keyboardleds in a Python script, so that it tells me what the state of Caps Lock is?** The Python version on my system is 2.7.3rc2. 2. The information I've found about "keyboardleds", is too technical for me to understand. Also an example I found of how keyboardleds is used, uses complex python programming that I don't understand either. Also, the example I've looked at uses keyboardleds for one of its **other** purposes, not for the purpose I want (ie determining the state of Caps Lock). I don't even know what the "import" commands mean at the beginning of the example script, and whether I need all of them. **I would be most grateful if you could tell me what python commands I need to use, and what detailed contents I put in them.** 3. I just need the python script to give an exit status of zero (true) if Caps Lock is off, and an exit status of 1 (false) if Caps Lock is on. Say the python script is called "capslockstate". Then I'll use it in a bash script as follows: if capslockstate then else fi 4. SIGNIFICANT I BELIEVE: Regarding accessing the keyboard, the info I've found refers to using either /dev/console, /dev/input/event*, and /dev/input/by-path/*-event-kbd. On my system, all 3 of these exist. In the latter 2 cases, I've got the following on my system: /dev/input/event0 through to /dev/input/event9. /dev/input/by-path/platform-i8042-serio-0-event-kbd ### ie only ^this^ one item exists The "by-path" is the **actual** directory name. I believe that one of the above 2 "/dev/input/..." entities is what I need to use (as opposed to /dev/console), even though I don't understand the ins and outs of it. 5. Below are the websites where I found the information on keyboardleds: 1. The first site that put me onto using keyboardleds (with examples that are too complex for me): Alternative approaches for accessing keyboard LEDs in Linux with Python What particularly interested me on this site is the comment "the program [keyboardleds] accesses the keyboard DIRECTLY." 2. Official documentation I believe, on keyboardleds (too complex for me to understand): python-keyboardleds 0.3.3 documentation 3. The site of the author of keyboardleds: python-keyboardleds — Jakub Wilk's software

I was trying to show the capslock status on hyprlock , the default screenlock hyprland window manager uses, to avoid unnecessary password failures, as xset -q | sed -n 's/^.*Caps Lock:\s*\(\S*\).*$/\1/p' is not any help for wayland. So far I am able to accomplish this putting in hyperlock conf

label {
    monitor =
    #CapsLock status
    text = cmd[update:500] echo "CapsLock $(cat /sys/class/leds/input*::capslock/brightness)"
    color = rgba(200, 200, 200, 1.0)
    font_size = 25
    font_family = Fira Semibold
    position = 30, 70
    halign = left
    valign = bottom
    shadow_passes = 5
    shadow_size = 10
}

It just shows the status like CapsLock 1 or CapsLock 0 but I think a better result can be achieved calling a script in the conf like CapsLock on.

Under X, I can make Caps Lock behave as Esc when pressed briefly, but as Ctrl when held down with: setxkbmap -option 'caps:ctrl_modifier' xcape -e 'Caps_Lock=Escape' -t 100 How can I replicate this behavior under Sway / Wayland?

I'm on a 20.04 Ubuntu machine. I've been trying to use a combination of

and

to map AltGr and escape onto my caps-lock key, where a *quick key press* acts as **escape** and a *longer key press* acts as **AltGr**. I believed the desired behavior could be achieved by executing the following:

$ setxkbmap -option lv3:caps_switch
$ xcape -e 'Caps_Lock=Escape' -t 300

Once the setxkbmap command is executed however, the xcape process/daemon no longer makes caps-lock act as escape when tapped. I'm not entirely sure why since the **xcape process is still running**, so I might just simply be oblivious to how setxkbmap works (I tried executing the commands in a different order, with the same result). How would I go about achieving the desired behavior? Why does setxkbmap 'silence' the xcape daemon regardless of whether I execute xcape before/after executing the setxkbmap command?

I am using Arch Linux and Openbox window manager with all the latset updates For years I have struggled with the caps lock key. I never know it's status until I come to use it. The same for all of us. I have to push it a few times, and experiment to find out where it is, upper or lower, then get it where I want it, upper or lower Obviously a huge waste of time I am planning to - leave caps lock key as a toggle caps key - assign = key to upper case - assign # key to lower case I believe this will be much simpler I can use a script to release these keys if necessary and put everything back to default as I am sure will be necessary now and again How can I distinctly get set either upper or lower case via a script?

I've updated to Fedora 26 and now my Capslock key behaves strangely (or not at all). In Fedora 25 the xkb setting worked perfectly for both my Ctrl and Caps changes. I've selected "Caps as Ctrl" in Gnome Tweak Tools, but Caps just does nothing at all! Using xev I get the following output for the caps key: KeyRelease event, serial 36, synthetic NO, window 0x2600001, root 0x273, subw 0x0, time 2293119, (164,-21), root:(271,94), state 0x10, keycode 66 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False the bracket after keycode should contain LCtrl instead of NoSymbol. I've also tried deactivating and or activating Caps. As well as that I've tried to modify /usr/share/X11/xkb/keycodes/evdev and use Caps = 37; which would make Caps similar to Left Control - but this as well has no effect whatsoever. Please help me - since wayland I'm kinda lost here! I've also changed Left Control and Alt by: = 37; //64; = 64; //37; In the previously stated file -> this still works like a charm!

I'm trying to enable capslock with a console command, is there a possibility to do so? I found setleds +/-caps but that only works in a non-graphical environment sadly. Any help is appreciated, thanks!

I am trying to remap caps lock to escape on the keyboard. I tried the following solution found on AskUbuntu without success:

$ xmodmap -e "keycode 9 = Caps_Lock NoSymbol Caps_Lock"
$ xmodmap -e "keycode 66 = Escape NoSymbol Escape"
$ setxkbmap -option caps:swapescape

what shall I do?

I already understand how to remap keys in an X graphical server. However, I sometimes like to do work from a TTY and cannot seem to figure out a way to functionally remap Ctrl to Caps Lock. I have already tried creating a .keymap file with the following contents:

keycode 37 = Control_L

Then sourcing it using loadkeys, but to no avail. However, 37 is the keycode for Ctrl in X (according to xmodmap -pke | grep 'Control') so perhaps the keycode is different in a TTY? If so, how would I go about determining the correct key code and subsequently setting the remap?

Why can't I switch my layout with these settings:

setxkbmap -layout us,ru -option grp:alt_caps_toggle,compose:caps

Is it possible at all to have a compose key assigned on CapsLock and a layout switch combination relied on this key? Also, how to turn off Shift+CapsLock combination?

I can disable Caps Lock in the GUI using following command: setxkbmap -option ctrl:nocaps But how can I disable it completely in the console, on a machine without X/GUI ?

My Xorg program uses tty1. Use Ctrl+Alt+F[2~6] to switch between ttY[2~6]. At this time, the NumLock or CapsLock state (including the corresponding LED light on the keyboard) can be synchronized normally. If I switch between tty1 and tty[2~6], the NumLock or CapsLock state is normal, but the keyboard light does not switch normally. I want to know, who is responsible for saving and switching the NumLock or CapsLock state of the tty keyboard (including the corresponding LED light on the keyboard)? Use evtest to monitor keyboard events, an example is as follows: scene 1: tty1: Num led is on, you can input numbers; tty2: Num Led is off, you cannot enter numbers; tty1-->tty2: Num led is on, no number can be input ctrl+alt+f2, tty1-->tty2, evtest print as follows: Event: time 1631671173.524324, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631671173.524324, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1631671173.524324, -------------- SYN_REPORT ------------ Event: time 1631671173.612530, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2 Event: time 1631671173.612530, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1631671173.612530, -------------- SYN_REPORT ------------ Event: time 1631671173.684525, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003b Event: time 1631671173.684525, type 1 (EV_KEY), code 60 (KEY_F2), value 1 Event: time 1631671173.684525, -------------- SYN_REPORT ------------ Event: time 1631671173.804507, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631671173.804507, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0 Event: time 1631671173.804507, -------------- SYN_REPORT ------------ Event: time 1631671173.812235, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2 Event: time 1631671173.812235, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1631671173.812235, -------------- SYN_REPORT ------------ Event: time 1631671173.824310, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003b Event: time 1631671173.824310, type 1 (EV_KEY), code 60 (KEY_F2), value 0 Event: time 1631671173.824310, -------------- SYN_REPORT ------------ scene 2: tty2: Num led is on, you can input numbers; tty3: Num Led is off, you cannot enter numbers; tty2-->tty3: Num led is off, no number can be input ctrl+alt+f3, tty2-->tty3, evtest print as follows: Event: time 1631671357.985873, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631671357.985873, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 Event: time 1631671357.985873, -------------- SYN_REPORT ------------ Event: time 1631671358.097893, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2 Event: time 1631671358.097893, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1 Event: time 1631671358.097893, -------------- SYN_REPORT ------------ Event: time 1631671358.181861, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003c Event: time 1631671358.181861, type 1 (EV_KEY), code 61 (KEY_F3), value 1 Event: time 1631671358.181861, -------------- SYN_REPORT ------------ Event: time 1631671358.313866, type 17 (EV_LED), code 0 (LED_NUML), value 0 Event: time 1631671358.313866, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7003c Event: time 1631671358.313866, type 1 (EV_KEY), code 61 (KEY_F3), value 0 Event: time 1631671358.313866, -------------- SYN_REPORT ------------ Event: time 1631671358.321862, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0 Event: time 1631671358.321862, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0 Event: time 1631671358.321862, -------------- SYN_REPORT ------------ Event: time 1631671358.337870, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2 Event: time 1631671358.337870, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0 Event: time 1631671358.337870, -------------- SYN_REPORT ------------

I routinely disable Caps Lock and the respective modifier with a script, using xmodmap. That all works fine. Sometimes, however, for some reason unknown, Caps Lock is active. Having no key bound to Caps_Lock and no key bound to toggle the Lock modifier, I cannot switch Caps Lock off unless I reset the keymap, press the key, then re-map it to my desired configuration. So: **How can I disable Caps Lock (currently active) without re-mapping keys and with no keys bound to do the job?** Perhaps a command line tool can set the state? For anyone interested, here is how my script disables the accidental activation of Caps Lock by a key press (I never enable it intentionally): #!/bin/sh # I never want to use Caps_Lock. Make Caps_Lock another Control_L... xmodmap -e "remove Lock = Caps_Lock" 2> /dev/null xmodmap -e "keysym Caps_Lock = Control_L" 2> /dev/null xmodmap -e "add Control = Control_L" 2> /dev/null

So, I got a Lenovo Chromebook running the latest ubuntu Mate, and I really hate this Searcch button bringing up the top left corner menu. So, I decided that I will make a Caps Lock from it, but I am new at linux. I already searched the net, but nothing. Changed some the keycode thing, still nothing. As I found out, the key's keycode is 125. Thank you.

I need a program, say a Python script, to be notified when the CapsLock and NumLock status are changed. I may have several keyboards and the code must run in user space so I can't rely on a kind of keylogger to receive KEY_CAPSLOCK events. Some tools fire visual notifications by running xset q in a loop, but I can't find anything useful for receiving direct events. I don't want to use the xset method because I don't want to use a loop, I don't want to use an external tool and also that would need an X server.

I wanted to remap CapsLock to work as escape, and I did it. What I did was: setxkbmap -option caps:escape But that method has a problem. Whenever I press CapsLock, on top it of working as escape, it also locks capitals. My question is, is there any way in which I can make CapsLock not lock capitals, but keep its new function? (and please, if possible, in case your method makes the LED light up, help me turn it off). I want this to work with vim, but I think it would be more appropriate to remap it at an OS level. As the saying goes, "I use Arch btw" Thank you very much. Edit: Finally solved it! setxkbmap -option caps:swapescape

I'm not sure how this happened. Maybe it was when I was adding a second layout to my keyboard somehow (although I only added another language). When I press caps, which I only use and have only used to capitalize alphabetical characters, now I get the behavior of shift: the spacebar doesn't work, numerical character such as 123 become !@#. This greatly affects my workflow in a negative way. When I run setxkbmap -query this is what I get back: rules: evdev model: pc105 layout: us,il variant: intl,biblical options: caps:caps_toggle And this is only after I tried running setxkbmap -option -option caps:caps_toggle. I've also tried the same with caps:caps_lock with no result. Before I did this, -query returned rules: evdev model: pc105 layout: us,il variant: intl,biblical options: caps:shiftlock,caps:caps_lock,caps:capslock,caps:none,caps:nocaps,caps:caps,caps:capslock,grp:toggle Although the options are different, the behavior is the same. I know this is an issue with the X keyboard, since this doesn't happend when I switch to a purely terminal screen.

I am using lightweight Linux, with Xorg, an minimal xbase-client for the only purpose to launch specific program on remote site. These programs used by lambda users works well with a single default. When used on laptop computer with no digit-keypad the only way to type digits on entry fields is to use the upper line of the keyboard. The thing is that with an English/US keyboard there is no problems, but with a French keyboard if I type the keys 123 with shift I got 123, with nothing pressed I get &é" and with capslock pressed I get &É". But for most user when they are entring digigs they are used to set capslock on and directly type the digits. Which, in this case is not effective. Is there a way to have capslock do the same as keeping shift while typing?