Live data from Hacker News

SpaceVim – Like Spacemacs, but for Vim

spacevim.org

11–20 of 186 posts

Re: SpaceVim – Like Spacemacs, but for Vim

#11
post #9

… and people wonder why I dislike Markdown. (There are fairly radical rendering differences between the GitHub page and the spacevim.org page, because different Markdown renderers with different bugs have been used, and the Markdown was fairly sloppily written.)

Is there a linter yet for markdown?

There's quite a few (outside of vim), such as https://github.com/mivok/markdownlint and https://github.com/SublimeText-Markdown/MarkdownEditing

Re: SpaceVim – Like Spacemacs, but for Vim

#13
Yay for the effort! But personally I don't think this is a good way to learn and use vim. The strength of vim is to customise it after your own needs and you'll do yourself a disservice if you end up with a config that you don't know and don't use more than x percent of.

Re: SpaceVim – Like Spacemacs, but for Vim

#14

The greatest dev timesaving tip that someone gave me was to clear my .vimrc and start off with a blank slate. vim is a language in itself [1] and it's easy to try to mimic someone who has conversational fluency in it, but as with languages, the only way to learn in practice from the start. Projects like SpaceVim try to create an IDE like environment, but because of being terminal driven, it's difficult for anyone to…

    truncate -s 0 ~/.vimrc
Shorter way:

    > ~/.vimrc

Re: SpaceVim – Like Spacemacs, but for Vim

#15

I started using Spacemacs recently for its out-of-the-box IDE-like features but the layers' functionality seems to be fairly hit-or-miss and overall the impression is one of a bug-infested nightmare. Every time I try to set up my environment on a new machine, I get some new set of problems that I have no idea how to solve (disappearing powerline, broken neotree, weird projectile caching behavior totally breaking my w…

I have the exact opposite experience with vanilla Emacs. It works consistently without issue.

Regarding plugins you can use melpa and track the latest release of everything at all times.

You can use melpa and update most stuff infrequently save for the ones that are most important to you.

You can use melpa stable and run only stable versions of everything.

You can use melpa stable and run newer versions of a minority of plugins that are important to you.

What plugins you choose to use and and whether you choose stable or unstable could very well lead to vastly different experiences.

The best strategy is to carefully select plugins which are useful to you and high quality, and run the stable versions of most things updating your tools infrequently when a new major release adds something that looks useful to you.

Re: SpaceVim – Like Spacemacs, but for Vim

#16
Oh, yeah! Good old curl | sh via HTTP. Fucking awesome. I wonder how many people get unknowingly pwned while executing such curl | sh instructions. It's not hard at all to MitM HTTP, detect if shellcode is being transmitted, then add your own instructions to it. Or you can just compile a list of known sources that encourage to execute curl | sh and MitM only them if you want to make your exploits even more discreet. What a nice way to get yourself your own little botnet. Way to go! There's a catch though. You need access to infrastructure of ISP. But is it that hard to get such access? No.

Re: SpaceVim – Like Spacemacs, but for Vim

#17
post #7

Ok, but what it is? The page doesn't explain it. The top page explanation refers to spacemacs and most vim users don't know spacemacs. Is it a vim plus a bundle of plugins? EDIT: Cleaned up the spacemacs sentence.

it's emacs with vim controls. FWIW, I wouldn't compare emacs with vim in this set up, but with something like tumx instead (and imo what emacs offers is better than tmux).

Re: SpaceVim – Like Spacemacs, but for Vim

#20
post #16

Oh, yeah! Good old curl | sh via HTTP. Fucking awesome. I wonder how many people get unknowingly pwned while executing such curl | sh instructions. It's not hard at all to MitM HTTP, detect if shellcode is being transmitted, then add your own instructions to it. Or you can just compile a list of known sources that encourage to execute curl | sh and MitM only them if you want to make your exploits even more discreet.…

curl sh is no more dangerous than running any script you haven't read, or binary you haven't decompiled for that matter. The odds of mitm are exactly the same.
Post reply on HN