top 71 comments

sorted by: hot top controversial new old
[–] 215 points 6 months ago (3 children)

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.

  • source
  • hideshow 3 child comments
  • [–] 94 points 6 months ago

    Ok this proves that AI has reaches human level intelligence.

  • source
  • [–] 85 points 6 months ago

    This is the closest I have seen Copilot doing something like a human Programmer would

  • source
  • [+] 127 points 6 months ago (12 children)
  • [–] 51 points 6 months ago (9 children)

    What if my PC boots straight into Vim? It's not like I need anything else, can do everything in Vim

  • source
  • parent
  • hideshow 9 child comments
  • [–] 23 points 6 months ago (2 children)

    Jokes aside, vim as PID 1 is just a bad idea.

    Emacs on the other hand: https://github.com/emacs-os/el-init

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 6 months ago (3 children)
  • [–] 5 points 6 months ago (2 children)
  • load more comments (1 reply)
  • [–] 54 points 6 months ago (3 children)

    This is how we trap it. This is how we win.

  • source
  • hideshow 3 child comments
  • [–] 15 points 6 months ago (1 child)

    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?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 40 points 6 months ago
    [–] 74 points 6 months ago (7 children)

    Instructions: "Next, open the .config file in vim..."

    Me:

  • source
  • hideshow 7 child comments
  • [–] 51 points 6 months ago (5 children)

    What a weird way to spell nano

  • source
  • parent
  • hideshow 5 child comments
  • [–] 20 points 6 months ago (3 children)

    Nano is the proper tool for this job.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 35 points 6 months ago (9 children)
  • [–] 71 points 6 months ago (4 children)

    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!

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 6 months ago (3 children)
  • [–] 6 points 6 months ago (2 children)
  • [–] 8 points 6 months ago* (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 10 points 6 months ago (3 children)

    Could be in recording mode, which usually needs a couple ESC or a Q then you can :wq

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 6 months ago (2 children)

    You mean EX mode? IIRC recording mode doesn't prevent exiting vim

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 6 months ago

    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.

  • source
  • parent
  • [–] 1 point 6 months ago

    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.

  • source
  • parent
  • [–] 32 points 6 months ago (2 children)

    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?

  • source
  • hideshow 2 child comments
  • [–] 31 points 6 months ago

    Just like me fr

  • source
  • [–] 30 points 6 months ago

    Blowing through all those tokens failing to exit a vim

  • source
  • [–] 26 points 6 months ago
    [–] 22 points 6 months ago

    First funny thing ive seen Microslop Copilot do...

  • source
  • It has achieved the same level of awareness as the average emacs user.

  • source
  • [–] 16 points 6 months ago

    I'm sorry, Dave. I'm afraid I can't exit vim.

  • source
  • [–] 16 points 6 months ago (1 child)
  • [–] 14 points 6 months ago

    How to protect your computer from automated AI attacks 101: start vim

  • source
  • [–] 14 points 6 months ago (1 child)

    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.

  • source
  • hideshow 1 child comment
  • [–] 12 points 6 months ago (1 child)

    Is it stupid? Just do C-x-c!

  • source
  • hideshow 1 child comment
  • If you use nvim you don't exit you open a float terminal. Why would you exit?

  • source
  • [–] 17 points 6 months ago (3 children)

    Ngl, there have been some times when i Ctrl-Z, then found and killed the PID

  • source
  • hideshow 3 child comments
  • [–] 13 points 6 months ago (2 children)

    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)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 6 months ago (1 child)

    Well, it has to earn its stripes just like the rest of us in IT! No shortcuts, even for an LLM. :D

  • source
  • hideshow 1 child comment
  • [–] 2 points 6 months ago* (last edited 6 months ago)

    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.

  • source
  • parent
  • [–] 6 points 6 months ago

    Shit, does that mean LLMs are real programmers, bow?

  • source
  • [–] 5 points 6 months ago
    [–] 5 points 6 months ago (1 child)

    I was a programmer for the Commodore PET, let me see what I can do.

    10 Exit VIM

    20 end

    did it work?

  • source
  • hideshow 1 child comment
  • [–] 5 points 6 months ago

    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.

  • source
  • parent
  • [–] 8 points 6 months ago
    [–] 4 points 6 months ago

    ZZ? ZC? Come on now, copilot. You have more options than simply killing it.

  • source
  • [–] 4 points 6 months ago

    It really was an oversight forgetting to put in a Exit.

  • source
  • [–] 3 points 6 months ago

    The command opened the alternate buffer.

  • source
  • load more comments
    view more: next β€Ί