Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3404 - Vim Not Displaying Files Correctly when Using the CLI

Attached to Project: Arch Linux
Opened by Aaron Bull Schaefer (elasticdog) - Monday, 31 October 2005, 00:04 GMT
Last edited by arjan timmerman (blaasvis) - Monday, 31 October 2005, 11:23 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'm not sure if this would an upstream issue or not, but some oddities with Vim rendering files incorrectly (only the console version is affected) has crept in with the upgrade to 6.4. Everything seems to be just fine when using gVim. For specific examples and pictures of the problem, take a look at this forum thread: http://bbs.archlinux.org/viewtopic.php?t=16158
This task depends upon

Closed by  arjan timmerman (blaasvis)
Sunday, 26 March 2006, 10:29 GMT
Reason for closing:  Works for me
Comment by Judd Vinet (judd) - Tuesday, 01 November 2005, 20:22 GMT
Could you attach a text file that produces the vim weirdness?
Comment by Aaron Bull Schaefer (elasticdog) - Wednesday, 02 November 2005, 17:48 GMT
Sure thing...here's the example from my screenshot: current.new
(application/octet-stream)    current.new (0.9 KiB)
Comment by Judd Vinet (judd) - Thursday, 03 November 2005, 20:49 GMT
Strange, your example works find in my vim here. Version 6.4-2.

I tried it in aterm, xterm, and terminal.

Which terminal are you using?
Comment by Aaron Bull Schaefer (elasticdog) - Thursday, 03 November 2005, 21:52 GMT
I'm using Xfce and Terminal to load the files. I also found other examples of files that were getting cut off as well. When I get home tonight I can upload those if you like. I'll also try re-installing the vim package again to see if that makes a difference (although I haven't been the only one experiencing weirdness)
Comment by Aaron Bull Schaefer (elasticdog) - Sunday, 06 November 2005, 22:53 GMT
DOH! I think I tracked down what was causing the issue (at least mine...not the syntax stuff other people were complaining about). I had set the columns and lines options under my .vimrc file instead of moving that to the .gvimrc file where it should have been. I moved those two over and it appears that my weirdness is gone. Sorry for wasting your time...I'll let you know if I come up with any other issues. Thanks...
Comment by Alexander Baldeck (kth5) - Tuesday, 08 November 2005, 12:07 GMT
i don't think this is the cause of the real problem. a few days ago i already posted this on the forums but i put the screenshot into the attachment again.

as you can see the uppermost two lines with find in them which have a trailing "\;" cause the rest of the PKGBUILD to be highlighted incorrectlz or differently at least. by adding backsticks around each one of them i seemed to have overridden this bug.
   2005-10-29_vimbug.png (369.5 KiB)
Comment by Aaron Griffin (phrakture) - Wednesday, 08 February 2006, 00:05 GMT
Is this still an issue, if not, I'd like to close this bug - PKGBUILD syntax uses the sh.vim file, and bugs with that highlighting should be reported to the maintainer of that syntax file.

Loading...