-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some ideas ! #5
Comments
Keep in mind that the original purpose of the plugin is to allow students to use vim in Epitech. |
A gist to refer some links to show to students how to begin with vim is a very good idea ! About the git merge marker, it's cleaner to use this plugin https://github.com/rhysd/conflict-marker.vim, it was a bad idea, as much as the end of line red marker because it's invasive ! About the ColorColumn configuration, I totally agree that users must have the choice, I'm agree to add a line to the README to inform them ! |
@gnuletik As for the About new features, are you looking for something like http://vimawesome.com/plugin/vim-signify? All about helping beginners could have its place here but in the wiki. A good way to share plugins and tweaks is simply linking your .(n)vimrc online (or dotfile repo, ...) |
Yes, but for a begginer's who doesn't have theme, the default one is red. Anyway, with a theme, there isn't problems. I was just talking about highlighting merge conflicts markers in git. But the plugin I mentioned before do it ! Okay, it's true that the wiki is a better place ! I will try to put some links to help the beginners (and the more experienced ones) ! |
It would be great having an issue to track wiki advancement listing points to document too. Someone will to make it? |
I posted a new thread, I will edit it to add the page / information you want to add in the wiki. |
👍 |
Add a part in README.md to show how to configure the color of cc bar (the default one is a uggly red one)
New features ?
A part "What next ?" for vim's beginners containing for example :
The text was updated successfully, but these errors were encountered: