The first 2 points can be relatively straightforward to implement. These are developer tools which are not required for Vim mode and therefore will not be installed with ti-vim. Karabiner is a relatively heavy package, including cumbersome apps like PreferencesWindow, NotificationWindow and EventViewer. Enthusiasts have created different complex modifications, including Vim modes, from which a suitable one can be imported into the app. Karabiner needs to be installed to enable remapping of keystrokes. Thirdly, this app and the keystrokes need to be connected.
Secondly, an app needs to be created that displays the Vim modes. To create a fast and robust experience, first the keystrokes need to be mapped into ones that simulate Vim behaviour. There needs to be a system wide Vim mode. These two separate environments create a problem where the developer needs to use different code editing systems in Vim and MacOS. Vim is also fast, does not require the use of mouse, and has convenient arrow keys on the home row – hjkl.
However, when SSH-ing into another computer, there is no visual editor, and Vim needs to be used. When using a code editor in MacOS, the developer alters the caret position with Alt + →↑↓ ←.
As a result of these concepts arose the idea of a system-wide Vim mode. Besides this I understood the benefits of using Vim: It is fast and can be used in most Unix distributions. With that came the understanding of Karabiner, which allows the remapping of keyboard keystrokes. I got interested in workflow automations a while ago.
0 kommentar(er)
