this article suggests shell allowed, but git also has a built-in feature for aliases itself. I prefer these as it allows you to keep using the git command normally (more consistent when you tend to use history search/auto-suggestions heavily).
running git config --global alias.st status, for example, will allow you to run git st as an alias for typing out the full git status (you can also manually add aliases to your ~/.gitconfig).
not sure about escape sequences just yet, but Kitty gives you insane control over font rendering https://sw.kovidgoyal.net/kitty/conf/#fonts
Short, simple, informative, and helpful. 10/10
zsh has ctrl-r as well; this feature is specifically for beginning-of-match and some find it a bit more ergonomic.
I’m struggling to see how bug reports found using this prediction approach would ever be sent as anything but bugs of the predictive debugger itself.
how would end-users ever see bugs caused by a debugger the devs use? how would users of a third-party library conflate bugs in their own code/the third-party code when you can see which lines are which as you debug?
it’s so useful! I used to have some terrible setup going with branches for different OSes in my dotfiles, and chezmoi really simplified the whole thing
https://www.chezmoi.io/ if you’ve got some complexity with your setup. otherwise, could be overkill.
Great article. there was a even a response a year later https://medium.com/front-end-weekly/how-it-feels-to-learn-javascript-in-2017-a934b801fbe
to add to the other comments: I half-switched a while back, wrote a couple of my files in lua. since you can still source lua files from within vim, so I did that until I switched everything over later. it made it easier to do it that way if you already have a lot of config and don’t want to spend a lot of time up-front to learn it
haven’t tried it myself, but I’ve heard https://earthly.dev/ is supposed to address the execute locally problem