You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: