I'm actually pretty interested in the project and will definitely take a look into it when I next set up a Linux desktop for whatever reason. That said, I'm only interested in it because I had to spend a lot of effort to figure out exactly what it would be useful for.
> I prioritized the info to make it a little faster to get up and running versus the need to scroll past an ever increasingly long ToC. For the most part people shouldn't really need to read something a mile long to get it up and running.
This is fair! But I don't want to "get set up and running" on something I've never heard of and don't know what it's going to do. I still don't understand why it says "copy and paste with all apps and terminals"... is it because you can copy and paste with a keyboard shortcut?
> is it because you can copy and paste with a keyboard shortcut?
To be honest the genesis of Kinto came from my Dell XPS 13 Developer Edition days in 2016 - I was wanting to make Ubuntu my primary OS, but I was highly annoyed by 2 things.
1) Copying and pasting btwn the general GUI apps and the terminal had inconsistent hotkeys because of the need to hold down shift on the terminals. That has always stuck w/ me and I have never liked the need to carry or backup dotfiles around for hotkey configurations of individual apps or being forced into creating a global, always on, hotkey (aka xmodmap, setxkbmap, etc). Autokey was also not good enough & my early python based attempts at context switching was far from what it needed to be.
2) The Dell XPS 13 had a hardware level bug that would cause the kernel on either Linux or macOS to halt the system randomly. I reported it to the community & as far as I know that bug still exists to this day. Only Windows would ignore it, so I sold it and bought another macbook pro after that.
You have to understand that I decided to commit 100% to the macOS keyboard layout in 2012 - up until then I had been switching back and forth btwn Windows, macOS and Linux distros, but I wanted to get a lot more serious about programming and it felt like too much additional mental overhead to keep changing that gear, especially as I was learning new keymaps in code editors that were not consistent btwn OS's. I also committed for ergonomic reasons and the how the terminal behaved.
Back then Apple was still making fairly good decisions and updates to their OS unlike how I feel about that platform in the last few years.
Kinto is just a culmination of an itch I've had for a very long time - it's just I've been extra motivated to scratch it in the last 2-3 years and it's really come together pretty well in the last several months. It's literally the program I wish had always existed for Linux and the one I wouldn't have had to write in the first place lol.
> I prioritized the info to make it a little faster to get up and running versus the need to scroll past an ever increasingly long ToC. For the most part people shouldn't really need to read something a mile long to get it up and running.
This is fair! But I don't want to "get set up and running" on something I've never heard of and don't know what it's going to do. I still don't understand why it says "copy and paste with all apps and terminals"... is it because you can copy and paste with a keyboard shortcut?