You are not logged in.
For the console:
/etc/vconsole.conf
----
KEYMAP=dvorak
For X Session:
.xinitrc
----
setxkbmap -layout us -variant dvorak &
For the console, it applies the dvorak layout to a firmware dvorak
keyboard, messing up the input.
When starting the X Session, I have to re-plug the keyboard in order for
it to function properly.
Re-plugging in console has no effect.
How do I prevent these configurations from affecting the external
keyboard?
OR
How do I restrict these configurations to only affecting the internal
laptop keyboard?
Offline
You rather don't w/ setxkbmap (and that's a clumsy way to persistently configure the keyboard anyway) and I doubt that the console can discrimintate outputs this way.
https://wiki.archlinux.org/title/Xorg/K … tion_files - you can match product and vendor to limit the impact, https://man.archlinux.org/man/extra/xor … SS_SECTION
Online
Thanks for the answer. I'm having trouble understanding the first part. Is that a typo? "You rather don't w/?"
Offline
w/: "with"
w/o: "without"
Online
That was not the part tripping me up. It was the grammar. "You rather don't with setxkbdmap... and I doubt." I'll read this as "You can't with setxkbdmap."
You're suggestion promises to tighten up my X Session persistent configuration, but the console is where I have no workaround. Even with these settings in an X Session, I can replug the keyboard and type properly. From the console, my only recourse is to resort to the built-in laptop keyboard.
Offline
for clarity :
Do the laptop keyboard and your external keyboard use the same layout ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I'm pretty sure the OP has two keyboards they want to use w/ a dvorak layout, but one has a regular qwerty layout, the other one has the dvorak layout in hardware (or firmware, but that's an irrelevant detail)
Online