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

MacVim through MacPorts problems

Expand Messages
  • guivho
    Hi, I have installed MacPorts through MacVim, asking for +huge +perl +ruby +tcl etc... I was quite surprised to observe that the ports command fetched its own
    Message 1 of 6 , Nov 16, 2010
    • 0 Attachment
      Hi,

      I have installed MacPorts through MacVim, asking for +huge +perl +ruby
      +tcl etc...

      I was quite surprised to observe that the ports command fetched its
      own ruby, tcl etc...

      These are by default available in OSx (10.6.5), so I thought this was
      a real waste of resources. But MacVim works, so I did not reflect
      further on this.

      Until I tried to run a console version. That is a different vim all
      together. And it does not understand ruby, perl, tcl etc...

      That would not be a problem if I would not have any plugins that are
      dependent on e.g. ruby. But recently this list drew my attention on
      the CommandT, the LustyExplorer and the LustyJuggler scripts which do
      need ruby.

      So either I manage to keep gui and console versions in sync, or I
      somehow prevent these plugins from being loaded for console vim.

      I suppose that there will be some solution to achieve the latter, but
      wouldn't the former be nice: only one single vim version in the
      system!

      I would like to hear your advice about how to proceed.

      TIA, Guivho

      --
      You received this message from the "vim_mac" 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
    • Adam Mercer
      ... Bring this up with MacPorts, file a ticket at Cheers Adam -- You received this message from the vim_mac
      Message 2 of 6 , Nov 16, 2010
      • 0 Attachment
        On Tue, Nov 16, 2010 at 11:23, guivho <guivho@...> wrote:

        > I would like to hear your advice about how to proceed.

        Bring this up with MacPorts, file a ticket at
        <http://guide.macports.org/#project.tickets>

        Cheers

        Adam

        --
        You received this message from the "vim_mac" 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
      • Robert
        ... Macports does not look at what is installed on OSX already. It does its own thing in that regard. There was another port package called Homebrew that
        Message 3 of 6 , Dec 11, 2010
        • 0 Attachment
          On 2010-11-16 12:23:40 -0500, guivho said:

          > Hi,
          >
          > I have installed MacPorts through MacVim, asking for +huge +perl +ruby
          > +tcl etc...
          >
          > I was quite surprised to observe that the ports command fetched its
          > own ruby, tcl etc...
          >
          > These are by default available in OSx (10.6.5), so I thought this was
          > a real waste of resources. But MacVim works, so I did not reflect
          >

          Macports does not look at what is installed on OSX already. It does its
          own thing in that regard. There was another port package called
          "Homebrew" that does exactly what you want.

          http://mxcl.github.com/homebrew/

          I have not used it but a friend of mine has and he says it works great. YMMV.

          HTH

          --
          Robert


          --
          You received this message from the "vim_mac" 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
        • Steven
          I use and contribute to Homebrew. I can confirm it works really well. Very active user base too. Constantly being updated. It s starting to hit those awkward
          Message 4 of 6 , Dec 13, 2010
          • 0 Attachment
            I use and contribute to Homebrew. I can confirm it works really well. Very active user base too. Constantly being updated.

            It's starting to hit those awkward teenage years though. I foresee growing pains in the near future.

            --
            You received this message from the "vim_mac" 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
          • björn
            ... Once you have installed MacVim.app inside /Applications (for example) you can start it without a GUI as follows $
            Message 5 of 6 , Dec 14, 2010
            • 0 Attachment
              On 16 November 2010 18:23, guivho <guivho@...> wrote:
              >
              > Until I tried to run a console version. That is a different vim all
              > together. And it does not understand ruby, perl, tcl etc...

              Once you have installed MacVim.app inside /Applications (for example)
              you can start it without a GUI as follows

              $ /Applications/MacVim.app/Contents/MacOS/Vim

              and to get the GUI you add the "-g" flag

              $ /Applications/MacVim.app/Contents/MacOS/Vim -g

              This seems to be what you are looking for? Read more about this in
              ":h macvim-start".

              Björn

              --
              You received this message from the "vim_mac" 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
            • guivho
              My original post was about two problems: 1) MacPorts ignored what was already installed 2) I had two vims, and the original complained about missing features
              Message 6 of 6 , Dec 14, 2010
              • 0 Attachment
                My original post was about two problems:
                1) MacPorts ignored what was already installed
                2) I had two vims, and the original complained about missing features
                triggered trough my .vimrc

                Both these problems are solved and I'd like to share my current setup.
                For starters, I have removed the MacPorts version of MacVim. I then
                installed MacVim from http://code.google.com/p/macvim/ which of course
                still left me with two different vims.

                I symlinked /usr/bin/vim to /opt/local/bin/vim to solve that problem.
                (note that ':h macvim-start' refers to /usr/local/bin/mvim, where my
                original mvim is in /opt/local/bin)

                I added a 'wait' clause the mvim script to be able to create a gwait
                symlink and specify that as editor for e.g. the "it's all text"
                extension which I use in FireFox to edit my gmail:

                % diff -u /opt/local/bin/mvim.orig ./mymvim
                --- /opt/local/bin/mvim.orig 2010-11-30 18:31:26.000000000 +0100
                +++ ./mymvim 2010-12-14 13:54:55.000000000 +0100
                @@ -52,6 +52,9 @@
                *view)
                opts="$opts -R"
                ;;
                + *wait)
                + opts="$opts -f"
                + ;;
                *ex)
                opts="$opts -e"
                ;;

                I think that this should be in the default mvim file (ignore the file
                dates on the diff output, they're not correct)

                Being a keyboard maniac, I have v, view, vim, vimdiff, g, gview,
                gviewdiff, gvim, gvimdiff as well as gwait symlinks that all link to
                the same mymvim (i.e. original mvim edited cfr supra)

                This setup is quite satisfactory, and maybe it does inspire others.

                Guivho

                --
                You received this message from the "vim_mac" 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
              Your message has been successfully submitted and would be delivered to recipients shortly.