kinto VS Vim

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 have a project called Toshy that finally brings Mac-like keyboard shortcuts to KDE Plasma desktops using a Wayland session. It's based on a project called Kinto, by Ben Reaves (https://kinto.sh). As of now, Kinto works only on X11/Xorg sessions. This is due to its use of the xkeysnail keymapper, which has no Wayland support. It is totally reliant on Xlib.

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?

For Mac switchers, check out https://github.com/rbreaves/kinto

Another option is https://kinto.sh . It worked perfectly for me out of the box on Pop OS, and with a few tweaks to shortcuts I’m pretty happy with the experience to the point where I can fairly seamlessly switch between computers and not be driven crazy by the shortcuts.

There have been six releases of Vim _this week_. So, no, Vim is not "dead".

https://github.com/vim/vim/tags

Vim

We wanted this machine to be as lean as possible. There is only so much memory and processing power to go around. Remember, our machine has 3 GHz Dual-Core Intel Core i7 processor with 16 GB 1600 MHz DDR3 memory. We also wanted as much of that space and power to be used for serving up our web applications. However, we also wanted to have an additional option for editing any code files, in addition to vim.

Vim: winget install vim.vim

So Raylib library could be your best option. Let's code, just open your text editor like vim or VSCodium in your Windows, Linux or Mac computer and let's build our indie game with Raylib library, no extra dependencies are needed.

When you said Vim, I thought you were talking about Vim (a code editor). Clearly not haha

Let’s get to it! To create your service file, you can use Vim (if you enjoy a challenge) or Nano as your editor, and I will be using Nano. Thank you and God bless 🙏🏿. So to create your service file in the appropriate directory, you will execute the command

When you use NeoVim/Vim, you should type :next after :w (save) in order to switch files.

I used to be a pretty heavy Vim user (RIP Bram), but when I started doing a lot of remote pairing with less experienced devs I realised that they were sometimes having trouble following along when I was driving. Their experience was basically "click click click" some text whizzes around the screen.

From what I can tell the reason is that that’s the way it was always done. As I understand it, back in the days before there were distributed version control systems, Bram was the only one who could commit to the code-base so he would credit the actual author of a submitted patch in the commit message. He continued this practice after the Vim project moved to Mercurial (and Git).

Related discussion: https://github.com/vim/vim/issues/1554