-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 � wrote: > On Sep 19, 9:27�am, David C <[email protected]> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I've discovered this problem with Vim in relation to NFO formatting. >> >> I won't post the whole contents of the bug here, because there were >> attachments and tests. >> >> When followinghttp://vim.wikia.com/wiki/View_NFO-files_correctlyie >> trying to open a *.nfo file with the cp437 encoding I come across these >> problems regarding undefined variables: >> >> http://code.google.com/p/macvim/issues/detail?id=189 >> >> Note initially I thought it was a MacVim problem (and yes this isn't an >> official distribution of Vim but, I then later discovered it occurs with >> the Windows version too, but not on Ubuntu. >> >> - -David > > This explanation applies to Windows. > > You have two autocmds (one for *.nfo and one for *.NFO) which both > (unnecessarily) try to unlet b:myfileencodings. This works on Ubuntu > because file names are case sensitive on Linux. If you're seeing > different behaviour on different versions of MacVim, that probably > means they changed something in how case in file names is treated - > this is just a guess, I don't really know. > > Also, this is a question for vim_use, as Bj�rn suggested. > > Henrik. > > >
ah, yeah it works if you remove that other case. I must have forgotten that I disabled HFSX (Case Sensitive HFS). Too used to EXT and ZFS. :) Thanks. - -David -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) iEYEARECAAYFAkq3YboACgkQ0eSIJfL+k/hfZgCeNl/ARv8qQM/5LrvPbwVkvgK0 iVwAn2kQhsAO6BHmaWMXNruTokolxz28 =PQvh -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
