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

Re: loadview errors

Expand Messages
  • h3xx
    Ah. That seems to have fixed it. Thank you very much. I guess that ll teach me to use a distro that packages vim and gvim separately [they had separate
    Message 1 of 3 , Jan 7, 2009
    • 0 Attachment
      Ah. That seems to have fixed it. Thank you very much.

      I guess that'll teach me to use a distro that packages vim and gvim
      separately [they had separate binaries].

      On Jan 6, 1:23 pm, Tony Mechelynck <antoine.mechely...@...>
      wrote:
      > On 06/01/09 16:27, h3xx wrote:
      >
      >
      >
      > > I set up my ~/.vim/filetype.vim to include these lines:
      >
      > > aug views
      > >     au!
      >
      > >     au BufWinLeave  *    if expand("%") != "" |
      > >                          \ mkview |
      > >                          \ endif
      > >     au BufWinLeave  *    if expand("%") != "" |
      > >                          \ silent loadview |
      > >                          \ endif
      > > aug END
      >
      > > So that every time I stopped editing/viewing a file, vim would save my
      > > folds, options, etc. in a file in ~/.vim/view/
      >
      > > But if I edit a file in gvim and then open it again in console vim, I
      > > get the following error:
      >
      > > Error detected while processing /home/h3xx/.vim/view/[filename]=:
      > > line 6:
      > > E518: Unknown option: balloonexpr=
      > > line 46:
      > > E474: Invalid argument: imsearch=2
      >
      > > I looked it up and both those options refer to things only available
      > > in gvim. My question is whether there is a way to either omit those
      > > options when saving the view with gvim, or to suppress those errors
      > > when editing in console vim.
      >
      > If you are on a Unix-like OS, use a single binary as gvim and Console
      > Vim. You can compile it yourself, seehttp://users.skynet.be/antoine.mechelynck/vim/compunix.htm
      >
      > Then you'll find yourself with a GUI-enabled version of Vim as
      > /usr/local/bin/vim and a softlink /usr/local/bin/gvim -> vim (also
      > gview, view, gvimdiff, vimdiff, etc., all pointing to the same binary).
      > When you invoke it as gvim (or gview, gvimdiff etc.) it will run in GUI
      > mode; when you invoke it as vim (or view, vimdiff etc.) it will run in
      > Console mode; in both cases the same options will be accepted even if
      > sometimes they won't produce any effect (e.g. 'guifont' has no effect in
      > Console mode, but it isn't an error to set it as long as your vim binary
      > is GUI-enabled). I use that method, and just tried ":set balloonexpr?"
      > in Console Vim; the answer was "  balloonexpr=", not an error message.
      >
      > Best regards,
      > Tony.
      > --
      > ... the privileged being which we call human is distinguished from
      > other animals only by certain double-edged manifestations which in
      > charity we can only call "inhuman."
      >                 -- R. A. Lafferty
      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_use" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    Your message has been successfully submitted and would be delivered to recipients shortly.