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

autocommands added for every file of every filetype interfering with other plugins #27

Open
Valloric opened this issue Aug 7, 2012 · 1 comment

Comments

@Valloric
Copy link

Valloric commented Aug 7, 2012

I'm writing a plugin for Vim and while I'm not absolutely sure that this is the problem, I believe I've tracked it down to an interaction with the autocommands that the notes plugin adds (especially the CursorHold ones).

Is there a reason why all the autocommands in plugin/notes.vim are added for every file? Wouldn't it be more prudent to add them only for files with the 'notes' filetype (and then make them buffer-local with <buffer>)? That way all the functionality is preserved while the already crowded autocommand space is now less crowded. :)

This is also more efficient since the commands don't have to execute for irrelevant files. For instance, I doubt that it's necessary to call xolox#notes#refresh_syntax() on every CursorHold event when I'm editing a C++ file.

I love your plugins, keep up the great work!

@eivindj
Copy link

eivindj commented Mar 24, 2015

Any news on this issue?

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

2 participants