On 01/02/2008, Nico Weber <nicolasweber@...
> attached is a patch that lets MacVim write to protected directories
> (for example /Library/InputManagers).
> The first two commits add a class called `AuthorizedShellCommand` that
> can execute arbitrary shell commands and shows the standard
> authorization dialog before doing so (think "graphical sudo"). The
> third commit is only an example for how this class is used -- this
> commit shouldn't be applied to the official tree.
> With this class, we could literally execute the steps Bruno outlined
> (put the inputmanager somewhere in the macvim bundle, preferrably with
> the defaults preset to org.vim.MacVim, `cp -pR` it to /Library/
> InputManagers, `chmod -R root:admin` it, done). A "Install \"Edit in
> in MacVim\" Input Manager" button in the prefs would be a good first
> place to put this I think.
> Likewise, we could install the `mvim` script to `/usr/local/bin` (with
> a similar button). Are there comments on how the mvim script should
> behave? Since we would install it from withing MacVim, MacVim could
> basically just put
> exec <path to myself>/Contents/MacOS/Vim -g
> in the mvim file. Would there be any problems with this? Other
I would not encourage fixed paths like this since an app bundle is
supposed to be able to be moved around (of course, if you move the app
bundle to some exotic location then mvim fails anyway, but...).
However, an item that "installs mvim" sounds fine to me.
> ps: The patches are numbered starting at 0003 because git is stronger
> than me.
> pps: Bjorn, any comments on the sparkle patch?
Both patches look great...I will try to merge them this weekend.
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php