Vim periodically reverts to system version
(I am running Xubuntu 18.10.)
I want clipboard support in my Vim, which isn't present in the vim package in apt, so I compiled Vim myself with +clipboard. I then proceeded to install it using checkinstall. This works fine.
However, after some time, I will notice my Vim no longer supports the clipboard. vim --version shows -clipboard; it's clear that it has reverted to the system version.
What could be causing this? Where can I look to figure out what is making my installed version disappear? checkinstall produces a .deb file which I can install using the Software GUI app; but when it reverts, (my build of) Vim is no longer listed as installed in that app.
I am experiencing another issue with something happening periodically, which I include here only because it might be relevant. I have set proxy variables in various places including /etc/environment and /etc/profile.d/office_proxy.sh, because I need these for the office. When at home, I will typically manually go and comment all of these out & relog to disable the proxy. However, some time after logging in, the proxy variables will reinstate themselves. I'm 99% certain it's not a script of mine that is setting the proxy; I suspect Xubuntu is doing this somehow. Again, I only mention this here because this is another seemingly time-based behaviour.
apt xubuntu vim clipboard
asked Jan 28 at 8:03
henrebothahenrebotha
1035
add a comment |
(I am running Xubuntu 18.10.)
I want clipboard support in my Vim, which isn't present in the vim package in apt, so I compiled Vim myself with +clipboard. I then proceeded to install it using checkinstall. This works fine.
However, after some time, I will notice my Vim no longer supports the clipboard. vim --version shows -clipboard; it's clear that it has reverted to the system version.
What could be causing this? Where can I look to figure out what is making my installed version disappear? checkinstall produces a .deb file which I can install using the Software GUI app; but when it reverts, (my build of) Vim is no longer listed as installed in that app.
I am experiencing another issue with something happening periodically, which I include here only because it might be relevant. I have set proxy variables in various places including /etc/environment and /etc/profile.d/office_proxy.sh, because I need these for the office. When at home, I will typically manually go and comment all of these out & relog to disable the proxy. However, some time after logging in, the proxy variables will reinstate themselves. I'm 99% certain it's not a script of mine that is setting the proxy; I suspect Xubuntu is doing this somehow. Again, I only mention this here because this is another seemingly time-based behaviour.
apt xubuntu vim clipboard
asked Jan 28 at 8:03
henrebothahenrebotha
1035
2
It looks like it might just be apt "upgrading" my Vim to the apt version. I have appliedapt-mark hold vim; let's see if that fixes the problem.
– henrebotha
Jan 28 at 8:16
If you know the solution, then you should add it as answer and accept it.
– Ralf
Jan 29 at 21:13
add a comment |
(I am running Xubuntu 18.10.)
I want clipboard support in my Vim, which isn't present in the vim package in apt, so I compiled Vim myself with +clipboard. I then proceeded to install it using checkinstall. This works fine.
However, after some time, I will notice my Vim no longer supports the clipboard. vim --version shows -clipboard; it's clear that it has reverted to the system version.
What could be causing this? Where can I look to figure out what is making my installed version disappear? checkinstall produces a .deb file which I can install using the Software GUI app; but when it reverts, (my build of) Vim is no longer listed as installed in that app.
I am experiencing another issue with something happening periodically, which I include here only because it might be relevant. I have set proxy variables in various places including /etc/environment and /etc/profile.d/office_proxy.sh, because I need these for the office. When at home, I will typically manually go and comment all of these out & relog to disable the proxy. However, some time after logging in, the proxy variables will reinstate themselves. I'm 99% certain it's not a script of mine that is setting the proxy; I suspect Xubuntu is doing this somehow. Again, I only mention this here because this is another seemingly time-based behaviour.
apt xubuntu vim clipboard
asked Jan 28 at 8:03
henrebothahenrebotha
1035
(I am running Xubuntu 18.10.)
I want clipboard support in my Vim, which isn't present in the vim package in apt, so I compiled Vim myself with +clipboard. I then proceeded to install it using checkinstall. This works fine.
However, after some time, I will notice my Vim no longer supports the clipboard. vim --version shows -clipboard; it's clear that it has reverted to the system version.
What could be causing this? Where can I look to figure out what is making my installed version disappear? checkinstall produces a .deb file which I can install using the Software GUI app; but when it reverts, (my build of) Vim is no longer listed as installed in that app.
I am experiencing another issue with something happening periodically, which I include here only because it might be relevant. I have set proxy variables in various places including /etc/environment and /etc/profile.d/office_proxy.sh, because I need these for the office. When at home, I will typically manually go and comment all of these out & relog to disable the proxy. However, some time after logging in, the proxy variables will reinstate themselves. I'm 99% certain it's not a script of mine that is setting the proxy; I suspect Xubuntu is doing this somehow. Again, I only mention this here because this is another seemingly time-based behaviour.
apt xubuntu vim clipboard
apt xubuntu vim clipboard
asked Jan 28 at 8:03
henrebothahenrebotha
1035
asked Jan 28 at 8:03
henrebothahenrebotha
1035
asked Jan 28 at 8:03
henrebothahenrebotha
1035
asked Jan 28 at 8:03
henrebothahenrebotha
1035
asked Jan 28 at 8:03
henrebothahenrebotha
1035
1035
2
It looks like it might just be apt "upgrading" my Vim to the apt version. I have appliedapt-mark hold vim; let's see if that fixes the problem.
– henrebotha
Jan 28 at 8:16
If you know the solution, then you should add it as answer and accept it.
– Ralf
Jan 29 at 21:13
add a comment |
2
It looks like it might just be apt "upgrading" my Vim to the apt version. I have appliedapt-mark hold vim; let's see if that fixes the problem.
– henrebotha
Jan 28 at 8:16
If you know the solution, then you should add it as answer and accept it.
– Ralf
Jan 29 at 21:13
2
2
It looks like it might just be apt "upgrading" my Vim to the apt version. I have applied
apt-mark hold vim; let's see if that fixes the problem.– henrebotha
Jan 28 at 8:16
It looks like it might just be apt "upgrading" my Vim to the apt version. I have applied
apt-mark hold vim; let's see if that fixes the problem.– henrebotha
Jan 28 at 8:16
If you know the solution, then you should add it as answer and accept it.
– Ralf
Jan 29 at 21:13
If you know the solution, then you should add it as answer and accept it.
– Ralf
Jan 29 at 21:13
add a comment |
1 Answer
1
active
oldest
votes
This was caused by apt overriding my own version of Vim whenever I ran it. The solution was to use apt-mark hold vim to tell apt not to try to upgrade Vim.
answered Feb 11 at 13:29
henrebothahenrebotha
1035
add a comment |
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%2f1113456%2fvim-periodically-reverts-to-system-version%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This was caused by apt overriding my own version of Vim whenever I ran it. The solution was to use apt-mark hold vim to tell apt not to try to upgrade Vim.
answered Feb 11 at 13:29
henrebothahenrebotha
1035
add a comment |
This was caused by apt overriding my own version of Vim whenever I ran it. The solution was to use apt-mark hold vim to tell apt not to try to upgrade Vim.
answered Feb 11 at 13:29
henrebothahenrebotha
1035
add a comment |
This was caused by apt overriding my own version of Vim whenever I ran it. The solution was to use apt-mark hold vim to tell apt not to try to upgrade Vim.
answered Feb 11 at 13:29
henrebothahenrebotha
1035
This was caused by apt overriding my own version of Vim whenever I ran it. The solution was to use apt-mark hold vim to tell apt not to try to upgrade Vim.
answered Feb 11 at 13:29
henrebothahenrebotha
1035
answered Feb 11 at 13:29
henrebothahenrebotha
1035
answered Feb 11 at 13:29
henrebothahenrebotha
1035
answered Feb 11 at 13:29
henrebothahenrebotha
1035
1035
add a comment |
add a comment |
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.
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%2f1113456%2fvim-periodically-reverts-to-system-version%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
2
It looks like it might just be apt "upgrading" my Vim to the apt version. I have applied
apt-mark hold vim; let's see if that fixes the problem.– henrebotha
Jan 28 at 8:16
If you know the solution, then you should add it as answer and accept it.
– Ralf
Jan 29 at 21:13