Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What differentiates this from slimv? #1

Closed
pebblexe opened this issue Mar 30, 2017 · 2 comments
Closed

What differentiates this from slimv? #1

pebblexe opened this issue Mar 30, 2017 · 2 comments

Comments

@pebblexe
Copy link

Sorry, I haven't installed it yet because I haven't installed Vim 8 yet.

What features differentiate this from slimv?

@l04m33
Copy link
Contributor

l04m33 commented Mar 31, 2017

Slimv is really good at what it does, but it had some limitations.

When comparing to Slimv:

  • Vlime doesn't have Python dependency while Slimv does. Vlime needs Quicklisp though.
  • Vlime supports multiple SWANK connections, while Slimv doesn't.
  • Vlime supports remote SWANK connections through SSH tunnels, while Slimv doesn't.
  • Vlime uses the new channel & JSON APIs in Vim, which is faster than Slimv I believe. But there's no benchmark at the moment.
  • Vlime has a rather different REPL implementation, which enables swank-presentations, that means you can copy & paste most of the values returned by the REPL, like you can in Emacs. Slimv cannot do this AFAIK.
  • Vlime tries to be extendable. I think it's source code is better organized.

But Vlime has it's own limitations too:

  • Vlime doesn't come with paredit mode, you'll need to install the paredit plugin, or other plugin of your choice, by yourself.
  • Vlime is asynchronous. you can operate Vim when the server is processing a request. This may cause something weird if the request needs a long time to finish.
  • While Vlime tries to be compatible with most major CL implementations, it's not been tested thoroughly on different platforms. Maybe you can help, by actually using it :)

There's a tutorial if you're interested: :help vlime-tutor

@pebblexe
Copy link
Author

Thank you for that detailed response!

@l04m33 l04m33 closed this as completed Apr 5, 2017
sjl pushed a commit to sjl/vlime that referenced this issue Jan 24, 2020
Fix *json-cache* to avoid choking on CCL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants