4 ms·

> So you use your most used key with a sidewise motion of your weakest finger of your weakest hand? I'll clarify that for you, my most used individual key. Mos

> So you use your most used key with a sidewise motion of your weakest finger of your weakest hand? I'll clarify that for you, my most used individual key. Most of my typing is on the home row. > and that's what's wrong with the native keybindings - they are simply awful ergonomically You asked for a way to bind the keys, you got one. Now all of a sudden your problem is that the default keybindings not being ergonomical. I use vim keys EVERYWHERE to help my RSI, but to each their own. > There are ways to avoid any latency/typing sideffects, but as far as I know that is only possible by eschewing the "but functionally it should act like the terminal UI" maxim, hence the original question whether any GUI app is ready to break off the rusted chains This makes zero sense. My point is that there is no native way to bind hold. The latency comes from vim waiting for either a second keypress to run the binding, or typing the character. You can natively set the delay lower and I do in :termdebug, but when typing it's very noticeable at my typing speeds. You could write a plugin and one probably even exists if you want that functionality. But please, explain how a GUI would solve that in a way a TUI can't. Very curious to hear what you come up with.

eviks 3y ago
> my most used individual key I'll clarify that for you: this is still a big ergonomic issue typing notwithstanding > You asked for a way to bind the keys, you got one. No, I asked for a specific way to bind keys, and got nothing ("except for holding a key") and another JK nothing you yourself don't like >Now all of a sudden your problem is that the default keybindings not being ergonomical. There is nothing sudden about it, it was you who asked what's wrong with the defaults. > I use vim keys EVERYWHERE to help my RSI, but to each their own. That's not true since the vast majority of those aren't supported everywhere, but also irrelevant - I use better keys everywhere, so? > This makes zero sense. My point is that there is no native way to bind hold. That's why you don't get it. Binding hold/modtaps is what allows avoiding the latency etc. > The latency comes from vim waiting for either a second keypress to run the binding, or typing the character Even in this case of two taps (not what I mentioned) there is no need for a wait, you can type right away and perfectly clean up later if the 2nd key is a combo. Neovintageous plugin for Sublime does this > You can natively set the delay lower and I do in :termdebug, but when typing it's very noticeable at my typing speeds. I don't want just the delays, that's a failed branch of key chord evolution, delays can't be perfect. I've described what I want in the very first comment > But please, explain how a GUI would solve that in a way a TUI can't. Very curious to hear what you come up with. By having access to all keyboard event info, not being limited by the terminal, and handling that properly. Check out kanata or google modtaps and home row mods, don't remember a link with a great description.
- worksonmine 3y ago
  > I'll clarify that for you: this is still a big ergonomic issue typing notwithstanding > That's why you don't get it. Binding hold/modtaps is what allows avoiding the latency etc. Modkeys are how Emacs does it, but have you ever heard of Emacs pinky? Why do Emacs users swap control and escape? To me chords and modal editors are the solution. My way solved my RSI, it's definitely more ergonomic than the finger gymnastics I need with modifiers. > That's not true since the vast majority of those aren't supported everywhere, but also irrelevant - I use better keys everywhere, so? Use vimium in chromium, vimium-ff in firefox. Vibreoffice for LibreOffice, adding 'set editing-mode vi' in ~/.inputrc sets it for pretty much every TUI program such as gdb, sqlite, psql and so on. My window manager dwm has vim keys, neomutt for mail, newsboat for rss. For rofi and dmenu I set them manually to follow the same pattern. And the list goes on, what do you mean? Everything works exactly as expected and is intuitive to me. Anyway, in your first comment you ask: > Is there any complicated no-nonsense GUI for Neovim that transcends the GarbageUI of the terminals and, for example, allows you to have advanced keybinds to invoke various vim actions (like enter insert mode on tap I and exit it on hold I or modtap J+I) The answer is yes, just use the vim way of binding the keys? The problems you mention are invented and have nothing to do with a GUI. What does a GUI even have to do with the keyboard? What am I missing, it's still unclear and I'm confused? If you like mods just bind mods, vim supports it and I bind ctrl+p to fzf. What is even the problem? Explain it to me in a simple way don't ask me to search for what you try to say. If you don't like neovim, or the terminal, just use VsCode like everyone else? Who's forcing you to live with something that pisses you off so much?
  - eviks 3y ago
    Modtap isn't modkeys, seriously, just google, I know you're confused, and since you keep ignoring what I write or replace my words with your wrong ones, my simple words won't help alleviate your confusion (also ironic mention of emacs pinky when you're using pinky for one of the most frequent commands) > Vimium in chromium So what's your Vimium command to scroll down by two paragraphs and then select the next two sentences? > The answer is yes That wasn't a yes or no question If you like neovim and the terminal so much, just stay there and ignore this GUI topic, who is forcing you to avoid the light of knowledge at the end of the Google tunnel to insist there is no problem just because you can't see it? > Vim supports mods So how do you bind left control p to run one command, and right control p to run another? (hint: this limitation is also terminal-related)

