Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SpaceVim – Like Spacemacs, but for Vim

spacevim.org

Post reply on HN
Print view View original

61–70 of 186 posts

Re: SpaceVim – Like Spacemacs, but for Vim

#61

Post by bigbugbag »

shmerl wrote: post #14
madmax108 wrote: post #8

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

Not really shorter as I have to Ctrl+C to get back to shell afterwards.

Anyways my zsh has noclobber set so your command fails with error: zsh: file exists: ~/.vimrc

Re: SpaceVim – Like Spacemacs, but for Vim

#62

Post by ageofwant »

madmax108 wrote: post #8

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…

I have done this and while 'regret' is going to far, I would have benefit more from doing something more productive with that time.

Re: SpaceVim – Like Spacemacs, but for Vim

#63

Post by stplsd »

shmerl wrote: post #14
madmax108 wrote: post #8

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

Or to be completely portable

:> ~/.vimrc

Re: SpaceVim – Like Spacemacs, but for Vim

#64

Post by stplsd »

bigbugbag wrote: post #61
shmerl wrote: post #14

Earlier quoted context omitted.

truncate -s 0 ~/.vimrc Shorter way: > ~/.vimrc

Not really shorter as I have to Ctrl+C to get back to shell afterwards. Anyways my zsh has noclobber set so your command fails with error: zsh: file exists: ~/.vimrc

> ~/.vimrc works on bash, but it hangs on zsh because it treats it like cat > ~/.vimrc (> without any command in front of it is not well defined in POSIX) So portable way to do this is like this:

:> ~/.vimrc

Re: SpaceVim – Like Spacemacs, but for Vim

#65

Post by hollander »

The 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.

Re: SpaceVim – Like Spacemacs, but for Vim

#66

Post by bigbugbag »

scrollaway wrote: post #27
semi-extrinsic wrote: post #23

Earlier quoted context omitted.

No, installing a package using my package manager will a) ensure this exact binary/script is GPG signed by someone I ostensibly trust b) ensure it's not been tampered with by a MitM between the hosting server and my computer This reduces my risk exposure to "creator of software X (or distro packager Y) has turned rogue", which is many orders of magnitude less likely than "website of software X got pwned, or someone i…

That does not invalidate what I said.

It absolutely does.

You trust the distro maintainer and have a security mechanism to ensure the scripts and binaries have not been tampered with.

So virtually no risk of MitM and very little risk of malicious scripts and binaries.

Reading script and decompiling binaries does not imply you understand every thing they do, but it does imply that you have an unlimited amount of time which is impractical at best.

Re: SpaceVim – Like Spacemacs, but for Vim

#67

Post by ageofwant »

chrismorgan wrote: post #2

… 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.)

Yes I recognized the markdown fails from my own markdown fails. Especially when you move repos between github and bitbucket, and expect README.md to 'just work', it seldom does. I've gone between md, org and even rst. They are all great, but still suck in curious ways. pandoc helps but it is a whole kettle of fermented fish in itself.

Re: SpaceVim – Like Spacemacs, but for Vim

#68

Post by yrro »

madmax108 wrote: post #8

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…

FYI, Vim 8 ships a defaults.vim that set up some nice defaults for new users, and an empty .vimrc file disables processing of these files. A 'null' .vimrc looks something more like:

    unlet! skip_defaults_vim
    source $VIMRUNTIME/defaults.vim
See ':help defaults' for more info.

Re: SpaceVim – Like Spacemacs, but for Vim

#69

Post by ageofwant »

hollander wrote: post #65

The 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…

   for 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.

Re: SpaceVim – Like Spacemacs, but for Vim

#70

Post by yrro »

hollander wrote: post #65

The 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…

Particularly annoying given that Vim 8 (finally!) has a perfectly fine packaging system.
Post reply on HN