6 ms·

WTF are you talking about? Vim have may have many demerits but segfaults is not on that list. If segfaults are that frequent you described then people would hav

• leokun 13y ago
  Nope, and nope. > WTF are you talking about? Vim have may have many demerits but segfaults is not on that list. If segfaults are that frequent you described then people would have jumped ship already. Vim is all segfaults once you introduce async, and it's highly unstable during any dev work. On any given day visit the Vim dev mailing list and scroll down. Today I see: Scrolling in a c file segfaults: https://groups.google.com/forum/#!topic/vim_dev/teRV3RyDtzc https://groups.google.com/forum/#!topic/vim_dev/teRV3RyDtzc Referencing an old buffer seg faults: https://groups.google.com/forum/#!topic/vim_dev/Mssm8pKtnGM https://groups.google.com/forum/#!topic/vim_dev/Mssm8pKtnGM Segfault opening a readme: https://groups.google.com/forum/#!topic/vim_dev/SE31YUccJN4 https://groups.google.com/forum/#!topic/vim_dev/SE31YUccJN4 Segfault selecting a lot of text: https://groups.google.com/forum/#!topic/vim_dev/yzVqZ3qogho https://groups.google.com/forum/#!topic/vim_dev/yzVqZ3qogho Segfault on autocompletion: https://groups.google.com/forum/#!topic/vim_dev/lqcn57eRGGs https://groups.google.com/forum/#!topic/vim_dev/lqcn57eRGGs Segfault on tab switching: https://groups.google.com/forum/#!topic/vim_dev/Vc9Z8rfe22w https://groups.google.com/forum/#!topic/vim_dev/Vc9Z8rfe22w Just keep scrolling, the segfaults never stop. > Though async future is not built-in there are several plugins for doing async operation, for example... For your other point, some plugins fake async using a cursorhold hack that break vim for users who use leader keys. That is they insert fake key strokes. Vimproc actually quits on cursorhold: https://github.com/Shougo/vimproc.vim/blob/master/autoload/vimproc.vim#L1124 https://github.com/Shougo/vimproc.vim/blob/master/autoload/v... That's right thess plugins inserts keys to trigger autocommand. I would like you to go ahead and type a long vim command using leader keys and see if that works for you. When a plugin inserts keys while you are inserting keys everything stops and you have to start over. Go ahead, go implement a clock with a plugin that updates every second. I bet that plugin fakes user interaction. It doesn't work. Edit: Also nice on the downvotes, perhaps explain how my post is wrong in addition to downvoting. Everything I have said are matters of fact. Are my facts wrong?
  • dllthomas 13y ago
    It doesn't surprise me terribly that, in the sizable userbase, some people manage to make it segfault - particularly running unknown plugins &c. The first example you give is even found to be a bug in a compiled external extension. I've not read through any of the others... I've been using vim pretty much daily, across many versions, over roughly two decades, and I literally do not recall encountering a segfault. I would be hugely surprised if "segfaults all the time" is a more typical experience for an individual user.
    • leokun 13y ago
      It probably isn't. It's when you want to do async or timed things that things start to fall apart.
      • weaksauce 13y ago
        What use case do you have for timed things or async things?
        • to3m 13y ago
          For good ideas for async stuff you should try emacs. You don't have to keep using it, just look at what it does with its built-in asynchronous subprocess handling. The interactive python shell is particularly neat, but it also has grep and compile functionality that doesn't block the editor as it runs, and a gdb mode that (based on my very brief go with it) seemed to work pretty well. One neat thing I use it for is TTY capture from a target system (usually games console or embedded device) over a serial or network cable. Run your terminal program in emacs at the start of the day, and emacs will dutifully capture all the terminal output as you work. Search, save and manipulate TTY output using all the commands you know and love. Well - except for `.'. Or `*'. emacs doesn't do those two...
      • dllthomas 13y ago
        My experience certainly doesn't make that implausible. I am pretty careful about async IO in terms of how my software interfaces with me, and this translates to less uncontrolled use of it generally.
• krakensden 13y ago
  vim segfaults a lot on my copy of OS X. Never seen it happen on Linux or Windows though. Given the Macbook-heavy nature of HN, that's probably what leokun is talking about.
  • super_mario 13y ago
    Never experienced VIM crash of any kind on Mac OS X, Linux or Windows. And I have been using it since Amiga days. On the other hand I don't use very many plugins, esp. not plugins that have native extensions.