Adapting Keyboard & Software

I think I’ll just karate-chop the Ctrl keys instead of keeping the left swapped with Caps Lock and swapping the right with something else. Vim’s movement keys aren’t exactly intuitive either: four keys in a line—the left two go up and down; why couldn’t the I and M buttons be up and down, J and K left and right? Another thing that Emacs had against it was its term mode: anything blue was illegible. Except for Cygwin, I could make directories cyan, but output would stay blue and unintelligible. I found this solution: (setq ansi-term-color-vector [unspecified "black" "red3" "lime green" "yellow3" "DeepSkyBlue3" "magenta3" "cyan3" "white"]). That’s also necessary for 24’s tsdh-dark theme.

The industry should encourage Dvorak for new computer users, but that would obviously present a problem for those users when they use most other computers. There hasn’t been enough study on Dvorak and QWERTY to justify a shift, but surely a keyboard designed to slow down typists (QWERTY) should have began phasing out a few decades ago. Split keyboards should become another standard.

GNU Screen for Cygwin and BASh

# ~/.bashrc

# screen Cannot find terminfo entry for 'eterm-color'.
if [ "$TERM" = "eterm-color" ] ; then
 TERM="vt100"
fi

# Start screen at login
[[ $TERM != "screen" ]] && exec screen

# screen Login greeting ------------------
if [ "$TERM" = "screen" -a ! "$SHOWED_SCREEN_MESSAGE" = "true" ]; then
  detached_screens=`screen -list | grep Detached`
  if [ ! -z "$detached_screens" ]; then
    echo "+---------------------------------------+"
    echo "| Detached screens are available:       |"
    echo "$detached_screens"
    echo "+---------------------------------------+"
  else
    echo "[ screen is activated ]"
  fi
  export SHOWED_SCREEN_MESSAGE="true"
fi