SpaceVim v1.1.0 released | Hacker News Reader

SpaceVim v1.1.0 released

spacevim.org

112 pointswsdjeg47 comments

org-mode, lisp...

Adding vim like layer to Emacs made sense but its best features are lisp and modules like org... I don’t think it works the other way around...

Cool! I left my homerolled vim config for spacemacs a little over a year ago. I'm glad to see a similar project for the vim community.

It looks really nice. I'll probably never leave emacs now since I've come to love lisp, but I have co-workers ask me all the time about my editor setup who are not into giving emacs a try. Maybe they'll like this!

thanks，yeah，that is why spacevim is created.

I tried setting up spacevim (edit: wrong! It was spacemac I used) a few days ago but gave up. I couldn't make auto-complete and snippets work.

Anyone knows how to make it work without having to spend hours? I was trying to make it work for python. Also, I want tab to be used.

EDIT: I am wrong. I tried setting up spacemac. I didn't know about spacevim.

SpaceVim seems really cool, but it has so many dependencies. Seems like a nightmare to get working on Windows and the 5 other platforms I use Vim on.

I use spacevim in win 7 and archlinux

This looks great! Every once in a while I decide I want to setup vim like an IDE, and inevitably lose motivation whenever I try to setup autocomplete or linting or language server stuff.

Have you tried using a vim emulator in your IDE? I've been using IdeaVim for IntelliJ for a few months now and it feels like having the best of both worlds. You get the power of vim combined with all the typical IDE features without having to spend hours on configuration.

Same here.

Tried to get autocomplete to work in Spacemacs for C/C++ using Rtags. While it worked for the project files it could not autocomplete external libraries (such as OpenGL). Since this is why I mostly need autocomplete I could not use Spacemacs as a daily driver even though it had a lot of features that worked really well and was in general a pleasure to use.

Does anyone else here have experience related to what I tried to achieve? Would love to hear similiar experiences.

I've tried this a few times over the past year, but I've always been put off by the lack of a `SPC-f-f` equivalent (helm-find-files). I filed a thoughtful issue [0] about this a while back, but one of devs pretty much closed it immediately.

[0] https://github.com/SpaceVim/SpaceVim/issues/1122

Also, looks like `SPC-f-f` doesn't exist anymore in spacevim.

you need to load one fuzzy find layer. denite unite fzf or leaderf.

It looks like you want a non recursive file find with the ability to navigate up and down.

Denite lets you move up with U and down with <Enter>, and you can use a custom filter or source to only display files in the current directory I believe. You could configure denite to include the custom filter and mapping in the after function.

The ability to edit the full path... I honestly don't know of denite or unite provide enough support to do that, but Shougo or someone on https://vi.stackexchange.com/ might.

Anyway you can set that up then configure a custom command, but I'd note that directly emulating spacemacs isn't really what spacevim seems to be trying to do.

I just spent an hour playing around with this, but I have to say it feels more difficult to set up than my own vim config.

If you know the kind of functionality you're looking for, this quickly becomes way overkill.

>If you know the kind of functionality you're looking for, this quickly becomes way overkill.

That’s probably true of just about every framework

I've been meaning to move to Vim for years. I'm not kidding. What prevents me is just the time to learn to config it the way I want. Perhaps it is time to buckle down and grok this with SpaceVim.

It doesn't take that long to get your own config up and running.

I switched to Vim not too long ago and started with pretty much an empty config. In 1 week I had things customized to my liking and felt quite productive.

You can read about that whole process at: https://nickjanetakis.com/blog/getting-productive-with-vim-i...

I would be reluctant to use something like SpaceVim from the beginning because it's way easier to learn something new at a lower level of abstraction and only add things in as you need it.

Maybe it's worth looking at in the future, but if you do at the start you're probably going to get hit by information overload.

That's how I felt about OhMyZsh and other premade configs. I find the developers tend to make the defaults sensible and not overwhelming. I now use fish and my vim config is <100 lines and only had syntax highlighting and syntastic as dependencies.

Honestly, I think everyone should learn to use vanilla software first so they can better understand what these premade configs provide.

Thank you!

I hope someone compiles this for Raspberry Pi and gets it in the Raspbian distro. I tried to compile this a few months ago, and it filled the file system beyond capacity.

I realise that some of the contributors to the documentation here may not be native English speakers, and if so, I would encourage them to clean up the English.

If you found typos or issues with the docs, why not open a PR and fix it?

https://github.com/SpaceVim/SpaceVim/blob/master/docs/_posts...

