

This looks … great.


This looks … great.
Ha. Lol. That’s bad
Context: this happens if you use patch(1) with patches generated by git format-patch. If you do, you should be using git am instead.


Lawndesk. Its not on play store, you have to download apk from github, but it does not have a drawer.
Every app is on the desktop, i organise them into folders and have a single home page with all the apps.


I wouldn’t call it state-of-the-art, but rather maybe most-straightforward or database-agnostic or as-simple-as-they-get


Yes. Highlighting, these selection actions and symbol detection all work with tree-sitter grammars. The whole premise of the editor is a modern-modal-editing with tree-sitter grammars.


I’m a bit surprised helix editor is not mentioned. It is based on tree-sitter grammars and allows for stuff like select-around-function or select-around-argument, to use grammar in the code navigation. Pretty wild and useful.
Have you erased the continuation of the message that is saying something about “similar names, but are actually two distinct types”?
It is a common error if you have two dependecies that export the same third dependency and your code makes an assumption that the versions of the third dep match.
All other languages either straight-up don’t support multiple versions of the same dep, or throw random errors at runtime. So this message is a consequence of rust supporting things that other langs only dream of.
Let’s say I manage an engineering department. How could I promote people who build simple software?