Kazunobu Kuriyama wrote: > 2017-02-22 19:39 GMT+09:00 Tony Mechelynck <[email protected]>: > > > On Wed, Feb 22, 2017 at 11:25 AM, Yegappan Lakshmanan > > <[email protected]> wrote: > > > Hi all, > > > > > > Why is the native MacOS port of Vim not part of the mainline > > > Vim source and is maintained in a separate repository? > > > > > > https://github.com/macvim-dev/macvim > > > > > > The above branch is actively synced with the mainline Vim > > > source. But it should be part of the mainline Vim source base. > > > > > > Note that I am able to build and run Vim on MacOS from > > > the main branch. But the above clone looks like a more > > > native port of Vim. > > > > > > Thanks, > > > Yegappan > > > > The idea has merit. > > > > <snip> > > A native-Mac Vim GUI requires the macvim code. > > > > That exactly makes MacVim unique. Apart from the core part imported from > the mainline Vim, the GUI part is written in Objective-C and takes > advantage of macOS's native API such as CoreText and Cocoa. Thanks to > them, MacVim works for macOS users as if Vim were written as a native GUI > application for macOS and enjoys higher quality rendering of an established > reputation. In addition, the GUI has some features gvim doesn't have, such > as translucent background, ligatures and so on. To some extent, the > project has already been going their own way independently of the mainline > Vim. > > As such, if we really hope to merge MacVim into the mainline Vim most > successfully, we definitely need not only the codebase but also people who > have a working knowledge of development and maintenance of MacVim and are > willing to join us. Obviously, the people who are most qualified for the > first requirement are honorable MacVim developers. The second requirement, > therefore, depends on their will.
The current split in two repositories has proven to work well. Sometimes a change for macOS needs to be made in the main Vim repo, but it doesn't happen very often. The advantage of two separate repositories is that we can have a separate set of developers working on each. Thus, I don't really see an advantage in merging the repositories. -- hundred-and-one symptoms of being an internet addict: 8. You spend half of the plane trip with your laptop on your lap...and your child in the overhead compartment. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" 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_dev" 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/d/optout.
