I would like to see a re-emergence of this keyboard design, with some added modern enhancements like function keys, command/control/option/etc. modifiers, and media keys.
Some programs from that era have keyboard shortcuts that were comfortably done on those ancient keyboards, but are unnatural enough to cause injuries on modern keyboards [1].
In practice I suspect this tends to manifest itself as hassle, as the user remaps their keyboard, rather than damage to the user's hands. At least I hope so.
Somewhat related: Long term Vi use has caused my standard right hand position to shift one key left. I don't even use hjkl that much anymore, but Vim (and probably more than a little nethack) have changed how I touch-type with QWERTY.
I don't have this issue with VI, but I do have that problem with FPS games that use the wasd keys -- I can only use them if I move my left hand to the left one key space. So I end up remapping those control keys one to the right, in games where that is possible.
The keyboards — the Japanese layout and the ADM-3A — are bit-paired, meaning that the characters on an unshifted and shifted key differ in exactly one bit in the ASCII encoding.
SP ! " # $ % & ' ( ) * + , - . /
0 1 2 3 4 5 6 7 8 9 : ; < = > ?
@ A B C D E F G H I J K L M N O
P Q R S T U V W X Y Z [ \ ] ^ _
` a b c d e f g h i j k l m n o
p q r s t u v w x y z { | } ~ DEL
Shift toggles bit 4 of the numeric and low punctuation keys (codes < 0x40), and bit 5 of the alphabetic and high punctuation keys. This made terminals easier and cheaper to build, in the days before cheap microprocessors, when encoding was done in discrete logic or, like the Teletype 33, mechanically.
HEAD~1 and HEAD^1 are equivalent, but HEAD~n and HEAD^n aren't.
HEAD~n means "the n-parent of HEAD, always choosing the first parent." So HEAD~3 means the first parent of the first parent of the first parent of HEAD.
HEAD^n means "the nth parent of head". git commits can have multiple parents if they are merges. So HEAD^3 means the third parent of HEAD.
As a result, HEAD~1 means "the first parent of HEAD" and HEAD^1 means "the first parent of HEAD", but the 1 means two completely different things.
I'd be more interested on why the control key was removed from the home row to help out those who where too lazy to use the shift key or macro a simple translit to their workflow: tr 'a-z' 'A-Z'
When the datamining show is over let me know. I'm in need of a well paying position and interested in moving out to california. I can teach shell automation, programming paradigms and productive workflow to eager learners new to the UNIX programming environment, hacking and building their own tools.
18 comments
[ 3.1 ms ] story [ 39.2 ms ] thread[1] http://en.wikipedia.org/wiki/Emacs#Emacs_pinky
Somewhat related: Long term Vi use has caused my standard right hand position to shift one key left. I don't even use hjkl that much anymore, but Vim (and probably more than a little nethack) have changed how I touch-type with QWERTY.
https://discussions.apple.com/servlet/JiveServlet/showImage/...
Early Japanese codepages put ¥ where ASCII has the backslash. Even today, on most (if not all) OSes render the \ as ¥ when using the Japanese locale.
Further reading: http://blogs.msdn.com/b/michkap/archive/2005/09/17/469941.as...
Installing South Korean games (this was middle school), I've always wondered why the paths were showing up as :
And trying to type \ in the installation path input box results in ₩HEAD~n means "the n-parent of HEAD, always choosing the first parent." So HEAD~3 means the first parent of the first parent of the first parent of HEAD.
HEAD^n means "the nth parent of head". git commits can have multiple parents if they are merges. So HEAD^3 means the third parent of HEAD.
As a result, HEAD~1 means "the first parent of HEAD" and HEAD^1 means "the first parent of HEAD", but the 1 means two completely different things.
The gitrevisions manpage is pretty mindblowing: https://www.kernel.org/pub/software/scm/git/docs/gitrevision...
When the datamining show is over let me know. I'm in need of a well paying position and interested in moving out to california. I can teach shell automation, programming paradigms and productive workflow to eager learners new to the UNIX programming environment, hacking and building their own tools.