5 ms·

vim crashes or hangs for me about once every month. I've never bothered to find out why since I don't think it's worth the effort. The effort would be lower if

vim crashes or hangs for me about once every month. I've never bothered to find out why since I don't think it's worth the effort. The effort would be lower if the code was cleaner and didn't have so much bloat related to platforms that don't exist. It would definitely be easier to submit a patch if I didn't need to cater to all the platforms I've never seen.

Watabou 11y ago
Are you sure the crashes aren't caused by a plugin you installed? I have only experienced a handful of vim crashes but all of them were caused by plugins.
- mintplant 11y ago
  vim may still be partly to blame in that case, as it lacks support for async plugins.
  - Watabou 11y ago
    Do you also blame Microsoft Word because it doesn't let you play movies?
    - mintplant 11y ago
      People have tried to add async plugin support to vim, but the patches have all been rejected. Meanwhile, the plugin support in Neovim is worlds better. Microsoft Word doesn't even accept patches, which I do indeed hold against it.
      - Watabou 11y ago
        The patches were rejected because they didn't provide a working solution for cross platform support. The plugin system in Neovim is only "better" for people who actually want async plugins. I am not one of them.
jrbrtsn 11y ago
Most likely you've typed Ctrl-S, which causes the terminal to pause. Here is the what the vim docs have to say about that: Note: CTRL-S does not work on all terminals and might block further input, use CTRL-Q to get going again.
- omaranto 11y ago
  I've never heard of Ctrl-S causing a crash, though. So your explanation at most accounts for the hangs.
  - jrbrtsn 11y ago
    I've used vim pretty much every work day in the last 15 years or so, and I can count the number of times it's crashed on one hand. If you can actually verify that it crashed (i.e. core dump file), then you've got the source available, and you can send in the patch.
    - omaranto 11y ago
      It's never crashed on me. I'm not the person who claimed it crashed.
- joeheyming 11y ago
  This was my biggest hurdle to learning vim, I kept hitting Ctrl-S...
  - firebones 11y ago
    This might help: http://vim.wikia.com/wiki/Map_Ctrl-S_to_save_current_or_new_files http://vim.wikia.com/wiki/Map_Ctrl-S_to_save_current_or_new_... (Caveat emptor, can't speak from first hand experience.)
- MereInterest 11y ago
  If you run "stty -ixon", it will prevent Ctrl-S from pausing the terminal. I understand that feature in the days of slow connections, but it feels rather silly at this point.

Watabou 11y ago

Are you sure the crashes aren't caused by a plugin you installed? I have only experienced a handful of vim crashes but all of them were caused by plugins.

mintplant 11y ago
vim may still be partly to blame in that case, as it lacks support for async plugins.
- Watabou 11y ago
  Do you also blame Microsoft Word because it doesn't let you play movies?
  - mintplant 11y ago
    People have tried to add async plugin support to vim, but the patches have all been rejected. Meanwhile, the plugin support in Neovim is worlds better. Microsoft Word doesn't even accept patches, which I do indeed hold against it.
    - Watabou 11y ago
      The patches were rejected because they didn't provide a working solution for cross platform support. The plugin system in Neovim is only "better" for people who actually want async plugins. I am not one of them.

jrbrtsn 11y ago

Most likely you've typed Ctrl-S, which causes the terminal to pause. Here is the what the vim docs have to say about that: Note: CTRL-S does not work on all terminals and might block further input, use CTRL-Q to get going again.

omaranto 11y ago
I've never heard of Ctrl-S causing a crash, though. So your explanation at most accounts for the hangs.
- jrbrtsn 11y ago
  I've used vim pretty much every work day in the last 15 years or so, and I can count the number of times it's crashed on one hand. If you can actually verify that it crashed (i.e. core dump file), then you've got the source available, and you can send in the patch.
  - omaranto 11y ago
    It's never crashed on me. I'm not the person who claimed it crashed.
joeheyming 11y ago
This was my biggest hurdle to learning vim, I kept hitting Ctrl-S...
- firebones 11y ago
  This might help: http://vim.wikia.com/wiki/Map_Ctrl-S_to_save_current_or_new_files http://vim.wikia.com/wiki/Map_Ctrl-S_to_save_current_or_new_... (Caveat emptor, can't speak from first hand experience.)
MereInterest 11y ago
If you run "stty -ixon", it will prevent Ctrl-S from pausing the terminal. I understand that feature in the days of slow connections, but it feels rather silly at this point.