31–40 of 43 posts
It feels wierd to write this as im stumbled how so many people prefer video content over text. But I would like a video to see how this looks like in practice.
Vlime README has a terminal session recording that provides a quick demo of the plugin: https://github.com/l04m33/vlime#readme.
I wonder why the author doesn't mention the plugin vim-slime[1], given that it seems to be more popular than either Slimv or Vlime on github. From what I can gather, Slimv and Vlime are more focused on lisp with built-in completion and debugging whereas vim-slime is language agnostic and simply recreates just the "connected REPL" behavior of Slime. [1] https://github.com/jpalardy/vim-slime
The "vim-slime" plugin is not appropriate for my blog post because it is nothing like SLIME. In fact, the word "slime" in "vim-slime" is poorly chosen. It supports none of the SLIME features. It does not even provide the "connected REPL" experience like SLIME, Slimv, or Vlime does. Here are the major reasons why vim-slime is very limited and insufficient as a Lisp development environment when compared to SLIME, Slimv…
Two questions: With the advent of capable editors like Visual Studio Code, is Vim still a relevant skill to have? Is SLIME still the state of the art for Lisp development environment? Is there no way to get started with Lisp programming without having to learn Emacs or Vim?
I have no idea why you were downvoted for your questions. Weird. I will try to answer your questions: One killer application of Vim and Emacs is development on powerful remote servers, for example, you might want 16 cores, a powerful GPU, and 64gig memory for a task so remote exploration and development makes sense. (VSCode does have a remote mode but I haven’t tried it.) I have been using Emacs for 20+ years with Li…
Earlier quoted context omitted.
SLIME has a successor now called Sly, but yes that's still state of the art for Lisp programming. No, you don't have to learn emacs to get started with Lisp though. You'll just have an inferior experience. As a side note, if you do start to learn without emacs, please use something like this[1] for formatting your code. Most editors lack a Lisp indentation plugin, and any time you ask a question online, whomever answ…
I don't think it's fair to call it a successor since it intentionally doesn't implement all the features of Slime. I'm specifically talking about presentations which were removed because the author of Sly never uses them. For the first people who do, however, Sly can never be a successor to Slime. It may be an alternative, and a pretty good one, but not enough a successor.
Two questions: With the advent of capable editors like Visual Studio Code, is Vim still a relevant skill to have? Is SLIME still the state of the art for Lisp development environment? Is there no way to get started with Lisp programming without having to learn Emacs or Vim?
Here's one maybe-reason and one definitely-reason VSCode cannot replace vim for me: 1) Logs are often compressed. Can VSCode open .gz files? Vim behaves pleasingly unixy: 'zcat logs.gz | vim -' opens the file pretty quickly in vim. No fuss with explicit de/recompression. This also ties in to the usual "but ssh" argument, since of course you're likely to be getting logs on remote machines. 2) Bash pipelines are usuall…
Two questions: With the advent of capable editors like Visual Studio Code, is Vim still a relevant skill to have? Is SLIME still the state of the art for Lisp development environment? Is there no way to get started with Lisp programming without having to learn Emacs or Vim?
SLIME has a successor now called Sly, but yes that's still state of the art for Lisp programming. No, you don't have to learn emacs to get started with Lisp though. You'll just have an inferior experience. As a side note, if you do start to learn without emacs, please use something like this[1] for formatting your code. Most editors lack a Lisp indentation plugin, and any time you ask a question online, whomever answ…
I detect an emacs joke here.
What would be a good resource to learn Lisp in terms of problem solving or doing projects? I feel I only learn something when I use it to solve a problem in the real world.
A previous article on using Fennel for lispy Neovim configuration was posted here a week ago [1].
What would be a good resource to learn Lisp in terms of problem solving or doing projects? I feel I only learn something when I use it to solve a problem in the real world.
It worked out of the box for me and so far is the best setup I've found for Vim users learning Lisp. I tried (wasted time with) all the Vim lisp plugins.