this
is very handy when you want to carry over some shared context. Justin Fagnani described this
as an implicit first argument, which is a model that helped me understand how to use it better.
Gefilte ficcionado | semitic HTML
this
is very handy when you want to carry over some shared context. Justin Fagnani described this
as an implicit first argument, which is a model that helped me understand how to use it better.
agreeing with krogoth - i use vscode via github’s web editor and other such buffoonery, and since many of my teammates also use microsoft’s loss-leader false-flag not-quite open-source community trojan editor, I have to stay reasonably current.
so i’m conversant, and use it, but i wouldn’t “switch” in the sense of “adopt as my daily driver”, for reasons which should be obvious from the last sentence ;)
" already means something though (leader to pick a register)
Try the which-key plugin, and/or make up silly stories for your bindings e.g. "you surround a word "
It depends on what your expectations are and how you see your relationship to your editor (sorry for the cringe anthropomorphism)
If you want to tinker and think of tweaking your editor as a hobby, then sure dive in
If your config already works and you don’t need the hassle, then don’t
In between? Want to use a specific lua plugin but don’t want to commit? You can do that too
It will be annoying for a minute but this change is good: it will help developers ship extensions faster and with fewer bugs by using standard JavaScript modules and IDE support. As mentioned in the blog: modules were standardized in 2015! At what point does it become acceptable to drop non-standard features?