Bug 185645 - Vim is not usable in Konsole
Summary: Vim is not usable in Konsole
Status: RESOLVED DUPLICATE of bug 238073
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-26 21:06 UTC by icefox
Modified: 2011-07-30 14:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description icefox 2009-02-26 21:06:58 UTC
Version:           2.2 (using KDE 4.2.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Launching vim in Konsole (4.2.0 packages) it will not paint the text on the screen.  All I will see is ~ all on the left hand side, if I hit i and start typing in text the cursor will move across the scree, but the text will not appear.  If I drag highlight the screen I will be able to see the text.  Resizing the screen solves the issue.  It seems like vim thinks that the terminal is twice the height or something that it actually is and it is painting farther up or konsole is only painting row+80 or something odd from the fact that if I drag highlight I can scroll up to get to the text.
Comment 1 Robert Knight 2009-02-27 13:54:21 UTC
Works for me on my system.  Does resizing the terminal window fix the problem?
Comment 2 icefox 2009-02-27 16:43:45 UTC
Yes every single time vim is launched I resize the konsole window slightly with the mouse to fix it.  I had the same problem in 4.1 and am surprised it was in 4.2 still.  It makes using Konsole.  Being a vim guy you can probably guess how annoying this is ;)  Is there anything I can test on my system or more information I can provide?
Comment 3 Robert Knight 2009-02-27 18:00:13 UTC
> I had the same problem in 4.1 and am surprised it was in 4.2 still

You're the first to report it - so whatever caused the problem then is probably the same now.

> Is there anything I can test on my system or more
> information I can provide?

Before you start Vim, does "echo $COLUMNS" and "echo $ROWS" in the shell produce correct values?
Comment 4 icefox 2009-02-27 18:55:11 UTC
$ROWS is empty and $COLUMNS says 132 which looks about right
Comment 5 Robert Knight 2009-02-27 20:17:02 UTC
Sorry, I meant $LINES and $COLUMNS, not $ROWS
Comment 6 icefox 2009-02-27 20:45:35 UTC
$LINES returns 44 which looks correct

btw I am icefox on freenode
Comment 7 icefox 2009-03-27 23:50:33 UTC
Upgrade to 4.2.1 and still seeing the issue.
Comment 8 icefox 2009-03-28 00:25:37 UTC
To reproduce the issue add "set columns=100" to your .vimrc.  Once I removed that then I am able to use vim in konsole.
Comment 9 Jekyll Wu 2011-07-30 14:17:48 UTC

*** This bug has been marked as a duplicate of bug 238073 ***