> Unfortunately, getting things to compile as a framework is the easy > part
I agree. However, it's the first part. :) > how to deal with the fact that Vim is an application and not just a > view will require more thought (I have no good solution, and I've > spent some time thinking on this). Yes, that's true. I think that one cannot get the perfect solution—if it exists at all—at the first time. I like more the iterative approach: first get a working version—even it is crappy—collect feedback and gradually improve it. When the direction should be completely wrong, well, start over; now you know how not to do it and why. :) BTW: Is there a easy way to forbid certain commands, eg :e or :tabe, being sent to the Vim-backend? As far as I can see, not the complete command :e is sent to the backend, but each character separately. Well, I could discard the result coming back from the backend (and undo the command), but this would be very ugly... Best, Tae -- @hataewon http://qvacua.com -- -- You received this message from the "vim_mac" 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_mac" 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.
