This sounds similar to SLIME (and its fork SLY) for Common Lisp. These tools use their own protocols rather than LSP in part because they pre-date LSP but also because LSP is not a good match for everything they do. In addition to the usual LSP functionality like symbol lookup, xref and completion they also provide a very good Lisp REPL. It is easy to have the server side (called swank) running as part of an existing service which sounds a lot like what the post describes. For example I’ve used SLIME to connect to my live StumpWM sessions.

It shouldn’t as long as you make sure that the numeric uid/gid of your user account matches the one from the original system. If that’s not feasible then you can chown the tree.

I thought that slock was too complicated so I wrote a tiny one for myself in Go using xgb. Less than 100 lines and pretty straightforward but it makes some assumption about my personal setup so not public.

Not worried at all, I’ve moved on many years ago.

Why bother with either of those for private personal repos though? Why not just regular remote repos over ssh?

When you have a goose that produces a reliable daily supply of golden eggs do you:

1. keep collecting your daily egg
   or
2. see if giving it a good kick or two gets you more eggs

For me “scratch your own itch” is what works best for keeping up the motivation. Think of a tool or service that you’ll actually want to use yourself and implement that in the language you are learning. Or create a better version of an existing tool that you regularly use.

EXWM. I am a longtime Emacs user so merging the concepts of Emacs buffers and X windows is a huge benefit. Only one set of keybindings to worry about, all of my Emacs window management stuff works for X windows too. One less external dependency to worry about too. In a new environment (like when starting a new job etc) as long as I have my Emacs config I am good to go.