You can patch and update the old software, not changing behaviour, and
change the new software (progression!). If you keep updating the new
to be compatible with all the old while adding new features, you're
going to end up with a big heap of .. lots of stuff most people don't
need anymore..
If other systems rely on old software, then just dont use the new
version (maybe update the systems?)..
On Tue, Aug 23, 2011 at 11:36 AM, Christian Brabandt <cblists@256bit.org> wrote:
> On Tue, August 23, 2011 10:02 am, Tom wrote:
>> Scripting solutions aside, I thought the mailinglist would be a good
>> place to talk with developers of vim (or policy makers) on their view
>> on this. Do they post here?
>
> In the end, you need to talk to Bram about it. He decides.
>
> My guess is, that this is some vi compatibility thing and since vi- and
> backwards compatibility is very important to Bram, I think it is very
> unlikely to change. Especially, since alternative solutions have been
> mentioned.
>
> regards,
> Christian
>
> --
> You received this message from the "vim_use" 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
>
--
You received this message from the "vim_use" 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
No comments:
Post a Comment