vim doesn't terminate when terminal is forcefully closedWhy doesn't vim ask for password when reopenning an...
How to find directories containing only specific files
How much can I judge a company based on a phone screening?
Boss asked a co-worker to assault me
How far did Gandalf and the Balrog drop from the bridge in Moria?
Can the IPA represent all languages' tones?
Using hearing aids on the sabbath?
Why did IBM make public the PC BIOS source code?
Can renaming a method preserve encapsulation?
Why did Saruman lie?
Case Condition for two lines
Is there any way to stop a user from creating executables and running them?
Is there a way to encourage or even force airlines and booking engines to show options with overnight layovers?
Does EU compensation apply to flights where the departure airport closes check-in counters during protests?
What kind of liquid can be seen 'leaking' from the upper surface of the wing of a Boeing 737-800?
Why aren't rockets built with truss structures inside their fuel & oxidizer tanks to increase structural strength?
How big are the Choedan Kal?
What can Amex do if I cancel their card after using the sign up bonus miles?
Do beef farmed pastures net remove carbon emissions?
Why is the Lucas test not recommended to differentiate higher alcohols?
Are those flyers about apartment purchase a scam?
Is there a SQL/English like language that lets you define formulations given some data?
How do I call a 6 digit Austrailian phone number with a US based mobile phone?
Does Nightpack Ambusher's second ability trigger if I cast spells during the end step?
If you know the location of an invisible creature, can you attack it?
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 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 18 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 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 18 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
18 hours ago
@VincentAchard See the last step in the list. They can see thevimprocess in thepsoutput.
– Kusalananda♦
18 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
17 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
17 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
14 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 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 18 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 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 18 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 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
asked 18 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 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
edited 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
edited 18 hours ago
Kusalananda♦
159k18 gold badges316 silver badges502 bronze badges
159k18 gold badges316 silver badges502 bronze badges
asked 18 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 18 hours ago
NxKaiNxKai
11 bronze badge
asked 18 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
18 hours ago
@VincentAchard See the last step in the list. They can see thevimprocess in thepsoutput.
– Kusalananda♦
18 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
17 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
17 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
14 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
18 hours ago
@VincentAchard See the last step in the list. They can see thevimprocess in thepsoutput.
– Kusalananda♦
18 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
17 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
17 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
14 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
18 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
18 hours ago
@VincentAchard See the last step in the list. They can see the
vim process in the ps output.– Kusalananda♦
18 hours ago
@VincentAchard See the last step in the list. They can see the
vim process in the ps output.– Kusalananda♦
18 hours ago
2
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
17 hours ago
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
17 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
17 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
17 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
14 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
14 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
18 hours ago
@VincentAchard See the last step in the list. They can see the
vimprocess in thepsoutput.– Kusalananda♦
18 hours ago
2
How did you kill the terminal program? Depending on that, it may or may not kill child processes.
– muru
17 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
17 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
14 hours ago