Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Personal Preferences vimrc #1

Open
straps opened this Issue May 12, 2011 · 5 comments

Comments

Projects
None yet
3 participants

straps commented May 12, 2011

First of all, thanks for your vimrc, works very well and is the best I've found for Javascript programming...

Could be useful to add an empty .vimrc-custom where everyone, if needed, can insert it's own code and personal shortcuts.

Thanks again

Owner

vgod commented May 12, 2011

That's a good idea! I will add it later.

Owner

vgod commented May 12, 2011

It seems a little tricky to get the path to the custom vimrc. I don't want to put the custom vimrc in the home directory, but in the ~/.vim. However, I can't find a universal way to get its path.

In fact, since I've used pathogen, you can create your own custom settings without modifying my vimrc by putting them in the ~/.vim/bundle//plugin/.vim.

straps commented May 12, 2011

I've inserted the source .vimrc-custom command on bottom of your .vimrc file and created my .vimrc-custom in the same directory; it works for me...

Owner

vgod commented May 12, 2011

I would like to put .vimrc-custom in the ~/.vim folder, not the home directory.

I guess put .vimrc-custom in the home directory makes more sense. It's custom setting file, and shouldn't be part of version control. the .vimrc could add the logic to detect if there are .vimrc-custom in the home directory and source it if there is

asivitz pushed a commit to asivitz/vimrc that referenced this issue Dec 10, 2014

Add backwards compatible s:set_visual_marks()
Vim patch 7.3.590:

    updated for version 7.3.590
    Problem:    The '< and '> marks cannot be set directly.
    Solution:   Allow setting '< and '>. (Christian Brabandt)

This change was committed less than a year ago, leaving most vendor
installations of vim unable to run vim-sexp.

Closes #1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment