On 10.04.18 12:51, KatolaZ wrote: > On Tue, Apr 10, 2018 at 09:12:13PM +1000, Erik Christiansen wrote: > > Not many issues with devuan_ascii_2.0.0-beta_i386_NETINST, but for the > > moment I have to hit '@' for '"' and '"' for '@'. That's on a Logitech > > cordless keyboard. > > > > OK, for myself, I can remap them in ~/.Xmodmap, but is a more general > > fix called for? > > > > You just need to use the right keymap (it looks like you are using a > US keymap on a UK keyboard or vice-versa). I guess the setting depends > on your desktop environment of choice. > > If you don't use a DE, instead, setxkbmap should probably do the trick > for X. > > For virtual consoles (i.e., if you don't use X), loadkeys is the > key. But in most cases it is sufficient (and easier) to > "dpkg-reconfigure console-data".
As indicated by the "~/.Xmodmap", I do use X. Curiously, $ dpkg -L console-data # told me that console-data was not installed. After an "apt-get update" and install of console-data, I tried "dpkg-reconfigure console-data" a couple of times, in turn trying US and British keyboards, but neither fixed the scrambled keys. I see now that "|" gives "~" in addition to the miscoding described above, which remains constant for all maps tried so far. If there's some way to guess what map a Logitech wireless keyboard needs, it'd be really useful. Here in Australia, keyboards tend to be US or maybe US-international, whatever that is. (Found in the full list, option 4 in "dpkg-reconfigure console-data" dialogue) Erik _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng