Björn --
>> So, for...most...intents and purposes, mvim.app is deprecated due to the
>> *relatively* new MacVim preference. Additionally, if you read the blog
>> post, the purpose off gvim.app and mvim.app had to do with File
>> Associations. The launching in a login shell was just a bonus.
>
> I've asked this in the past, but would you consider adding all the
> file associations/icons in mvim.app to MacVim's Info.plist so that you
> can deprecate mvim.app once and for all? If you don't want to do it
> -- do you mind if I simply copy everything over myself? Or is there
> some other reason for keeping mvim.app alive?
I've been hesitant to do so because, IIRC, when I added all of those
associations, I just grabbed them from some other not-so-open-source
text editor on my system (e.g., TextMate or BBEdit... I don't remember)
and made a few modifications. I know this is poor form, but the "app"
was not meant to be exported initially... but then I saw posts from
people with the same problem, so I posted it with no claims about its
legitimacy.
So was is the copyright status of file associations buried within an
application bundle? If you think there's no problem, then I'm fine with
just moving them over. Otherwise... I guess someone (?) has to manually
add them in some sort of fresh manner. :(
Sorry for not responding about this a LONG time ago... it was always on
my ToDo list... but then my ToDo list turned more into a ToDo stack...
and... well... you know.
--Ted
--
Ted Pavlic <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
