Hi Ben, Excerpts from Ben Fritz's message of Tue Feb 09 17:40:15 +0100 2010: > plugin out there, [..]
Just think about missing one comment: "This plugin is superseded. It has been merged with xy.. use xy instead" How much value can this one comment generate for you? Think about the original plugin author either a) died b) is no longer interested c) forgot his password (Yes! There is no way to get back a password. The page tells you so!) I agree that we never ever want to delete any version. But I think we must have a way to mark such packages as deprecated. I've started doing so in vim-addon-manager-known-repositories. However not many people are using it at this point in time. Why is this that important: If you look for scripts you do search www.vim.org first. It's much more unlikely that you look for comments on a wiki. I dream of: get plugin vim-addon-c(pp)-tools and have *all* features I can get doing C(++) development using Vim. Same for Ruby, Vim, Perl, Python, C#, etc. Because if man power is spread results will suffer. Vim *is* a great editor. However to keep everything working we have to join efforts else people (including me) will use Eclipse or such as main editor because IDE features do matter a lot. I agree that I'm a programmer and that I want to see specific features to get my work done faster. But it's programmers who can move Vim into the future. And if programmers have to spend weeks on setting up Vim they may just use another tool. Vim will never die. But it maybe won't have the market share it deserves.. There are more things I don't understand yet. Python and Ruby are supported by Vim. But all interfaces seem to provide only a exec and a vimeval function. If you want to execute a simple command such as echoe you have to start thinking about quoting strings. Why don't those interfaces provide a simple vim_escape function ? But that's a different (off) topic.. Marc Weber -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