While you make a good point that pull requests can be made because it is open-source, I've always found the "pull requests welcome" response to a (presumably good faith) piece of constructive criticism as a little dismissive.

Or, it literally means, "we don't know what you found, so please point it out."

Not every response for help is a "fork off."

Because I'd have to fork, wait for the Github client to process the fork, find the source file that produced the error, fix it, commit, push, then go back to Github to create a PR. PRs are overkill for typos on a project I don't develop on.

You can do all of this from the web interface. There's a pencil icon on the top right of the document. It will let you edit the file then create a fork and PR

Awesome, didn't know that. Thanks!

It's relatively new and fantastic for simple text edits, though I certainly would recommend actually testing changes if you're changing code.

I'm finding it hard to get to something on the website that tells me exactly what this is?

Seems like a convention of standard set of plugins and configuration.

I am very interested, seems like it has good defaults for having an IDE-like experience on vim but was not able to find a nice video tutorial explaining it.

Definitely gonna try it later.

Seems like an opposite of spacemacs - thus vim with emacs key bindings?

I believe it’s just Vim with lots of plugins and sane defaults

yeah，but it manages plugins via layer. and the layers are disabled by default.

The homepage:

>SpaceVim - Modern Vim distribution SpaceVim is a distribution of the Vim editor that’s inspired by spacemacs. It manages collections of plugins in layers, which help collecting related packages together to provide features. For example, the python layer collects deoplete.nvim, neomake and jedi-vim together to provide autocompletion, syntax checking, and documentation lookup. This approach helps keeping configuration organized and reduces overhead for the user by keeping them from having to think about what packages to install.

The "About" link at the top.

Looks like Spacemacs [1], but for vim. Spacemacs has a more thorough "what is this."

Emacs is best thought of as a lisp virtual machine that happens to edit text. Vim is a hell of a text editor that happens to have a Turing complete scripting language. Spacemacs gives emacs a good text editor, while it looks like Spacevim is attempting to make extending vim easier.

The future of emacs and vim as platforms is interesting. Perhaps, at least for developer tools, we'll see more projects using these cross platform text editors as platforms for text based user interfaces in a revolt against electron.

[1] https://www.spacemacs.org

> we'll see more projects using these cross platform text editors as platforms for text based user interfaces in a revolt against electron.

Wow, I did not anticipate this comment ending this way.

"revolt against electron" who even uses that hippy shit ?

vim for life and after

   .-=-. 
  /  +  \
  | ~~~ |
  | :wq!|
  |_____|

As a vim user, please don't give the rest of us a bad name ;). You're sounding like a hippy :)

I like your explanation of emacs and vim. Btw, neovim natively talks async using msgpack meaning plugins can be written in any language (with glue in vimscript)

I don't like the trend of Electron being used anywhere but I've really struggled to match my productive in VS Code in Vim or Spacemacs. I've certainly tried! I even spent a month or two last year using exclusively OpenBSD and nvi as a bit of an experiment - I did enjoy how quick my text editor opened for example, but I am still a lot more productive in Code. Any suggestions for someone wanting to learn without their productivity taking a dive? Maybe finding a Vim plugin for my existing editor and learning there before switching to "real" vim... I'm not sure.

For spacemacs, I'd recommend you try it again in Holy mode with Ivy. Then slowly customize some of it to add some features and key bindings to your liking that make you more productive.

Emacs really clicks if you are someone whose going to learn your way around Emacs lisp and customize things to what works best for your style.

And make sure you use the develop branch.

Once you've groked that, you can slowly try to switch to Evil bindings, and explore if you enjoy modal editing or simply get some inspiration from the Vim editing commands and style.

I use SpaceVim for everything! In a nutshell, its a "shared" configuration for vim (neovim really imho), as well as an extensable framework for adding new functionality.

For example, its nice to have to have plugins offer similiar functionality on similiar key combos. Have a shared configuration allows for once idealogy to take hold. The Spacebad + mnemonics approach of Spacemacs + Spacevim is a really good base to build on.

The one thing I can't leave Spacemacs/Doom for is Org Mode. I have everything there now. Is it even feasible for Org Mode layer in Spacevim?

Generally speaking, Org Mode is the only thing that's really missing in Vim in comparison I think. I've been using Vim Wiki but have been told it's not really comparable.

Put it the other way, what's the one thing that would be better if you did move to Vim?

Or in another way as well, what about Spacemacs/Doom would make you want to move away from it?

Performance and removing the Emacs keybinding layer that I think complicates the way I use the tool. But mostly performance.

why do I need admin permissions to run a text editor in Windows?

Reply on news.ycombinator.com