On Sat, Jun 28, 2014 at 05:44:25PM +0100, Klaus Ethgen wrote: > Hello, > > Am Sa den 28. Jun 2014 um 17:17 schrieb James McCoy: > > On Sun, Jun 22, 2014 at 02:34:06PM +0100, Klaus Ethgen wrote: > > > With the newest version I get often the error "E518: Unbekannte Option: > > > balloonexpr=" (Unknown option) when using views. > > > > > > --- real paths of main Vim binaries --- > > > /usr/bin/vi is /usr/bin/vim.nox > > > /usr/bin/vim is /usr/bin/vim.nox > > > /usr/bin/gvim is /usr/bin/vim.gtk > > > > That's because your vim alternative is pointing to vim.nox. The balloon > > eval feature is only included in Vim builds that have GUI support. > > > > When you load a view in vim.nox with 'balloonexpr' set (from a gvim > > run), it complains because that's not an option that's available in > > vim.nox. > > I never changed this setting while upgrading vim: > ~> ls -l /etc/alternatives/vim > lrwxrwxrwx 1 root root 16 Oct 20 2013 /etc/alternatives/vim -> > /usr/bin/vim.nox > > and I never ever use gvim. So this really has changed in that version > and was working before.
No, it hasn't worked in vim-nox before. I've checked all previous uploads and the source. The 'balloonexpr' functionality requires a gvim build. Since you have vim-gtk installed, that should be used for all the alternatives that the Vim packages define, so I'd guess that the vi and vim alternatives are in manual mode instead of auto mode. “update-alternatives --display vim” will confirm that. > > You can remove "options" from the 'viewoptions' option to avoid caching > > mappings/options in the view file. > > That is no solution as it removes all local set options from the view > file. > > Proper behaviour would be to ignore that setting if it is set to empty > value in view. Why would that be proper behavior? If the option is set to a non-empty value in your vimrc, plugin, etc. but at the time the view was created the option was empty, then that's relevant for restoring the view and therefore should be saved in the view file. Vim explicitly leaves options out of the view file if they don't have a buffer/window-local value set and are at their default value. That means that when your view was created, there was a buffer-local value set for 'bexpr'. The problem is purely that the view was created with a vim build that had different capabilities than the vim you're trying to restore the view with. That is something you should be informed of because that means the view is not being faithfully restored. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org