Doesnt completely kill vim

[braindigitalis]

Hi,

So I tried this and after repeatedly pressing the button vim still remains installed in /usr/bin.

The killing of vim is somewhat incomplete, can you please add a lever or second button labelled "do not push" to kill vim more completely?

[caseykneale]

I see. Yes, the current solution is infact a temporary fix! My god... what if VIM opened again and again and the horror of having to press the button followed someone forever. All it takes is to forget the keyword argument for git commit and help! This very real scenario cannot be ignored.

It may take a week or two to find the time - err - secret location to implement such a feature. Version 2 will include this for the benefit of mankind. Thank you for bringing this to my attention.

[caseykneale]

Update - a revision is being drafted by the core team as how to best handle this issue. Many of the crew haven't slept for days crafting the best solution to this problem. We are finalizing on a draft now - but please be patient (and safe from VIM), we may need to order some a new component to make this a reality.

[braindigitalis]

Whatever it takes, we must be safe from the inability to exit vim...

[TheRealBecks]

What if: whereis vim | for i in *; do chmod -x $i; done Without "x" the maleficent vim can't be executed anymore. Instead of "-x" the "000" can be used so the files can't be accessed anymore. Maybe that will break the update process as well, but maybe root can still update the files. Nevertheless we have to make sacrifices for humanity! :)

[caseykneale]

Unfortunately - VIMKillers business model was deemed unsustainable. Yes - incredibly careful thought went into constructing this device but with a wanton disregard for its ability to sustain in a modern marketplace. We encourage you to go forth with this effort as you have suggested. It could be highly effective.

The plans for VIMKiller 2.0 involved speech recognition. So if one screamed, or said "VIM" loudly it would exit all VI instances. We saw this to operate in a 2 fold manner. 1) it closes VIM if you become paralyzed with fear, 2) it would alter the psychology of those who failed to exit VIM and have formed an allegiance with it, one would learn that VIM was scary and not to be trusted. Your idea may be more practical go forth and disrupt.

[The-MAZZTer]

If this is ever revived I suggest /usr/bin/vim be replaced with a small script that tries to break out of WSL and launches notepad.

I can see no possible problems this could cause for users of this software.

[braindigitalis]

if the effort is being taken to break out of wsl, it may make sense to then scan the whole host system for vim instances and remove them. I also see no issue with this for end users. it would be a positive development.

[TheGamer1002]

Perhaps the best way to completely wipe all instances of Vim and all mentions of it would be (probably needs root):

killall -9 vim
for i in $(find / | grep vim); do
   rm -rf $i
done
for r in $(find /); do
   for l in $(grep "vim" $r); do
      rm -rf $l
   done
done

Some stuff might break, but this is a comprehensive solution to save the user from the talons of the monster known as Vim.

[caseykneale]

Perhaps the best way to completely wipe all instances of Vim and all mentions of it would be (probably needs root):

killall -9 vim
for i in $(find / | grep vim); do
   rm -rf $i
done
for r in $(find /); do
   for l in $(grep "vim" $r); do
      rm -rf $l
   done
done

Some stuff might break, but this is a comprehensive solution to save the user from the talons of the monster known as Vim.

This post demonstrates to me that you really understand what is at stake here.

[The-MAZZTer]

My previous comment suggested vim should be replaced with a script which launches Windows Notepad.

What was I thinking?

Clearly we should launch the superior text editor, Microsoft Word, instead. We can even run it through Wine on Linux.