Blog: 2023-08-07

Currently waiting on nushell to download, straight from cargo. Apparently it hasn't been packaged for debian/ubuntu, which is a bit surprising. That might be a worthwhile project, if nushell is any good.

Reading vim koans made me think maybe I'm barking up the wrong tree trying to replace tmux with vim. But I'm pretty tired of tmux, and generally environments that have a bespoke configuration language. And the command line interface of tmux is a bit wack. I tried at one point to make tmux automatically start, but canceled that for some reason, maybe having to do with tmux updates. Probably a tool I don't need.

Anyways that reminds me of the ideas I had which prompted me to blog:

• an old one from an April blog:

Idea: a spellchecker kinda thing that fixes common typos in a variety of places, like command line, email, text editor. Really just spellchecker that doesn't do things you don't want, like smart quotes

Much like lsp, it would be nice to have this functionality abstracted such that different environments could reuse the core logic of what replacements are to be done. I suppose a bunch of applications have a spelling corrections list, and this is even built in to MacOS. But I don't use macos much any more. Anyways it could be good, since a command line could implement typo fixes using abbrs, email web client using javascript, text editor using built in abbrs or something. But ideally the corrections would be stored in a single location. not a super high priority tho

Ok the other idea is this sort of tree of programming, where I document what depends on what, and then identify proprietary / suboptimal components I'd like to get rid of. Like

computing experience

hardware

 operating system
   desktop environment
   browser

programming language: c, make, python

python: depends on c

 package manager: pip, poetry
 web framework: django, flask

text editor: vim, emacs, neovim

and then rate the various components, thus understanding what is a solid foundation and what isn't