kinto VS vim-clutch

If you like macOS keyboard shortcuts, I recommend you checkout Kinto go Windows and Linux. On Windows, Kinto used AHK

https://kinto.sh

However, at least when I set it up Kinto did not provide switching windows I’m this fashion. Here is the script I use.

```

    ; BRING FORWARD ALL WINDOWS OF THE CURRENT APPLICATION

The project was based on another project that's been around for a few years called Kinto, by Ben Reaves, which notably also has a Windows version (https://kinto.sh) using AutoHotkey. But has no Wayland support (at this time) in its Linux version.

Toshy is based on Kinto.sh, by Ben Reaves (https://kinto.sh or https://github.com/rbreaves/kinto). Kinto is basically an extensive keymapper config that not only shifts modifier keys appropriately for different keyboard types, but has full keymaps for a number of different apps like VSCode. My variant of Kinto adds some features and utilities for managing the services that make it work, and tools like a script to change the function keys mode of any keyboard that uses hid_apple. That means MacBook keyboards mostly, but also some non-Apple keyboards with media keys apparently use that driver module.

I don’t know if you can activate it via a keyboard shortcut, but I use Kinto.sh to swap keys on my MacBooks.

Hello, there's an open issue about this in their repo: https://github.com/rbreaves/kinto/issues/772

There is a setting in keyboard preferences for that.However if you can get yourself used to macOS shortcuts I highly recommend doing so as they seem to be superior especially if you are a programmer and use the terminal a lot, as on macOS you can simply use Command+C to copy from a terminal and Ctrl+C still works for sending SIGINT. Also Command+, will open preferences for almost every application on macOS. Shortcuts on macOS are very consistent across many apps unlike on Linux or Windows. After you get your Linux laptop back you can continue using these shortcuts thanks to a tool called kinto.sh.

Tangential: I'm currently looking for a way to map Mac-style shortcuts on Linux (e. g. Meta + C/V for copy / paste). The only thing I know is https://kinto.sh/, but it looks a bit too janky to my taste. Any other ideas?

And nothing about installing my https://kinto.sh app?

You mean something like this?

https://github.com/alevchuk/vim-clutch

Just wait until someone shows him vim-clutch.

Une pédale d'embrayage pour vim: https://github.com/alevchuk/vim-clutch

I used the same idea when setting up long-range WiFi (couple of KMs) via antenna for a mesh network.

In order to get the best latency/bandwidth, you need to point the antennas with precision at each other, and in order to know if you're pointing it right, you need to run some tool on a display at the same time, like `ping`, and see when it gets lower when you're pointing it right.

So rather than having to look with one eye towards the horizon, and one eye on a screen to see a tiny number (which I found impossible), I made a quick script that outputs a beep each time ping returns output, with the frequency being higher when the latency got lower. So now I could focus solely on the horizon while using my ears to hear if I was getting in the right direction.

Lots of fun, super useful and makes me wonder (just like you) what other tooling we could use more senses with, rather than just our eyes.

Similar vain: the vim foot pedal: https://github.com/alevchuk/vim-clutch

Im thinking about an improvement, where instead of pressing modifier keys, you simply use 2 vim clutches one for the row above and one for the one below

About two weeks ago, I posted a picture here about a vim clutch (a.k.a. vim pedal) that I got as a present from a friend. Its function is very simple: when you press the pedal, it types i and takes you to insert mode. When you release it, it types ESC and you are back in normal mode. Under the post, fellow redditors started to discuss whether it makes sense for the pedal to type i? Most people were guessing that o and a would be used much more often. I thought, "hey, why don't I just measure it for a couple of days and create statistics about it?"