Incorrect / truncated vimscript upload

[igrigorik]

Entry _id: 4d1a3c30fa85f32065000037, created_at: 2010-12-28 19:36:16 UTC, script: "\x80\xFD5:g/", score: 6

Happening on: linux/1.9.2p0

Probably something to do with an escape sequence.. Grr. What's the vimscript?

[nrocy]

Also been looking into this one, as my scores seemed too high :-P

VimGolf's score log seems to get prefixed with 3 extra bytes if you have 'set nocompatible' in your .vimrc

You can check if you're affected by noting the filename shown when you run 'vimgolf put', then 'hexdump -C' that file after Vim quits. Mine gets prefixed \x80\xFD\x35.

Analysis:

Comments in lib/vimgolf/cli.rb:67 seem to imply that -u NONE is/should be used to launch Vim, but then isn't. I'm assuming this is to retain things like 'filetype indent on', tabstop, etc.

Hack/work-around:

Copy your .vimrc to .vimrcgolf, modify it to remove 'set nocompatible' (I also had to remove pathogen stuff to avoid errors)

Modify $GEM_HOME/gems/vimgolf-0.1.1/lib/vimgolf/cli.rb
Add '-c ~/.vimrcgolf' to the param list on line 70.

Scores should be accurate now, check as above.

• Paul

[clvv]

or can we just manually check and remove \x80\xFD5 as for now?

[lmarburger]

I removed my ~/.vimrc and ~/.viminfo files and ~/.vim directory completely and my submissions are still prefixed with "\x80\xFD5".

Running OS X 10.6.5 here.

[joshtriplett]

See http://bugs.debian.org/608242 and http://groups.google.com/group/vim_dev/browse_thread/thread/9770ea844cec3282 .

You can work around this in non-GUI vim by adding "set t_RV=" to your .vimrc.

The GTK+ vim, and possibly other vim GUIs, seem to have a similar problem, though since the keystrokes arise from a different source the t_RV workaround won't help.

[igrigorik]

TERM=linux - @jordanlewis / https://github.com/igrigorik/vimgolf/issues#issue/31

Do we have a conclusion on whether it's safe to set the TERM?

[igrigorik]

3edca2f

This should do the trick. 0.1.3 now initializes vimgolf's .vimrc which should address the issue.

[joshtriplett]

Looks like vim 7.3.091 will fix this problem: http://groups.google.com/group/vim_dev/browse_thread/thread/c91310951bf30cd1

[igrigorik]

Josh, great detective work on this one! :-)