vim doesn't terminate when terminal is forcefully closedWhy doesn't vim ask for password when reopenning an...
Is it possible to grow new organs through exposure to radioactivity?
How exactly are corporate bonds priced at issue
A continuous water "planet" ring around a star
PhD advisor lost funding, need advice
How can God warn people of the upcoming rapture without disrupting society?
Is there any way to stop a user from creating executables and running them?
Does fossil fuels use since 1990 account for half of all the fossil fuels used in history?
Why are Tucker and Malcolm not dead?
Running code generated in realtime in JavaScript with eval()
Are differences between uniformly distributed numbers uniformly distributed?
Can I enter the USA with an E-2 visa and a one way flight ticket?
80's/90's superhero cartoon with a man on fire and a man who made ice runways like Frozone
Escape Velocity - Won't the orbital path just become larger with higher initial velocity?
Can renaming a method preserve encapsulation?
Is this n-speak?
Programmatically add log information in all renderings(controller, view) html
Case Condition for two lines
(A room / an office) where an artist works
How to remove ambiguity: "... lives in the city of H, the capital of the province of NS, WHERE the unemployment rate is ..."?
Are there really no countries that protect Freedom of Speech as the United States does?
Can lodestones be used to magnetize crude iron weapons?
Why is the result of ('b'+'a'+ + 'a' + 'a').toLowerCase() 'banana'?
Flood on the top floor
Translation of "I don't have anything to smile about"
vim doesn't terminate when terminal is forcefully closed
Why doesn't vim ask for password when reopenning an encrypted file?Terminal and VimVim to print file on terminal and exitVim: x-terminal key mappingHow may I reset a buffer index on Vim?Why in “:normal”command ^[ seems doesn't work with A? (vim)Vim doesn't delete underlying lines in Visual Block ModeHow to send the ESC signal to vim when my esc key doesn't work?vim doesn't move to expected line
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
steps to replicate:
vim def.txt(as a user)- kill the terminal program
vim def.txt(as a root)- vim will ask because of existing swp file, choose edit anyway, make changes
- save then exit.
- check ps
The Vim process will then still show itself, not terminating properly. Help a confused person please?
Vim version: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2014 06:55:55)
I will answer any questions that you might ask. Sorry for the poor formatting!
vim
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 15 hours ago
NxKaiNxKai
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 1 more comment
steps to replicate:
vim def.txt(as a user)- kill the terminal program
vim def.txt(as a root)- vim will ask because of existing swp file, choose edit anyway, make changes
- save then exit.
- check ps
The Vim process will then still show itself, not terminating properly. Help a confused person please?
Vim version: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2014 06:55:55)
I will answer any questions that you might ask. Sorry for the poor formatting!
vim
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 15 hours ago
NxKaiNxKai
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hello! I dont understand what makes you believe vim still runs after step 2. I suggest when you kill the terminal at step 2, vim is killed, so the swp file stays there. Is it the root/user way of starting vim? Maybe you could just check after step 2 if vim is still running? (in which case there is a mechanism that keeps it up like nohup or something).
– Vincent Achard
15 hours ago
@VincentAchard See the last step in the list. They can see thevimprocess in thepsoutput.
– Kusalananda♦
15 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
14 hours ago
2
The process is supposed to be a child process of the shell, not the terminal. Are you killing the shell that startedvim? And who is the owner of thevimrunning at (6)?
– Philippos
14 hours ago
1
Why not usepsafter step 2 to verify whether vim is still running or not? Why go to the bother of running vim again?
– wurtel
11 hours ago
|
show 1 more comment
steps to replicate:
vim def.txt(as a user)- kill the terminal program
vim def.txt(as a root)- vim will ask because of existing swp file, choose edit anyway, make changes
- save then exit.
- check ps
The Vim process will then still show itself, not terminating properly. Help a confused person please?
Vim version: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2014 06:55:55)
I will answer any questions that you might ask. Sorry for the poor formatting!
vim
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 15 hours ago
NxKaiNxKai
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
steps to replicate:
vim def.txt(as a user)- kill the terminal program
vim def.txt(as a root)- vim will ask because of existing swp file, choose edit anyway, make changes
- save then exit.
- check ps
The Vim process will then still show itself, not terminating properly. Help a confused person please?
Vim version: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2014 06:55:55)
I will answer any questions that you might ask. Sorry for the poor formatting!
vim
vim
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 15 hours ago
NxKaiNxKai
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 15 hours ago
NxKaiNxKai
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
edited 15 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
159k18 gold badges316 silver badges502 bronze badges
asked 15 hours ago
NxKaiNxKai
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 15 hours ago
NxKaiNxKai
11 bronze badge
asked 15 hours ago
NxKaiNxKai
11 bronze badge
11 bronze badge
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
NxKai is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hello! I dont understand what makes you believe vim still runs after step 2. I suggest when you kill the terminal at step 2, vim is killed, so the swp file stays there. Is it the root/user way of starting vim? Maybe you could just check after step 2 if vim is still running? (in which case there is a mechanism that keeps it up like nohup or something).
– Vincent Achard
15 hours ago
@VincentAchard See the last step in the list. They can see thevimprocess in thepsoutput.
– Kusalananda♦
15 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
14 hours ago
2
The process is supposed to be a child process of the shell, not the terminal. Are you killing the shell that startedvim? And who is the owner of thevimrunning at (6)?
– Philippos
14 hours ago
1
Why not usepsafter step 2 to verify whether vim is still running or not? Why go to the bother of running vim again?
– wurtel
11 hours ago
|
show 1 more comment
Hello! I dont understand what makes you believe vim still runs after step 2. I suggest when you kill the terminal at step 2, vim is killed, so the swp file stays there. Is it the root/user way of starting vim? Maybe you could just check after step 2 if vim is still running? (in which case there is a mechanism that keeps it up like nohup or something).
– Vincent Achard
15 hours ago
@VincentAchard See the last step in the list. They can see thevimprocess in thepsoutput.
– Kusalananda♦
15 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
14 hours ago
2
The process is supposed to be a child process of the shell, not the terminal. Are you killing the shell that startedvim? And who is the owner of thevimrunning at (6)?
– Philippos
14 hours ago
1
Why not usepsafter step 2 to verify whether vim is still running or not? Why go to the bother of running vim again?
– wurtel
11 hours ago
Hello! I dont understand what makes you believe vim still runs after step 2. I suggest when you kill the terminal at step 2, vim is killed, so the swp file stays there. Is it the root/user way of starting vim? Maybe you could just check after step 2 if vim is still running? (in which case there is a mechanism that keeps it up like nohup or something).
– Vincent Achard
15 hours ago
Hello! I dont understand what makes you believe vim still runs after step 2. I suggest when you kill the terminal at step 2, vim is killed, so the swp file stays there. Is it the root/user way of starting vim? Maybe you could just check after step 2 if vim is still running? (in which case there is a mechanism that keeps it up like nohup or something).
– Vincent Achard
15 hours ago
@VincentAchard See the last step in the list. They can see the
vim process in the ps output.– Kusalananda♦
15 hours ago
@VincentAchard See the last step in the list. They can see the
vim process in the ps output.– Kusalananda♦
15 hours ago
2
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
14 hours ago
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
14 hours ago
2
2
The process is supposed to be a child process of the shell, not the terminal. Are you killing the shell that started
vim? And who is the owner of the vim running at (6)?– Philippos
14 hours ago
The process is supposed to be a child process of the shell, not the terminal. Are you killing the shell that started
vim? And who is the owner of the vim running at (6)?– Philippos
14 hours ago
1
1
Why not use
ps after step 2 to verify whether vim is still running or not? Why go to the bother of running vim again?– wurtel
11 hours ago
Why not use
ps after step 2 to verify whether vim is still running or not? Why go to the bother of running vim again?– wurtel
11 hours ago
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
NxKai is a new contributor. Be nice, and check out our Code of Conduct.
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%2funix.stackexchange.com%2fquestions%2f535307%2fvim-doesnt-terminate-when-terminal-is-forcefully-closed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
NxKai is a new contributor. Be nice, and check out our Code of Conduct.
NxKai is a new contributor. Be nice, and check out our Code of Conduct.
NxKai is a new contributor. Be nice, and check out our Code of Conduct.
NxKai is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f535307%2fvim-doesnt-terminate-when-terminal-is-forcefully-closed%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
Hello! I dont understand what makes you believe vim still runs after step 2. I suggest when you kill the terminal at step 2, vim is killed, so the swp file stays there. Is it the root/user way of starting vim? Maybe you could just check after step 2 if vim is still running? (in which case there is a mechanism that keeps it up like nohup or something).
– Vincent Achard
15 hours ago
@VincentAchard See the last step in the list. They can see the
vimprocess in thepsoutput.– Kusalananda♦
15 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
14 hours ago
2
The process is supposed to be a child process of the shell, not the terminal. Are you killing the shell that started
vim? And who is the owner of thevimrunning at (6)?– Philippos
14 hours ago
1
Why not use
psafter step 2 to verify whether vim is still running or not? Why go to the bother of running vim again?– wurtel
11 hours ago