Shaun Brady wrote: > __BEOS__ did not work, but __HAIKU__ did. That might take BeOS off > the support list, but put on Haiku. That might be okay. We're just > shy of 16 on a proper BeOS release. Haiku is 3 years out, in alpha, > but is still looking for funding in 2016. > > FWIW
Well, perhaps I should include that patch for Haiku support then. Or turn the BeOS code into Haiku code. The patch I have for Haiku is more than two years old, I hope there is an update. -- hundred-and-one symptoms of being an internet addict: 165. You have a web page burned into your glasses /// 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.
