@imsnif making a very convincing argument for using the terminal in 2023 at @rustlab. A great talk in general and I learned some things about how terminals work that I never knew before!
Was looking into understand why everyone talks about neovim instead of vim and found myself trying Helix and … wow out of the box I learned more how to use a vim-like editor than in one year on vim ???
@tournesol#Helix has everything I needed from my many #Neovim plugins but out of the box and MUCH better integrated!
Who thought that needing multiple plugins in a "modern" editor for simple completions is a good idea?
Anyway, I highly recommend trying out Helix for at least a week to be able to adapt the muscle memory. You get a very powerful workspace, especially if you pair it with #Zellij and #GitUI 🚀
This has been a much requested feature for a long time. This would make #zellij sessions persist across reboots.
When starting Zellij, we'll have the option to resurrect sessions from previous reboots, including all open tabs, panes and commands running within those panes.
Monocle is a #zellij#rustlang plugin for fuzzy-finding file names and their contents.
It can open files in your $EDITOR - directed to the right line - in floating or tiled panes at your choosing.
It can open #terminal panes to the location of files in floating / tiled panes at your choosing.
It ignores hidden files and respects your .gitignore.
Here we see a demonstration of plugin workers (our built-in workaround for threads). We see the Strider plugin searching the file system (both file names and their contents), rendering in real time and offloading the search itself to the background worker.
When we select a search result, Strider will open it for us in a new pane with our default editor (#vim in my case) to the correct line if relevant.
More plugin system updates for #zellij. I'm about to merge a PR (https://github.com/zellij-org/zellij/pull/2410) that makes plugin updates and renders asynchronous. This is in addition to the recent PR that made them load asynchronously.
This opens the door for headless "background worker" plugins/instances that will address the issue of not being able to use threads in #wasm since they're still unstable.
Next up: thinking up an API for this and implementing fuzzy file name/contents search with it in Strider.