search

rey / computer

A reproducible and lightweight desktop environment to run on Ubuntu.
0 stars 1 forks source link

keyboard configuration - should add instructions or setup step? #5

Open cenau opened 8 years ago

cenau commented 8 years ago

Since the readme encourages use via vm/vagrant, it might be important to help users set up their keyboard on first boot.

ie, I couldn't use ~ ( tilde), meaning the instructions in the readme were impossible to type as is.

Suggest a) launch dpkg-reconfigure keyboard-configuration as part of provisioning or b) include keyboard setup instructions in the readme

NB To get a working keyboard on a british macbook air, I had to do:

sudo dpkg-reconfigure keyboard-configuration

Then chose 'macintosh' and 'UK' and mashed 'OK' through the defaults

rey commented 8 years ago

ie, I couldn't use ~ ( tilde), meaning the instructions in the readme were impossible to type as is.

I wonder why this was? Was it because the keyboard in i3 was set to US? Something else?

It's not related to the Vagrant build I've been hacking on keyboard fixes this evening and had added a line to the config to explicitly say to use a GB keyboard but ended up removing it as it was gnome-settings-daemon that I'd installed previously on the Lenovo machine.

If you vagrant ssh from your host machine you can just copy and paste mkdir ~/computer && cp -r /vagrant/* ~/computer/. && cd ~/computer && source install.sh before running startx from the GUI window :)

I'll revisit the wording because it could be clearer.

rey commented 8 years ago

If you do a setxkbmap -query what is the output?

cenau commented 8 years ago

didnt know about vagrant ssh!

I wonder why this was

I think the keymap its set up for just doesnt correspond to all the keys on the host system ( in this case, a mac) - nothing to do with i3 or x.

If you do a setxkbmap -query what is the output? well, nothing before I do startx... :-)

in a term in an x session tho i get rules: evdev model: pc105 layout: us

which tallies with cat /etc/default/keyboard

# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

The keyboard is defaulting to a US 105 key, which is fine, but for portability it might be useful to add keyboard options to the setup? OR just something in the readme maybe...similar to the notes for the lenovo?

also, realised from doing vagrant ssh that the box doesn't seem to have any locales (except US) loaded:

-bash: warning: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8)