2 ms·

what about the best layout for writing code? usually you use a lot of characters that require 2 key press like (){}:"|<>?~$+...

by painted 10y ago

chinathrow 10y ago
This. And the Ctrl key so far away you easily overwork it.
- rpxx 10y ago
  Definitely swap the Ctrl and Caps Lock in your OS. Ctrl on the home row makes so much more sense for coding.
floatboth 10y ago
Any layout (I prefer colemak) – you can add cool tricks to make it better. http://stevelosh.com/blog/2012/10/a-modern-space-cadet/ http://stevelosh.com/blog/2012/10/a-modern-space-cadet/ introduced me to "CapsLock == Control AND Escape" and "Shifts as parens" tricks. I have them set up in Xorg: https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324951186b05a49c2de5d78ad0/x11/xinitrc#L45-L57 https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324... And Windows: https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324951186b05a49c2de5d78ad0/windows/keyboardstuff.ahk https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324...
iagooar 10y ago
Pro-tip: if you can get a gamer keyboard, often times they come with plenty of additional, customizable keys. Then, you just assign whatever character you are using a lot to them.
kutkloon7 10y ago
Very interesting question. I think programming is so suboptimal from what we could do, just by clinging onto the ASCII-based textfiles paradigm. Actually, autocompletion really slows me down sometimes too. For example, sometimes I type faster than I can watch what happens, and I press the up button to go up a line. Sometimes autocompletion decided to give me some options, and decides that the up button press is meant for that list, and refuses to let me go up. So I have to press left or right until my cursor is no longer in the token that is being autocompleted, and THEN I can finally go up/down a line. Very bothersome. Also, sometimes space works to select a autocompletion option, for other editors it has to be enter. Same thing with braces: I will type both of them eventually, but a lot of IDE's put one there immediately, which is very annoying if you don't anticipate. The whole thing makes coding inconsistent among multiple different editors; a bad case. IMO features should only be triggered by keys which do not have an essential function already.

what about the best layout for writing code? usually you use a lot of characters that require 2 key press like (){}:"|<>?~$+...

by painted 10y ago

what about the best layout for writing code? usually you use a lot of characters that require 2 key press like (){}:"|<>?~$+...

chinathrow 10y ago

This. And the Ctrl key so far away you easily overwork it.

rpxx 10y ago
Definitely swap the Ctrl and Caps Lock in your OS. Ctrl on the home row makes so much more sense for coding.

floatboth 10y ago

Any layout (I prefer colemak) – you can add cool tricks to make it better. http://stevelosh.com/blog/2012/10/a-modern-space-cadet/ http://stevelosh.com/blog/2012/10/a-modern-space-cadet/ introduced me to "CapsLock == Control AND Escape" and "Shifts as parens" tricks. I have them set up in Xorg: https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324951186b05a49c2de5d78ad0/x11/xinitrc#L45-L57 https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324... And Windows: https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324951186b05a49c2de5d78ad0/windows/keyboardstuff.ahk https://github.com/myfreeweb/dotfiles/blob/2a3008b27997b6324...

iagooar 10y ago

Pro-tip: if you can get a gamer keyboard, often times they come with plenty of additional, customizable keys. Then, you just assign whatever character you are using a lot to them.

kutkloon7 10y ago

Very interesting question. I think programming is so suboptimal from what we could do, just by clinging onto the ASCII-based textfiles paradigm. Actually, autocompletion really slows me down sometimes too. For example, sometimes I type faster than I can watch what happens, and I press the up button to go up a line. Sometimes autocompletion decided to give me some options, and decides that the up button press is meant for that list, and refuses to let me go up. So I have to press left or right until my cursor is no longer in the token that is being autocompleted, and THEN I can finally go up/down a line. Very bothersome. Also, sometimes space works to select a autocompletion option, for other editors it has to be enter. Same thing with braces: I will type both of them eventually, but a lot of IDE's put one there immediately, which is very annoying if you don't anticipate. The whole thing makes coding inconsistent among multiple different editors; a bad case. IMO features should only be triggered by keys which do not have an essential function already.