No one can exit vim. It's simply not possible.
There are even legends that the devil himself was onced tricked into opening vim and is stuck there since.
No one can exit vim. It's simply not possible.
There are even legends that the devil himself was onced tricked into opening vim and is stuck there since.
This is the closest I have seen Copilot doing something like a human Programmer would
What if my PC boots straight into Vim? It's not like I need anything else, can do everything in Vim
Jokes aside, vim as PID 1 is just a bad idea.
Emacs on the other hand: https://github.com/emacs-os/el-init
Oh it's like Zombo?
Zombo.com
You simply need to set up a MCP server which controls the smart plug and give the AI access to it.
This is how we trap it. This is how we win.
Are you sure? It looks like this is going "Hey, I can't get the front door open to the house, so I called the cops and told them I was being held hostage so they would break down the door with a battering ram."
How long is it before CoPilot can't exit vim and just deletes vim as the solution?
Instructions: "Next, open the .config file in vim..."
Me:

What a weird way to spell nano
Nano is the proper tool for this job.
I prefer micro, but I never use it because my brain just autotypes nano and then it's too late I'm already in
Why :wq doesnt work?
If itβs a read only file it wonβt work, but it might be in insert mode and canβt escape.
It should have tried :q!
I think it might not be vim.
It's started something on a terminal. It is assuming it's vim, but it's not operating like vim. I'm questioning it's assumption. If it had fired up nano, for example, sending vim key sequences isn't going to work. Seeing as it seems to be doing stuff with git too, it may not have started this editor explicitly. It will be using whatever git is configured to use.
Could be in recording mode, which usually needs a couple ESC or a Q then you can :wq
You mean EX mode? IIRC recording mode doesn't prevent exiting vim
Nah, just looked it up. Recording mode is activated by pressing "q" and allows you to record your inputs for a macro. So if you forget to do ":" and just press "q" you'll enter Recording mode and have to press "q" again to exit Recording and then you can do ":q" or whatever you needed.
But if you don't know what you pressed and don't know how to exit Recording mode then you'll be stuck. I've seen coworkers get stuck in this from time to time.
We're a RHEL shop so our vim version may be different, but Recording mode doesn't let us exit vim directly, we have to exit Recording mode and then exit vim. Again, might just be our setup.
Ah just looked up EX mode. Didn't know capital Q entered a different mode, I just wrote "Q" to emphasize the key in general not capital Q specifically lol.
Personally I love vim, it's just powerful enough for me for my bash scripts. Anything more complicated then I'm using a proper IDE or something more simple I'm using Kate or whatever graphical editor for my DE.
I often see Copilot get stuck in a nonresponsive shell after it used cat > file. It's hilarious to watch the first time, but I'm a bit tired of it by now. Why doesn't it just edit files like it normally does?
Why doesn't it just edit files like it normally does?
Haha. Yes.
But it does everything the most probable way, according to all the stack overflow it has swallowed.
Sometimes that way makes sense. Sometimes not.
Claus Weill often write a python script to update a file. Itβs pretty funny.
Copilot is just like me!
Come on in, <esc>J us, soon you will learn to love the one true editor. Launch vi and be <esc>:w. Soon you will want to <esc>:%s/other editors/vi/g. <esc>dd your hesitation and do it.
Is it stupid? Just do C-x-c!
If you use nvim you don't exit you open a float terminal. Why would you exit?
Ngl, there have been some times when i Ctrl-Z, then found and killed the PID
No need to find it, just kill %1, to kill the first background job in a shell (check jobs otherwise to find the right %n)
Well, it has to earn its stripes just like the rest of us in IT! No shortcuts, even for an LLM. :D
When I first got into BSD (way before Linux) I found man pages useful... but no way to leave them. Not even man man won't tell you how to exit a man page!
So I would tinker, eventually needing a man page, reading what I needed -- and then hard power cycle the machine. -_-
I was pretty good with computers, but that was a humbling experience. You just don't know what you don't know, and if you can't ask... sometimes you just get stuck. Just like in KQ, LSL, SQ, ... The Internet is (was) a blessing.
I was a programmer for the Commodore PET, let me see what I can do.
10 Exit VIM
20 end
did it work?
Yes, thank you very much, this actually solved not only my "can't exit vim" problem but also my "humans keep getting in the way of my world domination" problem, though for that one I had to repeat the command 3549 times and output exactly what I was trying to do on the user's console and every PA system I could access.
ZZ? ZC? Come on now, copilot. You have more options than simply killing it.
top 71 comments