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

Taskpaper ftdetect somehow screws up python file detection #19

Open
rdeits opened this issue Nov 17, 2011 · 2 comments
Open

Taskpaper ftdetect somehow screws up python file detection #19

rdeits opened this issue Nov 17, 2011 · 2 comments

Comments

@rdeits
Copy link

rdeits commented Nov 17, 2011

This is a weird one...

Somehow ftdetect/taskpaper.vim is causing vim to set the filetype of a .py file which contains the # character at the start of a line to conf instead of python.

To reproduce:
Create an empty file called foo.py
Open it in vim
Do set ft? to check the filetype, verify that it shows up as "python"
Enter a single # into the file, then close and re-open it
Check the filetype: it's now "conf"
Delete the # and re-open: it's now "python" again.

Workaround:
Comment out the "augroup taskpaper" and "augroup END" lines in ftdetect/taskpaper.vim. This seems to completely fix the problem.

Any thoughts? This may just be taskpaper interacting badly with something else I've installed.

@davidoc
Copy link
Owner

davidoc commented Feb 18, 2012

Confirmed, but I thought the augroup plugin / augroup END structure was fairly standard...

@linux478
Copy link

according to http://learnvimscriptthehardway.stevelosh.com/chapters/44.html it is not needed.

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

No branches or pull requests

3 participants