eviks 3y ago

> my most used individual key I'll clarify that for you: this is still a big ergonomic issue typing notwithstanding > You asked for a way to bind the keys, you got one. No, I asked for a specific way to bind keys, and got nothing ("except for holding a key") and another JK nothing you yourself don't like >Now all of a sudden your problem is that the default keybindings not being ergonomical. There is nothing sudden about it, it was you who asked what's wrong with the defaults. > I use vim keys EVERYWHERE to help my RSI, but to each their own. That's not true since the vast majority of those aren't supported everywhere, but also irrelevant - I use better keys everywhere, so? > This makes zero sense. My point is that there is no native way to bind hold. That's why you don't get it. Binding hold/modtaps is what allows avoiding the latency etc. > The latency comes from vim waiting for either a second keypress to run the binding, or typing the character Even in this case of two taps (not what I mentioned) there is no need for a wait, you can type right away and perfectly clean up later if the 2nd key is a combo. Neovintageous plugin for Sublime does this > You can natively set the delay lower and I do in :termdebug, but when typing it's very noticeable at my typing speeds. I don't want just the delays, that's a failed branch of key chord evolution, delays can't be perfect. I've described what I want in the very first comment > But please, explain how a GUI would solve that in a way a TUI can't. Very curious to hear what you come up with. By having access to all keyboard event info, not being limited by the terminal, and handling that properly. Check out kanata or google modtaps and home row mods, don't remember a link with a great description.

worksonmine 3y ago
> I'll clarify that for you: this is still a big ergonomic issue typing notwithstanding > That's why you don't get it. Binding hold/modtaps is what allows avoiding the latency etc. Modkeys are how Emacs does it, but have you ever heard of Emacs pinky? Why do Emacs users swap control and escape? To me chords and modal editors are the solution. My way solved my RSI, it's definitely more ergonomic than the finger gymnastics I need with modifiers. > That's not true since the vast majority of those aren't supported everywhere, but also irrelevant - I use better keys everywhere, so? Use vimium in chromium, vimium-ff in firefox. Vibreoffice for LibreOffice, adding 'set editing-mode vi' in ~/.inputrc sets it for pretty much every TUI program such as gdb, sqlite, psql and so on. My window manager dwm has vim keys, neomutt for mail, newsboat for rss. For rofi and dmenu I set them manually to follow the same pattern. And the list goes on, what do you mean? Everything works exactly as expected and is intuitive to me. Anyway, in your first comment you ask: > Is there any complicated no-nonsense GUI for Neovim that transcends the GarbageUI of the terminals and, for example, allows you to have advanced keybinds to invoke various vim actions (like enter insert mode on tap I and exit it on hold I or modtap J+I) The answer is yes, just use the vim way of binding the keys? The problems you mention are invented and have nothing to do with a GUI. What does a GUI even have to do with the keyboard? What am I missing, it's still unclear and I'm confused? If you like mods just bind mods, vim supports it and I bind ctrl+p to fzf. What is even the problem? Explain it to me in a simple way don't ask me to search for what you try to say. If you don't like neovim, or the terminal, just use VsCode like everyone else? Who's forcing you to live with something that pisses you off so much?
- eviks 3y ago
  Modtap isn't modkeys, seriously, just google, I know you're confused, and since you keep ignoring what I write or replace my words with your wrong ones, my simple words won't help alleviate your confusion (also ironic mention of emacs pinky when you're using pinky for one of the most frequent commands) > Vimium in chromium So what's your Vimium command to scroll down by two paragraphs and then select the next two sentences? > The answer is yes That wasn't a yes or no question If you like neovim and the terminal so much, just stay there and ignore this GUI topic, who is forcing you to avoid the light of knowledge at the end of the Google tunnel to insist there is no problem just because you can't see it? > Vim supports mods So how do you bind left control p to run one command, and right control p to run another? (hint: this limitation is also terminal-related)