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

All folds initially toggled when trying to just toggle one fold #4

Open
jondkinney opened this issue Jan 12, 2015 · 3 comments
Open

Comments

@jondkinney
Copy link

Hi there,

This is a great plugin, but I have set nofoldenable as my default in my .vimrc. When I load up a controller or spec or whatever it's all good, the file is fully expanded. But when I try to toggle just one method closed, they all close! I'm not sure why that is, but two things... 1) it'd be great to be able to do exactly this, but with a different mapping from the standard fold toggle, 2) how can I restore the default of toggling just the method I'm inside of?

Thanks!

@andyw8
Copy link

andyw8 commented Feb 10, 2016

I've just started using this plugin and I'm having the same issue.

@fabpopa
Copy link

fabpopa commented Sep 30, 2016

I think the solution might be set foldlevelstart=99 in your .vimrc and has nothing to do with the plugin. This GitHub issue came up as I was searching for a reason why za was closing all folds the first time you type it in a new buffer. I guess it has to do with the default foldlevelstart of -1.

@jondkinney
Copy link
Author

@fabpopa thanks! That seems to have sorted things nicely.

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