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

Buffers blacklist #40

Merged
merged 1 commit into from
Aug 2, 2013
Merged

Buffers blacklist #40

merged 1 commit into from
Aug 2, 2013

Conversation

naquad
Copy link
Contributor

@naquad naquad commented Jul 27, 2013

In autocommands there's a check for buffer name. If it is blacklisted then nothing is done, in other case it'll execute given function. See issue #39

In autocommands there's a check for buffer name. If it is blacklisted then nothing is done, in other case it'll execute given function.
@RyanMcG
Copy link
Contributor

RyanMcG commented Jul 29, 2013

Good idea. Perhaps blacklisting filetypes would work too.

@jsallis
Copy link

jsallis commented Aug 1, 2013

👍

I came here to see if there was already an issue filed for preventing line numbers from showing up in NERDTree and this would definitely solve that.

@RyanMcG
Copy link
Contributor

RyanMcG commented Aug 1, 2013

I forked this project (a pretty breaking fork) that added this feature and many others (buffer specific variables). Since it was so breaking, I renamed it. RyanMcG/vim-autornu.

@naquad
Copy link
Contributor Author

naquad commented Aug 1, 2013

@RyanMcG cool, just tried it. +1 star and user to you

@RyanMcG
Copy link
Contributor

RyanMcG commented Aug 1, 2013

@naquad Great! I'm glad it works for you

myusuf3 added a commit that referenced this pull request Aug 2, 2013
@myusuf3 myusuf3 merged commit e4bfb08 into myusuf3:master Aug 2, 2013
@myusuf3
Copy link
Owner

myusuf3 commented Aug 2, 2013

This does fix the issue! Thanks for the pull request @naquad

@mikl
Copy link

mikl commented Sep 14, 2013

@myusuf3 it seems you have done a git push -f or something similar at some point – I had a merge conflict when pulling, and after resetting to your master branch, this commit is no longer in the master branch.

@myusuf3
Copy link
Owner

myusuf3 commented Sep 14, 2013

@mikl that was on purpose, I regretted merging that one the solution wasn't the correct way to go about it; caused everything to be super slow.

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.

5 participants