Marc-- Lots of people in the Vim community have thought about, maybe even started writing vim clones (I am guilty of this). There are lots of partial vim emulators embedded into other editors (vintage mode in Sublime, ViEMU for visual studio, many many more). These clones are considered "good" or "bad" based on if they support the X features you require. If they do, they seem fine, but as soon as they don't, they land on the trash heap, because the editor you spend your day in is the land of muscle memory.
Vim has thousands of features, each individual may only use a few, but they aren't the SAME few. Hence if you a vim clone, you would have to start by matching the feature set. Don't assume because you put a low value on feature X that the community agrees with your assessment. Once you have the giant feature list (every vim feature, maybe less some compatibility ones since you are breaking with the past), you could start to bucket them into core and extension buckets. In theory, with a good small core and a decent light language as the default (maybe forced only) extension language (something like Lua, not something like Python), you might be able to rebucket a lot of features that currently live in core vim into extensions that ship with your clone. But the level of effort and the time investment is absolutely massive. I think an aggressive attempt to fix the flaws you see in Vim is worth more than trying to fork or rewrite. -- Robert Melton -- -- 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 because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
