3 ms·

It's hard for me to imagine anyone installing this project and using it. Even when picking and installing vim plugins one by one it's hard to remember what they

It's hard for me to imagine anyone installing this project and using it. Even when picking and installing vim plugins one by one it's hard to remember what they all do and how to use them. I think it's better to see this project as an inspiration, like looking at someone else's dotfiles.

davidkunz 5y ago
Yes, I agree with you. The installation of a plugin is the easy part. Properly configuring it to fit _your_ needs and remembering the commands is the hard part. No all-in-one setups can make this effort go away.
rjzzleep 5y ago
Interesting point. I think it has two sides to it: 1. I started using Spacemacs which got me into using Emacs(mainly for org mode in the beginning). I'm not capable of building an emacs config from scratch(nor do I care). 2. In Vim though I already have my vim config and have been customizing it. When I try to use these neovim distributions, they're very far off how I configured my vim and I have no idea how to reconcile these two things. I feel like once you are capable enough to configure it on your own, you won't really be happy with these things, but neovim is also almost like the ever changing javascript ecosystem. There are new completion engines coming out every day, new file trees, etc. etc. I don't feel like changing to the next best lsp engine every 6 months. Also, spacemacs seems to have a better hook mechanism when it comes to configuring the default configuration.
memco 5y ago
As a counter point: most IDEs come with defaults for many things and offer the ability to customize. Whether it's better to have defaults that you have to override or have no pre-configured tools seems dependent on the user and the tool. I've personally been turned off by how much work it takes to get vim functional on the same level as my other tools and have often wished someone had put together a better starting point and explained how to integrate, extend and customize. I like that if I want to, I can build up from zero to a totally personalized vim setup, but I don't like that most of the time I have to start from zero and build a totally personalized setup.

davidkunz 5y ago

Yes, I agree with you. The installation of a plugin is the easy part. Properly configuring it to fit _your_ needs and remembering the commands is the hard part. No all-in-one setups can make this effort go away.

rjzzleep 5y ago

Interesting point. I think it has two sides to it: 1. I started using Spacemacs which got me into using Emacs(mainly for org mode in the beginning). I'm not capable of building an emacs config from scratch(nor do I care). 2. In Vim though I already have my vim config and have been customizing it. When I try to use these neovim distributions, they're very far off how I configured my vim and I have no idea how to reconcile these two things. I feel like once you are capable enough to configure it on your own, you won't really be happy with these things, but neovim is also almost like the ever changing javascript ecosystem. There are new completion engines coming out every day, new file trees, etc. etc. I don't feel like changing to the next best lsp engine every 6 months. Also, spacemacs seems to have a better hook mechanism when it comes to configuring the default configuration.

memco 5y ago

As a counter point: most IDEs come with defaults for many things and offer the ability to customize. Whether it's better to have defaults that you have to override or have no pre-configured tools seems dependent on the user and the tool. I've personally been turned off by how much work it takes to get vim functional on the same level as my other tools and have often wished someone had put together a better starting point and explained how to integrate, extend and customize. I like that if I want to, I can build up from zero to a totally personalized vim setup, but I don't like that most of the time I have to start from zero and build a totally personalized setup.