On 20 July 2011 15:25, Janusz Bossy wrote: > On Wed, Jul 20, 2011 at 3:18 PM, björn wrote: >> Now that Mac OS X Lion has been released I have pushed my "lion >> branch" to GitHub [1]. I have not yet had much time to think about >> Lion + MacVim so this branch does not contain much apart from the >> possibility to compile MacVim on Lion and tentative support for Lion's >> native full screen (there are still bugs to iron out with respect to >> full screen). > > thanks for the update. I have one very important question though - is > it safe to update to Lion - will the current MacVim (59) work without > any problems or have you found some issues? Maybe some plugins do not > work etc.?
I have not run into any problems running snapshot 59 on the developer preview of Lion. That being said, I am very low-tech when it comes to using plugins so I don't know if there will be any problems. It is safe to assume that plugins that are written in Vim script will work fine, but more complex plugins that are written in Ruby/Python/... may or may not work (I did read some tweet about one user having to rebuild the Cmd-T plugin in order to get it working). What I can say is that at least one Ruby plugin is working, namely the Lusty Explorer plugin (since that is one that I actually use). Maybe some other early adopters would like to chime in and let us know what plugins they use and whether they work or not? Fixing Lion related bugs is top priority right now so you can be assured that I'll do my best to fix any such bugs as quickly as I can. (The issue with Ruby is tricky however, and I'd like to restate my plea for help in fixing this bug.) Björn -- 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
