From: alex <alex9-ml@proton.me>
To: "9front@9front.org" <9front@9front.org>
Subject: [9front] making permanent changes to /dev/kbmap
Date: Sat, 22 Jun 2024 14:29:48 +0000 [thread overview]
Message-ID: <mGJ6le13OT4dYZe2VIs_ObYSusYCq42n4Eh2ruO1tGcoZVw7k7cnw3GKQRRs8E6DLTL6roMk5zdzRw3myh3YfgAVWkZi6m7yT5STER6W0tA=@proton.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Hello,
on my Dell Latitude 5490 I found myself without the "<" and ">" keys (expecting them between shift and "y"). I remembered an article from sl for the MNT Reform, where a special key was customized. I've edited /dev/kbmap and it worked, but after a reboot, my changed values (0x3c, 0x3e and 0x7c for 44, 45 and 46 in layer mod4) are all 0 again.
Do I need to set up a script in my profile, setting these values after every log in, or is there a way to make my changes permanent?
Thank you very much in advance!
Best regards,
Alex
[-- Attachment #2: Type: text/html, Size: 1077 bytes --]
next reply other threads:[~2024-06-22 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 14:29 alex [this message]
2024-06-23 11:17 ` cinap_lenrek
2024-06-26 6:52 ` alex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mGJ6le13OT4dYZe2VIs_ObYSusYCq42n4Eh2ruO1tGcoZVw7k7cnw3GKQRRs8E6DLTL6roMk5zdzRw3myh3YfgAVWkZi6m7yT5STER6W0tA=@proton.me' \
--to=alex9-ml@proton.me \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).