I want to be able to use sly, but I particularly want to be able to use it in my vagrant machines.
sly-tramp seems to help with that. In order to use
slynk remotely, first, I need to initialize the correct version of the
slynk server remotely. The vagrant machines have the sly repository cloned to
~/sly and the following added to
(push #p"~/sly/slynk/" ASDF:*CENTRAL-REGISTRY*)
(slynk:create-server :port 4005) ; adjust this accordingly
I then activate the
sly-tramp-contrib add the following to
(setq sly-contribs '(sly-tramp))
When you’re working on a file or a document, it is important to save frequently in order to make sure you don’t lose your work. But code is complicated. The development of code is not linear — often edits are exploratory and end up being reverted. You find quickly that what you want to be able to save and explore is not the actual state of your files, but the sequence of edits you’ve made.
git saves your project as a sequence of edits to your code base rather than a set of file contents.
You have been writing code…
CS Professor, AI/NLP Researcher