2009/9/17 Suresh Govindachar <[email protected]>: > > > Hello, > > People say that since Mac OS is based on Unix (BSD?), working in a > Mac command shell is just like working in any Unix command shell. > > > But on this email list, I have come across the treatment of VIM on > Mac as a special case that has some quirks. So what makes VIM on > Mac OS so much more difficult than VIM on Unix?
There is a vim_mac mailing list that may answer your question better. Not knowing your exact context of the quirks, I can only describe something that I am aware of: For the command line, there is not much difference. Mac OS X ships with a command-line vim, in fact. I believe it is built with the normal Unix way. Mac has a different GUI environment, not based on X. There are Vim ports that are based on the Cocoa or Carbon framework in Mac OS X, which are not incorporated the mainstream Vim tree. In fact, in order to use the modern Cocoa look and feel, I believe you need to write some Objective-C code, which Bram probably does not want in his tree. I suggest you check out MacVim, which I use on the Mac routinely. Another difference was that in the past Mac used only CR as the end-of-line mark, which is different from either Windows (using CR LF) or Unix (using LF). This was only historical, and nowadays Mac OS X using the same convention as any other Unices. Just my 2 cents. Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/ --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
