kanata VS svgbobrus

Gotta give a shoutout to kanata[1] which I have used daily for years at this point after giving up on QMK-powered keyboards.

QMK itself is great, but I was never able to find a non-columnar split ISO keyboard to use it with. Eventually I reluctantly settled on the Logitech K860[2] and I'm now happily using my favourite features from QMK with kanata at the software level.

[1]: https://github.com/jtroo/kanata

[2]: If I'm behind the times and there is now a QMK-compatible keyboard that looks like this, please let me know!

This is not in Emacs, but if I can't modify my keyboard's firmware (e.g on a laptop), I use Kanata https://github.com/jtroo/kanata. It works by creating a virtual keyboard in Linux (and uses a filter driver or process hooks in Windows), so it can work in any program as they just see a normal keyboard.

Besides the better caps word (by the way, you can have it in software in Win/Linux apps like https://github.com/jtroo/kanata/blob/main/docs/config.adoc#c...) you can also toggle capslock with e.g. a double tap while having on-hold functionality to the more useful Control, so you still wouldn't need to hold any modifier key

jtroo/kanata: Improve keyboard comfort and usability with advanced customization (github.com)

One particular approach that one might find it interesting is how the configuration is laid out (using S-expression from Lisps).

[0] https://github.com/jtroo/kanata/blob/main/docs/config.adoc

Kanata[0] is amazing. It support both Linux and Windows. But I'm yet to try it on windows because my majority work is on linux.

[0] https://github.com/jtroo/kanata

I recently had to draw some diagrams for documenting something. After looking at various Markdown-friendly options I landed on svgbob[1]. I believe it's a superior solution to these kinds of graph drawing tools for Markdown for one specific reason: the code is still readable. When I go to look at a Markdown file I don't always open the output. I will commonly open up a README file in Vim or just cat it to the terminal. In this case diagrams like those in this post is next to useless. I'm not going to read through some complex drawing definitions and try to visualise the results. With svgbob (or Typograms[2] or any of the other similar options) you can still read the Markdown text document and see the diagrams which is great!

Of course this comes with a tradeoff, drawing the diagrams can be a bit of a pain. But I believe this can be solved by a good Markdown editor or editor plugin. Alternatively a spec like this could be converted into an svgbob-compatible diagram.

[1]https://ivanceras.github.io/svgbob-editor/

Online playground svgbob-editor is also updated to use the latest version of svgbob. It is however a painfully slow to edit the diagrams from there, so it's better if you draw the diagram somwhere else and paste it to there.

There’s Svgbob. Plus when it comes to more complex diagrams or graphs where creating the ASCII art by hand in can be quite finicky, there’s a number of tools (including drawing tools) to make creating ASCII art much easier.

https://ivanceras.github.io/svgbob-editor/

svgbob

Since the post contains ASCII art, let me recommend you svgbob :)

The app can now render Svgbob code blocks (https://ivanceras.github.io/svgbob-editor).