For example, the philosophy of xah-fly-keys is to put the most frequently used commands on the most comfortable key positions. That said, I think personalization is more important with regards to key sequence length than with to key position. more than 2 keys for one-off actions is undesirable), and the most comfortable keys should be used for the most frequently used actions. The fewest number of keys possible should be used to perform all actions (e.g. Some may prefer to use modal editing only for consecutive, contextual, and/or composable editing commands and to instead consistently use modifiers regardless of mode/state when prefix keys become necessary to group one-off actions. for a find-file equivalent), this doesn’t matter too much in practice since I am always in normal state If I am not typing, making the ESC unnecessary. Although ESC SPC f is longer than C-SPC f (e.g. For example, I use modal keybindings for file/buffer/window/workgroup management keybindings in emacs even though these are one-off actions. when prefix keys become necessary because there are not enough + combinations available for some type of action, I prefer modal prefix keys). I use modifiers for the most frequently used one-off commands but generally use modal prefix keys over modified prefix keys (i.e. window management, basic line navigation, pasting at the cursor, deleting the previous word after mistyping a word, etc.). vim-arpeggio and key-chord or dual-role keys), and thumb modifiers (best method when possible) should be preferred for one-off commands/actions (e.g. Modal editing should be preferred any time non-text-insertion commands/actions are taken consecutively and repeatedly as it saves keypresses and allows for differentiating between different modes or types of actions. Similarly, modifier keys should be re-arranged and put into the most comfortable locations. parentheses, brackets, and programming operators) and keys like backspace and enter should be remapped or put on a layer based on their frequency of use. Time shouldn’t be wasted switching to and using the mouse. Navigation of any sort (window, file, etc.) should be quick and not get in the way of the task at hand. Sessions should be automatically saved and set up. The most frequently used programs should be opened automatically and bound to a key instead of opened with a launcher. Human-editable configuration files prevent the need to ever configure programs with a mouse/GUI, and keeping these files in a central location allows for better organization and easier backups (which should be performed regularly as well as automatic snapshots). My philosophy when choosing software is to pick customizable, keyboard-friendly programs that are configured in plain text. The goals for my workflow are to achieve speed and efficiency, cut wasted time and movement, and eliminate hand, pinky, and wrist pain. See aesthetics/ for more info on theming, panels, etc. Create a Modal Interface for Programs That Don’t Support Rebinding.Block Layout in Emacs/Vim and Examples of Context-dependent Keybindings.Use Ranger/Dired Instead of Default GUI Popup for File Saving.Make Any Terminal Emulator Dropdown Regardless of WM.Configuration Management/ Installation Automation.On Rodent Extermination (Why the Keyboard? Why Vim?).stevep99’s Colemak Mod-DH (Dvbg/Hm swap).I’ll eventually add my notes on vim, emacs, and text editing here and my notes on keyboards, keyboard layouts, and keybindings/remappings here. Here are some notes on browser-related software (e.g. I have some notes on software related to aesthetics (e.g. That said, if you have any comments, questions, or suggestions regarding this repo, feel free to make an issue. I move any scripts that become significant/generally useful from my dotfiles into their own repos (e.g. I’ve had alter my bspwm configuration for most updates), so I’d advise against copying anything without first testing it. However, the state of this repository is generally not up-to-date with my actual configuration, older config files may be a mess, and my actual configuration may have bugs, organization issues, or only work with a specific version of the relevant program (e.g. Most newer config files are consistently formatted (org-style headings/outline) and well-commented. If you are interested in keyboard-based programs (tui, cli, vim-inspired programs, emacs, etc.), keyboard ergonomics, Colemak, etc., this repo may be of some use.
0 Comments
Leave a Reply. |