On Sep 11 2008, 11:36 am, "Kana Natsuno" <[email protected]>
wrote:
> But that's not the problem I asked. The problem is why Vim also checks
> how {pattern} for '/' or '?' was inputted to determine whether folds
> should be opened or not.
After observation on 'foldopen' in 2 years, many users stumbled and
reported
the behavior about 'foldopen' and key mappings to vim_dev/vim_use. I
believe
that it's not intuitive for most users.
Though :help 'foldtext' describes HOW 'foldopen' works as follows:
> When the command is part of a mapping this option is not used. Add
> the |zv| command to the mapping to get the same effect.
It doesn't describe WHY 'foldopen' behaves so. Anyhow:
(1) What is the reason that 'foldopen' doesn't take effect for any
command
executed by a key mapping? (for example, compatibility with old
versions)
(2) I will write a patch to add a new item for 'foldopen' which
controls
whether 'foldopen' takes effect for key mappings or not. (for
example,
":set foldopen+=map" to change the behavior) Did anyone write
similar
patches?
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
