>> 4. foldmethod=all seems buggy. When I turn it on, folds open even >> when I move through them vertically, and never fold even when I try to >> close them explicitly. Setting all the documented foldopen values >> doesn't have this affect, so evidently 'all' is not the same as >> including everything manually. > > You mean ":set foldopen=all". Right, "all" is not the same as adding > all the other ones. That works as intended, a fold at the cursor is > always open.
Ah, I see, I misunderstood the documentation. Would it make sense to add a 'put' option? Or are puts intended to unfold and the current behaviour is due to a bug? > Looks like another instance of the first problem. Indeed, I hope so, then they can both be fixed at once :) The interesting one is the one only triggered by having a nested open fold inside. When I get some time I'll see if these happen with the other fold methods, and maybe take a look at fold.c if it's not too scary. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
