Possible Vim Bug? (Only CLI)

elasticdog · 2005-10-28 21:48:42

My Vim/gVim packages (v6.4-2) were updated on Oct 27th, and today I've noticed something weird when I use <code>vim</code> under the command line. I was sorting the mirrors list for pacman, which worked fine, but then looking at the list with <code>vim</code>, the file is all messed up. Using <code>less</code> to read the file works just fine, as does using gVim under Xfce. Take a look at my screenshot:

Should this be filed as a bug report? Can anyone else reproduce something similar?

T-Dawg · 2005-10-28 22:02:35

I don't see whats wrong with it

elasticdog · 2005-10-28 22:39:37

In the screenshot, both gVim (on the right) and Vim (in the Terminal on the left) are looking at the exact same file. They are both on the first line, and as you can see the command line version is missing all sorts of stuff...basically it has cut off the top portion of the file, and you can't scroll up to see them.

I'm also able to navigate below the 9th line (counting from the screenshot) and have the cursor on the lines starting with tildes, which should not be happening.

smoon · 2005-10-28 22:40:39

I've experienced similar behaviour a week or so ago. But as far as I can recall it only happened with this one file. I use vim everyday and it worked just fine in the last week.

kth5 · 2005-10-29 00:22:53

same here, something definetly wrong with vim's syntax highlighting:
Screenshot

In the lower Konsole i "corrected" the highlighting by putting backsticks around the lines with find, in the top one not. look at binutils's configure arguments.

elasticdog · 2005-10-29 05:22:59

That is strange...is this possibly an upstream issue? Do you have the same problem in gVim? I'm fairly sure that the 6.4 release was just for bugfixes...odd that this kind of a problem would creep in.

elasticdog · 2005-10-30 22:05:16

Admittedly, I'm not smart enough to determine if this is an Arch-centric issue, or something that is upstream...but it's definitely not just my machine. Any thoughts from someone more "in the know"?

kth5 · 2005-10-30 22:58:21

should be enough for a reason to file a bug so that the maintainer can take care of it.

phrakture · 2005-10-31 08:01:26

bah, just use vim-unstable! it's vim7, and neri is handling it, so I no longer have to in [community] (but I used to)

elasticdog · 2005-11-07 07:03:39

Doh!!! I filed a bug report and eventually tracked down what the issue was. I had accidentally set the lines and columns settings under .vimrc instead of their proper place in .gvimrc which confused the command-line version of Vim.

That doesn't explain the syntax issues that kth5 was having, but it looks like it's taken care of all my problems for the time being...

Arch Linux

#1 2005-10-28 21:48:42

Possible Vim Bug? (Only CLI)

#2 2005-10-28 22:02:35

Re: Possible Vim Bug? (Only CLI)

#3 2005-10-28 22:39:37

Re: Possible Vim Bug? (Only CLI)

#4 2005-10-28 22:40:39

Re: Possible Vim Bug? (Only CLI)

#5 2005-10-29 00:22:53

Re: Possible Vim Bug? (Only CLI)

#6 2005-10-29 05:22:59

Re: Possible Vim Bug? (Only CLI)

#7 2005-10-30 22:05:16

Re: Possible Vim Bug? (Only CLI)

#8 2005-10-30 22:58:21

Re: Possible Vim Bug? (Only CLI)

#9 2005-10-31 08:01:26

Re: Possible Vim Bug? (Only CLI)

#10 2005-11-07 07:03:39

Re: Possible Vim Bug? (Only CLI)

Board footer