Loading ...
Sorry, an error occurred while loading the content.

Re: MacVim and LaTeX

Expand Messages
  • Ted Pavlic
    ... It s not really a wrapper as much as a launcher. All the script does is: if( something not defined ) define it exec $0 else exec macvim end Because
    Message 1 of 15 , Dec 29, 2007
    • 0 Attachment
      > It's a bit more complicated than all that though, because of the way
      > MacVim spawns subprocesses, the need to support different shells, and
      > so on.
      >
      > I think there are other deeper reasons for not starting MacVim via a
      > wrapper that logs in first, though (interapplication communication
      > and such).

      It's not really a wrapper as much as a launcher. All the script does is:

      if( something not defined )
      define it
      exec $0
      else
      exec macvim
      end

      Because everything gets exec'd, there are no extra processes hanging
      around, and macvim gets launched exactly as it would if it were called
      directly.

      Running mvim twice is identical to running MacVim twice, but the paths
      get set correctly.

      --Ted


      --
      Ted Pavlic <ted@...>

      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_mac" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    Your message has been successfully submitted and would be delivered to recipients shortly.