WSwsdjeg·Jun 27, 2017Submission
Show HN: SpaceVim v0.3.1 is out – an IDE for people in terminal
2 points · Open discussionwsdjeg
SpaceVim
Vim Script2016–2024
wsdjeg / SpaceVim · Archived
SpaceVim
A modular configuration of Vim and Neovim
14Distinct people
24Mentions
1Explicit recommenders
20.2KGitHub stars
What to know before exploring
What it is
A modular configuration of Vim and Neovim
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
You may want to check out SpaceVim. I've been developing on a remote machine lately; before I was using ST2/3. I could have continued to do so using (e.g.) sshfs, but I think…
canhascodez used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 1:03:20 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year24 dated mentions
Observed mentions: 2016-12-27 15:16:45 UTC to 2024-03-14 17:51:01 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 15 | 8 | 7 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
15 sourcesVery confusingly there is 'space-vim' [1] and 'SpaceVim' [2]. Your link is about the former, this submission is about the latter.
[1] https://github.com/liuchengxu/space-vim
[2] https://github.com/SpaceVim/SpaceVim
In SpaceVim – A community-driven Vim distributionI have implement this feature in https://github.com/SpaceVim/SpaceVim/pull/458
In A video of SpaceVim's mapping guide featureNice post, I want improve tmux layer in SpaceVim. I think it is best editor for developers.
https://github.com/SpaceVim/SpaceVim
In Tmux and Vim – better togetherIn the 0.3.0-dev, we have implement these new features, hope you could have a try!
1. Plugin manager ui for dein, it just looks like vim-plug, but we can hide the windows before it finished, and resume it with same command.
2. Lint on the fly fature, as neomake support temp file, so we add this feature, it is not the only feature of ale, neomake also can, but better.
3. add some commands for spacevim
you can check our github page:
https://github.com/SpaceVim/SpaceVim
1 points · Open discussionSpaceVim release v0.2.0 with mnemonic key bindings(which key) feature
1 points · Open discussionSpaceVim will release v0.2.0 with 100+ issus fixed
1 points · Open discussionSpaceVim: a fully suited Vim distribution
2 points · Open discussionI got an email from the same guy, saying he noticed me starring a competing fork of SpaceVim, and asking if I "would like to try our project, https://github.com/SpaceVim/SpaceVim or https://spacevim.org "???
I think that's the first time I've ever gotten a personal email because I starred someone else's repo!
In Using Vim as a Python IDESpaceVim releases v0.1.0 – support many languages
1 points · Open discussionSpaceVim – support custom layer after this PR
1 points · Open discussionfor vim do: sh mv ~/.vimrc ~/.vimrc_bak mv ~/.vim ~/.vim_bak git clone https://github.com/SpaceVim/SpaceVim.git ~/.vim
for nvim do: sh git clone https://github.com/SpaceVim/SpaceVim.git ~/.config/nvim
I'm guessing markdown fail.
In SpaceVim – Like Spacemacs, but for VimThe install guide:
vim sh mv ~/.vimrc ~/.vimrc_bak mv ~/.vim ~/.vim_bak git clone https://github.com/SpaceVim/SpaceVim.git ~/.vim
nvim sh git clone https://github.com/SpaceVim/SpaceVim.git ~/.config/nvim
Why do people always expect the average joe user to understand this? What do I do with this? Do I run this in the terminal? Then what? First line opens Vim and it opens 11 files. Now what? This seems like the average explanation that works for the person who writes it, but is useless unless you know this already.
In SpaceVim – Like Spacemacs, but for Vim