top 50 comments

sorted by: hot top controversial new old
[–] 40 points 2 years ago (5 children)

I actually learned how to use vi like 30 years ago and I had all the commands memorized. Then, nano came along. All the commands are at the bottom of the screen to remind you. It was just too tempting to pass up. However, I can't help but suspect that somewhere out there I might have left a vi session open because maybe I mistyped. I might have accidentally typed ;q! instead of :q! or something.

  • source
  • hideshow 7 child comments
  • [–] 8 points 2 years ago (1 child)

    I'm feeling old now... I've been using vi for 35y now and was happy when I got vi.exe on a dos box, as I hated edit. I still don't like 'simple' editors like nano/joe.

    I used kill to get out of emacs when trying it agter 7y of vi usage, so I get the need to get mideval on editors users aren't used off. ;)

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (3 replies)
    [–] 33 points 2 years ago (1 child)

    You can :q! any time you want, but you can never leave.

  • source
  • hideshow 2 child comments
  • [–] 28 points 2 years ago

    It's really easy, just unplug your computer.

  • source
  • [–] 25 points 2 years ago* (last edited 2 years ago)
      • Esc Γ— 2
      • CTRL-[ Γ— 2
      • CTRL-\ CTRL-N Γ— 2
      • :q
      • :qa
      • :wq
      • :wq!
      • :wqa
      • :x
      • ZZ
      • :q!
      • ZQ
      • :q!
      • :cq
  • source
  • [–] 20 points 2 years ago (1 child)

    It's the hotel California of text editors >:)

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 16 points 2 years ago (2 children)

    Nano is pretty good if you're in a terminal. Used to use vim for ssh related stuff but since nano added syntax highlights I didn't go back.

  • source
  • hideshow 4 child comments
  • [–] 6 points 2 years ago* (last edited 2 years ago) (7 children)

    Nano's only appeal is that it's beginner-friendly, but you already know Vim, so why switch?

  • source
  • parent
  • hideshow 8 child comments
  • load more comments (6 replies)
  • [–] 14 points 2 years ago (4 children)

    I know how to get out. But I still like nano a lot more.

  • source
  • hideshow 4 child comments
  • load more comments (4 replies)
    [–] 13 points 2 years ago (1 child)
    load more comments (1 reply)
    [–] 12 points 2 years ago

    You exit vim by unplugging the pc.

  • source
  • [–] 11 points 2 years ago (1 child)

    That's how you learn Linux and Google: how to kill vim? kill -9 vim.

  • source
  • hideshow 2 child comments
  • [–] 10 points 2 years ago

    Now do ed...

  • source
  • [–] 9 points 2 years ago

    Pssh, come on, it's just :q or :q! - couldn't be simpler or more intuitive!

  • source
  • [–] 9 points 2 years ago (2 children)

    My main problem with vim is that they use hjkl instead of jkl; , it doesn't make sense to me why they'd do that.

    And my second problem is that I use my own custom keyboard layout instead of qwerty, so I'd have to remap all the keys. Why spend hours learning and then rebinding all the keys when I can instead play some Dota? /s

  • source
  • hideshow 4 child comments
  • [–] 3 points 2 years ago* (2 children)

    Been a vim user for decades but never used hjkl. Probably strongly correlated with the fact I'm non QWERTY as well (Dvorak). I just use the arrow keys combined with the jumps to start/end of lines/words or to characters.

    You don't need to remap anything aside from hjkl as the keybindings are mostly mnemonic and not location based.

    On Dvorak at least, ^C is so easy to press that it's great for switching modes, I never use Esc.

    I find the more time you've spent in non-graphical shells, especially on low spec devices or laggy connections, the more you appreciate vim. Instead of pressing Del a bunch of times and having it overrun you can ct" to swap out that string. I even use vim keys in vscode, as my hands are so used to them.

    My biggest complaint is logging into some legacy device that only has vi and not vim, when shortcuts like "dap" or "caw" don't work

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
  • [–] 8 points 2 years ago

    :q does the trick

  • source
  • [–] 7 points 2 years ago (1 child)

    I took the vim pill a few years ago and spent tons of time learning its shortcuts, trying out plugins, and forming strong opinions about my relationship with my text editor. It's a great tool, but I personally lost the plot somewhere down the line. I'm not sure that passion actually served me.

  • source
  • hideshow 2 child comments
  • [–] 7 points 2 years ago
    [–] 5 points 2 years ago

    !killall vim

  • source
  • [–] 3 points 2 years ago
    [–] 3 points 2 years ago (4 children)
    load more comments (4 replies)
    [–] 3 points 2 years ago (2 children)
  • Remember to actually kill the process though, since that will only background/suspend it in most cases.

    (Be sure to save the file though first, Vim creates a "swap" / recovery file but its best to not rely on that, use fg to re-open, then press escape and type :wq)

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