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

plugins in vim 7.1

Expand Messages
  • Tushar Desai
    Hello, I recently upgraded from vim 7.0 to vim 7.1 (on ubuntu feisty) by compiling the vim7.1 tarball. However, it looks like my plugins are not working, For
    Message 1 of 6 , May 30, 2007
      Hello,

      I recently upgraded from vim 7.0 to vim 7.1 (on ubuntu feisty) by
      compiling the vim7.1 tarball.

      However, it looks like my plugins are not working, For example, the
      plugin that used to highlight matching braces/parentheses is not doing
      so.

      I downloaded a cscope_maps.vim plugin for some cscope short-cuts and
      although the plugin seems to be getting loaded, the keystrokes don't
      seem to be working.

      The plugins are located at /usr/local/share/vim/vim71/plugins.

      thanks,
      -tushar.
    • panshizhu@routon.com
      ... Did you make install from the tarball? If compiled from tarball, the prefix defaults to /usr/local, while the ubuntu official version will be in /usr ...
      Message 2 of 6 , May 30, 2007
        "Tushar Desai" <tsdesai@...> 写于 2007-05-31 13:51:28:
        > I recently upgraded from vim 7.0 to vim 7.1 (on ubuntu feisty) by
        > compiling the vim7.1 tarball.
        Did you "make install" from the tarball?
        If compiled from tarball, the prefix defaults to /usr/local, while the
        ubuntu official version will be in /usr

        >
        > The plugins are located at /usr/local/share/vim/vim71/plugins.
        This is not the right place to place your plugins, a better approach is to
        put it into your ~/.vim/plugins

        HTH.
        --
        Sincerely, Pan, Shi Zhu. ext: 2606
      • A.J.Mechelynck
        ... This _is_ the right place for plugins distributed with Vim, like the one to highlight matching parentheses (matchparen.vim)... except that there should be
        Message 3 of 6 , May 31, 2007
          panshizhu@... wrote:
          > "Tushar Desai" <tsdesai@...> 写于 2007-05-31 13:51:28:
          >> I recently upgraded from vim 7.0 to vim 7.1 (on ubuntu feisty) by
          >> compiling the vim7.1 tarball.
          > Did you "make install" from the tarball?
          > If compiled from tarball, the prefix defaults to /usr/local, while the
          > ubuntu official version will be in /usr
          >
          >> The plugins are located at /usr/local/share/vim/vim71/plugins.
          > This is not the right place to place your plugins, a better approach is to
          > put it into your ~/.vim/plugins

          This _is_ the right place for plugins distributed with Vim, like the one to
          highlight matching parentheses (matchparen.vim)... except that there should be
          no s at the end of $VIMRUNTIME/plugin/

          "make install" would indeed have created all the runtime directories exactly
          where the version which "make" compiled just before that would expect them.

          >
          > HTH.
          > --
          > Sincerely, Pan, Shi Zhu. ext: 2606
          >
          >

          HTH,
          Tony.
          --
          Don't get suckered in by the comments -- they can be terribly
          misleading. Debug only code.
          -- Dave Storer
        • A.J.Mechelynck
          ... - What does ls -l `which vim` display? It should be your vim 7.1 - The :scriptnames command will show you which files (including plugins) have been
          Message 4 of 6 , May 31, 2007
            Tushar Desai wrote:
            > I had done a "make install" for vim7.1 and that's how the
            > /usr/local/share/vim71/... dir structure was created on my machine.
            >
            > Also, the directory is "plugin" and not "plugins" (which was my typo
            > in the email).
            >
            > The makeparens.vim plugin has stopped working in Fedora Core 6 as
            > well. The only thing common is that on both machines I started with
            > vim7.0 and then manually upgraded to vim 7.1, by compiling from the
            > tarball.
            >
            > Thanks for your help.

            - What does

            ls -l `which vim`

            display? It should be your vim 7.1

            - The ":scriptnames" command will show you which files (including plugins)
            have been sourced.

            - Near the middle of the output of ":version", there is a list of default
            directories for the current version of Vim.


            Best regards,
            Tony.
            --
            In specifications, Murphy's Law supersedes Ohm's.
          • A.J.Mechelynck
            see my comments interspersed and at bottom ... meaning the two outstanding patches were not compiled-in. ... You might want to check :help matchparen
            Message 5 of 6 , May 31, 2007
              see my comments interspersed and at bottom

              Tushar Desai wrote:
              > Thanks Tony; here's the output
              >
              > :scriptfiles
              >
              > /usr/local/share/vim/vim71/plugin/cscope_maps.vim
              > 2: /usr/local/share/vim/vim71/plugin/getscriptPlugin.vim
              > 3: /usr/local/share/vim/vim71/plugin/gzip.vim
              > 4: /usr/local/share/vim/vim71/plugin/matchparen.vim
              ...well, it was sourced:----------------^

              > 5: /usr/local/share/vim/vim71/plugin/netrwPlugin.vim
              > 6: /usr/local/share/vim/vim71/plugin/rrhelper.vim
              > 7: /usr/local/share/vim/vim71/plugin/spellfile.vim
              > 8: /usr/local/share/vim/vim71/plugin/tarPlugin.vim
              > 9: /usr/local/share/vim/vim71/plugin/tohtml.vim
              > 10: /usr/local/share/vim/vim71/plugin/vimballPlugin.vim
              > 11: /usr/local/share/vim/vim71/plugin/zipPlugin.vim
              > 12: /usr/local/share/vim/vim71/menu.vim
              > 13: /usr/local/share/vim/vim71/autoload/paste.vim
              > 14: /home/tushard/.gvimrc
              > 15: /usr/local/share/vim/vim71/syntax/syntax.vim
              > 16: /usr/local/share/vim/vim71/syntax/synload.vim
              > 17: /usr/local/share/vim/vim71/syntax/syncolor.vim
              > 18: /usr/local/share/vim/vim71/filetype.vim
              > 19: /usr/local/share/vim/vim71/colors/desert.vim
              > 20: /usr/local/share/vim/vim71/syntax/cpp.vim
              > 21: /usr/local/share/vim/vim71/syntax/c.vim
              >
              > :version
              > :vers
              > VIM - Vi IMproved 7.1 (2007 May 12, compiled May 15 2007 09:52:47)
              > Compiled by tushard@sjctushard-lnx

              meaning the two outstanding patches were not compiled-in.

              > Huge version with GTK2-GNOME GUI. Features included (+) or not (-):
              > +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
              > +cindent
              > +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
              > +comments +cryptv
              > +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic
              > +emacs_tags +eval
              > +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding
              > -footer +fork()
              > -gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap
              > +libcall
              > +linebreak +lispindent +listcmds +localmap +menu +mksession
              > +modify_fname +mouse
              > +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm
              > +mouse_xterm +multi_byte
              > +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl
              > +postscript +printer
              > +profile +python +quickfix +reltime +rightleft -ruby +scrollbind
              > +signs +smartindent
              > -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static
              > -tag_any_white -tcl
              > +terminfo +termresponse +textobjects +title +toolbar +user_commands
              > +vertsplit
              > +virtualedit +visual +visualextra +viminfo +vreplace +wildignore
              > +wildmenu +windows
              > +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard
              > -xterm_save
              > system vimrc file: "$VIM/vimrc"
              > user vimrc file: "$HOME/.vimrc"
              > user exrc file: "$HOME/.exrc"
              > system gvimrc file: "$VIM/gvimrc"
              > user gvimrc file: "$HOME/.gvimrc"
              > system menu file: "$VIMRUNTIME/menu.vim"
              > fall-back for $VIM: "/usr/local/share/vim"
              > Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
              > -I/usr/include/gtk-2.0 -I/
              > usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo
              > -I/usr/include/pango-1
              > .0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
              > -I/usr/include/freetype2 -I/usr/inc
              > lude/libpng12 -DORBIT2=1 -pthread -I/usr/include/libgnomeui-2.0
              > -I/usr/include/libgnome-
              > 2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0
              > -I/usr/include/libart-2.0 -I/
              > usr/include/gconf/2 -I/usr/include/libbonoboui-2.0
              > -I/usr/include/gnome-vfs-2.0 -I/usr/lib
              > /gnome-vfs-2.0/include -I/usr/include/gnome-keyring-1
              > -I/usr/include/glib-2.0 -I/usr/lib/g
              > lib-2.0/include -I/usr/include/orbit-2.0 -I/usr/include/libbonobo-2.0
              > -I/usr/include/bonob
              > o-activation-2.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2
              > -I/usr/lib/gtk-2.0/incl
              > ude -I/usr/include/atk-1.0 -I/usr/include/cairo
              > -I/usr/include/libpng12 -I/usr/include/lib
              > xml2 -O2 -fno-strength-reduce -Wall -D_REENTRANT -D_GNU_SOURCE
              > -I/usr/local/inclu
              > de -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm
              > -I/usr/lib/perl5/5.8.8/
              > i386-linux-thread-multi/CORE -I/usr/include/python2.4 -pthread
              > Linking: gcc -L/lib -Wl,-E
              > -Wl,-rpath,/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE
              > -L/usr/local/lib -o vim -L/lib -lgtk-x11-2.0 -lgdk-x11-2.0
              > -latk-1.0 -lgdk_pixbuf-2.0
              > -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0
              > -lglib-2.0 -L/lib -l
              > gnomeui-2 -lbonoboui-2 -lgnome-keyring -lxml2 -lgnomecanvas-2
              > -lgnome-2 -lpopt -lart_lgpl_
              > 2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
              > -lgdk_pixbuf-2.0 -lpangocairo-1.0 -
              > lpango-1.0 -lcairo -lbonobo-2 -lgnomevfs-2 -lbonobo-activation
              > -lgconf-2 -lgobject-2.0 -lO
              > RBit-2 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lXt -lncurses
              > -lacl -lgpm -Wl,-E -
              > Wl,-rpath,/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE
              > -L/usr/local/lib /usr/lib/per
              > l5/5.8.8/i386-linux-thread-multi/auto/DynaLoader/DynaLoader.a
              > -L/usr/lib/perl5/5.8.8/i386-
              > linux-thread-multi/CORE -lperl -lresolv -lutil -lc
              > -L/usr/lib/python2.4/config -lpython2.4
              > -lutil -lm -Xlinker -export-dynamic
              >
              >
              >
              > On 5/31/07, A.J.Mechelynck <antoine.mechelynck@...> wrote:
              >> Tushar Desai wrote:
              >> > I had done a "make install" for vim7.1 and that's how the
              >> > /usr/local/share/vim71/... dir structure was created on my machine.
              >> >
              >> > Also, the directory is "plugin" and not "plugins" (which was my typo
              >> > in the email).
              >> >
              >> > The makeparens.vim plugin has stopped working in Fedora Core 6 as
              >> > well. The only thing common is that on both machines I started with
              >> > vim7.0 and then manually upgraded to vim 7.1, by compiling from the
              >> > tarball.
              >> >
              >> > Thanks for your help.
              >>
              >> - What does
              >>
              >> ls -l `which vim`
              >>
              >> display? It should be your vim 7.1
              >>
              >> - The ":scriptnames" command will show you which files (including
              >> plugins)
              >> have been sourced.
              >>
              >> - Near the middle of the output of ":version", there is a list of default
              >> directories for the current version of Vim.
              >>
              >>
              >> Best regards,
              >> Tony.
              >> --
              >> In specifications, Murphy's Law supersedes Ohm's.
              >>
              >
              >

              You might want to check ":help matchparen" (without the quotes of course).


              Best regards,
              Tony.
              --
              ARTHUR: (as the MAN next to him is squashed by a sheep) Knights! Run away!
              Midst echoing shouts of "run away" the KNIGHTS retreat to cover with the odd
              cow or goose hitting them still. The KNIGHTS crouch down under cover.
              "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
            • A.J.Mechelynck
              ... No. The patches are in ftp://ftp.vim.org/pub/vim/patches/7.1/ and are _in addition_ to the tarball which is 7.1.0. See
              Message 6 of 6 , May 31, 2007
                Tushar Desai wrote:
                > Hi Tony,
                >
                > which patches are you referring to? if download latst vim7.1 tarball,
                > will it have the patches?
                >
                > thanks for your help,
                > -tushar.

                No. The patches are in ftp://ftp.vim.org/pub/vim/patches/7.1/ and are _in
                addition_ to the tarball which is 7.1.0.

                See http://users.skynet.be/antoine.mechelynck/vim/compunix.htm (which is for
                7.0, but you ought to be able to use it /mutatis mutandis/ fot 7.1) about how
                to download and apply the patches.


                Best regards,
                Tony.
                --
                But the greatest Electrical Pioneer of them all was Thomas Edison, who
                was a brilliant inventor despite the fact that he had little formal
                education and lived in New Jersey. Edison's first major invention in
                1877, was the phonograph, which could soon be found in thousands of
                American homes, where it basically sat until 1923, when the record was
                invented. But Edison's greatest achievement came in 1879, when he
                invented the electric company. Edison's design was a brilliant
                adaptation of the simple electrical circuit: the electric company sends
                electricity through a wire to a customer, then immediately gets the
                electricity back through another wire, then (this is the brilliant
                part) sends it right back to the customer again.

                This means that an electric company can sell a customer the same batch
                of electricity thousands of times a day and never get caught, since
                very few customers take the time to examine their electricity closely.
                In fact the last year any new electricity was generated in the United
                States was 1937; the electric companies have been merely re-selling it
                ever since, which is why they have so much free time to apply for rate
                increases.
                -- Dave Barry, "What is Electricity?"
              Your message has been successfully submitted and would be delivered to recipients shortly.