vim breaks the fonts #54

New Issue

2014-08-01T08:31:04+02:00

emmanueltouzery commented

2014-08-01 08:31:04 +02:00

(Migrated from github.com)

built it on fedora 20, it looks great but vim breaks it. Once I start vim, characters don't appear anymore on the screen, even after exiting screen. The cursor moves and the commands are obviously executed, but no fonts are drawn anymore.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3436156-vim-breaks-the-fonts?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github).

built it on fedora 20, it looks great but vim breaks it. Once I start vim, characters don't appear anymore on the screen, even after exiting screen. The cursor moves and the commands are obviously executed, but no fonts are drawn anymore. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3436156-vim-breaks-the-fonts?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github). </bountysource-plugin>

emmanueltouzery commented

2014-08-01 08:35:08 +02:00

(Migrated from github.com)

(less and man do work)

Swordfish90 commented

2014-08-01 18:22:26 +02:00

(Migrated from github.com)

Thank you for your report. Does the problem only appear in vim or also somewhere else? This is strange because no other Fedora 20 user reported something like that. Are you using some strange hardware/setup like a VM or something like that?

emmanueltouzery commented

2014-08-01 20:05:59 +02:00

(Migrated from github.com)

You are right, it's not that simple. I think it's because I have something in my vimrc which does something to the fonts. If I start vim with:

vim -u NONE

To make it ignore my vimrc:
http://evanhahn.com/ignore-vimrc-with-vim/

Then it works... It's probably because I'm using the powerline symbols (but then also my shell is using them and it still works). Trying to isolate the setting which causes the problem...

You are right, it's not that simple. I think it's because I have something in my vimrc which does something to the fonts. If I start vim with: > vim -u NONE To make it ignore my vimrc: http://evanhahn.com/ignore-vimrc-with-vim/ Then it works... It's probably because I'm using the powerline symbols (but then also my shell is using them and it still works). Trying to isolate the setting which causes the problem...

emmanueltouzery commented

2014-08-01 20:17:47 +02:00

(Migrated from github.com)

OK I tracked it down to this setting in the .vimrc:

" bigger window by default
set lines=30 columns=110

Now yeah, I guess I can't get more lines and columns in an "antique" terminal. Maybe you could try to ignore such requests...

OK I tracked it down to this setting in the .vimrc: > " bigger window by default > set lines=30 columns=110 Now yeah, I guess I can't get more lines and columns in an "antique" terminal. Maybe you could try to ignore such requests...

coydog commented

2014-08-02 17:28:08 +02:00

(Migrated from github.com)

I experienced the same symptoms with Vim on BodhiLinux 3. In my case, the offending .vimrc entry turned out to be the following:

set columns=82

Anything larger than 68 triggers the issue in my environment. As a workaround and perhaps some insight into the cause, the issue is "fixed" per run of vim if I switch between fullscreen and window mode. Perhaps some reinitialization is happening on a fullscreen switch that needs to happen elsewhere as well. I hope this is helpful.

I experienced the same symptoms with Vim on BodhiLinux 3. In my case, the offending .vimrc entry turned out to be the following: > set columns=82 Anything larger than 68 triggers the issue in my environment. As a workaround and perhaps some insight into the cause, the issue is "fixed" per run of vim if I switch between fullscreen and window mode. Perhaps some reinitialization is happening on a fullscreen switch that needs to happen elsewhere as well. I hope this is helpful.

Swordfish90 commented

2014-08-03 15:20:30 +02:00

(Migrated from github.com)

I just tested this and I can reproduce the bug. It seems that forcing the size causes this kind of behavior. A simple window resize is a workaround at the moment. Could someone test it and see if also happens upstream? https://launchpad.net/ubuntu-terminal-app

ukn-ubi commented

2015-09-12 14:09:09 +02:00

(Migrated from github.com)

I have this problem in Arch Linux. I love Cool Retro Term by the way. 😄

I have this problem in Arch Linux. I love Cool Retro Term by the way. :smile:

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#54