When nargs=1 is given to argparse, it creates a list with one item, which is why
the additional [0] was needed when reading the value.
However, default='ask' means that the default value was 'ask' rather than
['ask'], causing the skin tone to be set to 'a', resulting in:
Traceback (most recent call last):
File "/usr/bin/rofimoji", line 1905, in <module>
emojis = compile_chosen_emojis(stdout.splitlines(), args.skin_tone[0])
File "/usr/bin/rofimoji", line 1870, in compile_chosen_emojis
emoji = select_skin_tone(emoji, skin_tone)
File "/usr/bin/rofimoji", line 1756, in select_skin_tone
return selected_emoji + fitzpatrick_modifiers_reversed[skin_tone]
KeyError: 'a'
Instead, don't pass nargs to argparse at all - with the default nargs value, we
just get the value (or default) back, so we don't need the [0] anymore.
Fixes #16

First, the classical typing, our companion since v1.0
Secondly, the new "Copy to clipbard, paste and then restore the
clipoard" to work around Firefox's problems. However, as `Ctrl+v` does
not work with a console (and thus Vim), I changed it to use
`Shift+Insert`. Unfortunately, this copies from both clipboard and
primary depending on the application. To work around this (yay,
recursive workarounds), we just spam both with our emoji and restore
them later. What could go wrong?
Also, we now allow choosing a method using cli args or different
keybindings (`Alt+p` for copypasting, `Alt+t` for typing).