Vim does not redraw appropriately in Ubuntu18.04
I am using vim with youcompleteme plugin in terminal in Ubuntu 18.04. Every time the plugin triggers a diagnostic error, the current window has not been redrawn thoroughly. As you can see here
the signcolumn and cursorcolumn are broken. This status will last about 2~3 seconds if I don't press keyboard to fire redraw event.
My .vimrc config file was copied from my Ubuntu16.04 system, and working perfectly there. I also have that config file tested in Debian9 system, and found nothing abnormal.
Could someone give me a clue on it? I would appreciate any help:)
18.04 vim
asked Dec 15 at 15:44
Ngui Siautien
11
add a comment |
I am using vim with youcompleteme plugin in terminal in Ubuntu 18.04. Every time the plugin triggers a diagnostic error, the current window has not been redrawn thoroughly. As you can see here
the signcolumn and cursorcolumn are broken. This status will last about 2~3 seconds if I don't press keyboard to fire redraw event.
My .vimrc config file was copied from my Ubuntu16.04 system, and working perfectly there. I also have that config file tested in Debian9 system, and found nothing abnormal.
Could someone give me a clue on it? I would appreciate any help:)
18.04 vim
asked Dec 15 at 15:44
Ngui Siautien
11
I found a funny thing that if I start vim with command 'vim -V9myVim.log' which means that a log of debug level 9 would be created in the current directory everything would be working perfectly.
– Ngui Siautien
Dec 16 at 1:25
I guess it might be caused by the gtk library since nothing went wrong before the installation of vim-gtk (for clipboard-copy-paste supporting).
– Ngui Siautien
Dec 16 at 2:54
Use the steps in vi.stackexchange.com/a/2004/205 to see if some other plugin is interfering. Was your 16.04 system using them same version of Vim as the Debian 9 one or the 18.04 one? Have you tried using a newer version (say, from this PPA), orvim-nox?
– muru
Dec 17 at 2:09
add a comment |
I am using vim with youcompleteme plugin in terminal in Ubuntu 18.04. Every time the plugin triggers a diagnostic error, the current window has not been redrawn thoroughly. As you can see here
the signcolumn and cursorcolumn are broken. This status will last about 2~3 seconds if I don't press keyboard to fire redraw event.
My .vimrc config file was copied from my Ubuntu16.04 system, and working perfectly there. I also have that config file tested in Debian9 system, and found nothing abnormal.
Could someone give me a clue on it? I would appreciate any help:)
18.04 vim
asked Dec 15 at 15:44
Ngui Siautien
11
I am using vim with youcompleteme plugin in terminal in Ubuntu 18.04. Every time the plugin triggers a diagnostic error, the current window has not been redrawn thoroughly. As you can see here
the signcolumn and cursorcolumn are broken. This status will last about 2~3 seconds if I don't press keyboard to fire redraw event.
My .vimrc config file was copied from my Ubuntu16.04 system, and working perfectly there. I also have that config file tested in Debian9 system, and found nothing abnormal.
Could someone give me a clue on it? I would appreciate any help:)
18.04 vim
18.04 vim
asked Dec 15 at 15:44
Ngui Siautien
11
asked Dec 15 at 15:44
Ngui Siautien
11
edited Dec 17 at 3:18
asked Dec 15 at 15:44
Ngui Siautien
11
asked Dec 15 at 15:44
Ngui Siautien
11
asked Dec 15 at 15:44
Ngui Siautien
11
11
I found a funny thing that if I start vim with command 'vim -V9myVim.log' which means that a log of debug level 9 would be created in the current directory everything would be working perfectly.
– Ngui Siautien
Dec 16 at 1:25
I guess it might be caused by the gtk library since nothing went wrong before the installation of vim-gtk (for clipboard-copy-paste supporting).
– Ngui Siautien
Dec 16 at 2:54
Use the steps in vi.stackexchange.com/a/2004/205 to see if some other plugin is interfering. Was your 16.04 system using them same version of Vim as the Debian 9 one or the 18.04 one? Have you tried using a newer version (say, from this PPA), orvim-nox?
– muru
Dec 17 at 2:09
add a comment |
I found a funny thing that if I start vim with command 'vim -V9myVim.log' which means that a log of debug level 9 would be created in the current directory everything would be working perfectly.
– Ngui Siautien
Dec 16 at 1:25
I guess it might be caused by the gtk library since nothing went wrong before the installation of vim-gtk (for clipboard-copy-paste supporting).
– Ngui Siautien
Dec 16 at 2:54
Use the steps in vi.stackexchange.com/a/2004/205 to see if some other plugin is interfering. Was your 16.04 system using them same version of Vim as the Debian 9 one or the 18.04 one? Have you tried using a newer version (say, from this PPA), orvim-nox?
– muru
Dec 17 at 2:09
I found a funny thing that if I start vim with command 'vim -V9myVim.log' which means that a log of debug level 9 would be created in the current directory everything would be working perfectly.
– Ngui Siautien
Dec 16 at 1:25
I found a funny thing that if I start vim with command 'vim -V9myVim.log' which means that a log of debug level 9 would be created in the current directory everything would be working perfectly.
– Ngui Siautien
Dec 16 at 1:25
I guess it might be caused by the gtk library since nothing went wrong before the installation of vim-gtk (for clipboard-copy-paste supporting).
– Ngui Siautien
Dec 16 at 2:54
I guess it might be caused by the gtk library since nothing went wrong before the installation of vim-gtk (for clipboard-copy-paste supporting).
– Ngui Siautien
Dec 16 at 2:54
Use the steps in vi.stackexchange.com/a/2004/205 to see if some other plugin is interfering. Was your 16.04 system using them same version of Vim as the Debian 9 one or the 18.04 one? Have you tried using a newer version (say, from this PPA), or
vim-nox?– muru
Dec 17 at 2:09
Use the steps in vi.stackexchange.com/a/2004/205 to see if some other plugin is interfering. Was your 16.04 system using them same version of Vim as the Debian 9 one or the 18.04 one? Have you tried using a newer version (say, from this PPA), or
vim-nox?– muru
Dec 17 at 2:09
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102105%2fvim-does-not-redraw-appropriately-in-ubuntu18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102105%2fvim-does-not-redraw-appropriately-in-ubuntu18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I found a funny thing that if I start vim with command 'vim -V9myVim.log' which means that a log of debug level 9 would be created in the current directory everything would be working perfectly.
– Ngui Siautien
Dec 16 at 1:25
I guess it might be caused by the gtk library since nothing went wrong before the installation of vim-gtk (for clipboard-copy-paste supporting).
– Ngui Siautien
Dec 16 at 2:54
Use the steps in vi.stackexchange.com/a/2004/205 to see if some other plugin is interfering. Was your 16.04 system using them same version of Vim as the Debian 9 one or the 18.04 one? Have you tried using a newer version (say, from this PPA), or
vim-nox?– muru
Dec 17 at 2:09