search

edenzik / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

NFO Formatting #189

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When following http://vim.wikia.com/wiki/View_NFO-files_correctly ie trying
to open a *.nfo file with the cp437 encoding I come across these problems.

Picture 1 is the terminal VIM application running correctly, that is
included in MacOSX.

Picture 2 is the error I get in MacVim 7.2.209,

Picture 3 is what happens when I press a key on the error.

Picture 4 is what the file should look like in MacVim, this occurs with
7.2.0 Stable release.

Picture 5 is the error that does flash before Picture 4 in 7.2.0 Stable.
Note it differs from Picture 2 as it does not contain the [ILLEGAL BYTE in
line 1]

nfo.nfo.zip is a sample NFO file with some cp437 characters.

Original issue reported on code.google.com by dcecc...@gmail.com on 30 Jun 2009 at 2:22

Attachments:

GoogleCodeExporter commented 9 years ago 
I cannot reproduce this problem (I've tried snap 45 and stable 1.2) and from 
the fact that you get error messages 
when you try to open an nfo file I am guessing the problem is with your 
.vimrc/.gvimrc.

Please try renaming your .vimrc/.gvimrc and .vim folder and create a new .vimrc 
only containing the lines from 
the vim wikia page you linked to, quit MacVim and try again (make sure you 
copy/paste from that page so that 
you are sure there are no typos).

Original comment by bjorn.winckler@gmail.com on 1 Jul 2009 at 2:57

GoogleCodeExporter commented 9 years ago 
~/.vim does not exist as I've got no scripts/plugins/colorschemes/syntax 
highlights
or anything installed.

Renaming .vimrc and .gvimrc didn't help. My configs are pretty basic.

.gvimrc only has:
set bg=dark

and

.vimrc:

" Other startup commands
set lbr!
syntax enable
set cursorline
set nu
colorscheme macvim
set guifont=Monaco:h15

Original comment by dcecc...@gmail.com on 1 Jul 2009 at 7:57

GoogleCodeExporter commented 9 years ago 
Hmmm...strange that I can't repro over here.

Please tell me step-by-step how you start MacVim to repro the bug and attach 
your .vimrc/.gvimrc files as 
well so that I can try with exactly the same setup.

Before doing that however, please reset your preferences for MacVim and try 
again.  First quit MacVim and 
then in Terminal enter:

defaults delete org.vim.MacVim

Then try reproducing the bug.  Note that this step will erase any settings you 
have made in the Preferences 
panel in MacVim (so it will ask you about automatic updates etc. when you 
restart).

Original comment by bjorn.winckler@gmail.com on 2 Jul 2009 at 3:25

GoogleCodeExporter commented 9 years ago 
Hi,

Sorry for the late reply, I've been overloaded with work and out of the country 
for a
while.

To reproduce this bug, which it still occurs in 7.2.234

1. Run in terminal "defaults delete org.vim.MacVim"
2. Use supplied .gvimrc and .vimrc
3. Open the .nfo file attached.

Original comment by dcecc...@gmail.com on 10 Aug 2009 at 4:16

Attachments:

GoogleCodeExporter commented 9 years ago 
Hmmm...using your rc files I still have no problems with rendering.  I do get 
the warning messages (not about 
"ILLEGAL BYTE" though), but I guess that is because of a problem with the 
script (sorry, I know next to nothing 
about Vim script).

Are you still getting the "ILLEGAL BYTE" warning?  I guess this must be the 
root of the problem but I do not 
understand what it means.  Does the problem persist if you copy&past and save 
the nfo to a new file?  Are you 
having the same problem with every nfo file you open or just the one?

Do you have access to GVim on any other platform that you could try with?

Original comment by bjorn.winckler@gmail.com on 10 Aug 2009 at 9:00

GoogleCodeExporter commented 9 years ago 
Since I can be of so little help here I suggest you try asking on the vim_use 
mailing list.  Somebody there may 
understand what is going on with the "ILLEGAL BYTE" issue.  (As far as I can 
tell this is not really a MacVim 
specific issue.)

Original comment by bjorn.winckler@gmail.com on 10 Aug 2009 at 9:33

GoogleCodeExporter commented 9 years ago 
I'm not getting ILLEGAL BYTE messages with 7.2.234 but it does say:

Error detected while processing function RestoreFileEncodings:
line 1:
E121: Undefined variable: b:myfileencodingsbak
E15: Invalid expression b:myfileencodingsbak
line 2:
E108: No such variable: "b:myfileencodingsbak"

I tested this in Ubuntu 9.04 with GVIM 7.2.79, seems to work perfectly.

Original comment by dcecc...@gmail.com on 11 Aug 2009 at 6:58

GoogleCodeExporter commented 9 years ago 
...but you still get question marks (as in Picture 3) instead of properly 
rendered
"squares"?  Or are they gone as well?

I still urge you to ask on vim_use why you get those error messages...I can't 
answer
that question.

Original comment by bjorn.winckler@gmail.com on 11 Aug 2009 at 8:43

GoogleCodeExporter commented 9 years ago 
No they render as the squares (as they should) in both cases the only reason I
thought it was a MacVim error was because it worked in vim console and in gvim
perfectly on both windows and linux platforms. It's likely because of this the 
vim
guys won't be too interested as vim/gvim is what they distribute.

Original comment by dcecc...@gmail.com on 12 Aug 2009 at 7:14

GoogleCodeExporter commented 9 years ago 
This is some kind of problem with Vim...I just tested with GVim on Windows XP 
and it
also spews out the same warning message about an undefined variable.  Again: 
please
bring this topic up on the vim_use list.

Original comment by bjorn.winckler@gmail.com on 21 Aug 2009 at 7:26

GoogleCodeExporter commented 9 years ago 
My _vimrc config for windows and a screenshot of the result in windows.

This was using the official Vim 7.2 distribution from 
http://www.vim.org/download.php

(Strangely enough I thought it worked in windows, perhaps I was mistaken and it 
was
only in Linux.

Original comment by dcecc...@gmail.com on 19 Sep 2009 at 7:16

Attachments:

GoogleCodeExporter commented 9 years ago 
I posted a message about this on the Vim-Dev mailing list >
http://groups.google.com/group/vim_dev/browse_thread/thread/c5add9d5065fc38?hl=e
n

Original comment by dcecc...@gmail.com on 19 Sep 2009 at 7:40

GoogleCodeExporter commented 9 years ago 
The error is due to the fact that I switched from using a case sensitive 
filesystem
(HFSX/EXT/ZFS) where that configuration works correctly, ie 
Linux/Solaris/MacOSX.

Ofcourse in Windows with NTFS or with HFS+ it's not required to have an entry 
for
both cases.

Removing it causes everything to work fine.

Original comment by dcecc...@gmail.com on 21 Sep 2009 at 11:28

GoogleCodeExporter commented 9 years ago

Original comment by bjorn.winckler@gmail.com on 28 Nov 2009 at 6:19