Skip to content
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

Move filetype settings to own files. Create backup dir from rake. #247

Merged
merged 3 commits into from
Sep 26, 2011
Merged

Move filetype settings to own files. Create backup dir from rake. #247

merged 3 commits into from
Sep 26, 2011

Conversation

bergman
Copy link
Contributor

@bergman bergman commented Sep 26, 2011

No functional differences, just better organised.

au FileType python set … => .vim/ftplugin/python.vim

This makes things like ':verbose set textwidth?' work.

Before:
  textwidth=79

After:
  textwidth=79
        Last set from ~/.vim/ftplugin/python_pep8.vim
VIM
end
end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does vim know to use these ftplugin for make and python code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same way it knows to use whatever you set up in your autocommand for that filetype. The part after the underscore is only used for organisation and is not used in the filetype detection.

So wherever you can write au FileType you can just as well create a file called .vim/ftplugin/.vim

EDIT:
see :h ftplugin-name for more info

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha, good to know. Thanks.

tmm1 added a commit that referenced this pull request Sep 26, 2011
Move filetype settings to own files. Create backup dir from rake.
@tmm1 tmm1 merged commit b32b67b into carlhuda:master Sep 26, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants