• @ExtremeDullard
    -1•5 months ago

    I must be a minority then. I tried it once - as in, I made a real, honest attempt at liking it and making it work for me - and all it managed to do is show me it’s buggy and confused, and to convince me to steer well clear of it and stick to vanilla Vim.

    I really really dislike Neovim.

    Also, I question the vailidy of a survey in which VSCode is 13 times more “desired” - whatever that means, it’s not like it’s hard to procure - than VSCodium, given that VSCodium is VSCode sans the Microsoft spyware. Makes no sense to me…

    • ѕєχυαℓ ρσℓутσρє
      5•5 months ago

      I understand not liking the vim way of doing things (which seems not to be the case for you), but I’ve never heard anyone describe neovim as buggy. Not throwing shade, genuinely curious. What bugs did you encounter, and when was it?

      Edit: I missed that you posted a link there. Interesting.

      • @ExtremeDullard
        3•5 months ago

        Most people don’t even know VSCodium exists so that makes perfect sense

        What would make sense is that people who know what VSCodium is answer the survey while those who don’t refrain. Then you would see fairly identical scores for VSCode and VSCodium.

        What this survey demonstrates is that people express opinions about stuff they know nothing about.

        VSCode has a better selection of extensions.

        True. I’m aware some extensions don’t work in VSCodium. But I’ve yet to run into one myself.

        Having said that, I’m not a VSCod(e|ium) user myself, so it’s not like I’m a specialist I’m forced to know enough to support my users, and what I’ve seen of VSCodium so far is that it has almost zero downside for the invaluable upside of not feeding data to Microsoft.

        But naturally I’m a Vim user through and through, and we Vim / Neovim / whatever VI clone floats your boat don’t need no Microsoft-made Electron resource pig to do our work, as you well know 🙂

        • nickwitha_k (he/him)
          2•5 months ago

          Microsoft-made Electron resource pig to do our work, as you well know

          I hate that any it so much. It doesn’t need to be that way but, MS. Yeah. Maybe I’ll try to make an OpenAPI plugin so that I can return to Neovim.

        • NostraDavid
          1•5 months ago

          But I’ve yet to run into one myself.

          Pylance doesn’t work, and is a “necessity” for writing Python

    • @zygo_histo_morpheus@programming.dev
      4•5 months ago

      “Desired” and “Admired” are very strangle labels, it like the question(s) might have been:

      Which development environments did you use regularly over the past year, and which do you want to work with over the next year? Please check all that apply.

      In which case VSCodes high “desired” score just means that it was widely used?

    • @ericjmorey@programming.devOP
      3•5 months ago

      I remember that post. I’m surprised that nobody has run into that problem until now. Did you open up an issue on the Neovim GitHub repository?

      I ask because I don’t see one and I want try to replicate the issue. I’ll report it myself if I’m able to.

      • @ExtremeDullard
        1•5 months ago

        I don’t care enough to bother, to be honest. Neovim, like Vim, is just a tool to me. It failed me, I moved on. I have more interesting things to spend my time on.

        • @ericjmorey@programming.devOP
          1•5 months ago

          I care, because what you found is a bug. And I think it would be best to document the intended behavior and a temporary work around, and then fix the bug. So I’m doing just that.

    • @AVincentInSpace@pawb.socialEnglish
      2•5 months ago

      I don’t know how to open that post on my instance so I can reply to it, but if you’re willing to give it another shot, I figured out how to get indentexpr= to apply to all buffers from init.vim, using an auto command. Add this to your init.vim:

      autocmd BufRead,BufNewFile,VimEnter * set indentexpr=
set indentexpr=
    • NostraDavid
      1•5 months ago

      given that VSCodium is VSCode sans the Microsoft spyware

      Can’t use Pylance in VSCodium /rant

      It’s one of vscode’s killer features (at least for Python), and I can’t live without it (I tried).

      Yes, I don’t like it either; I wish I could use Pylance in Neovim or anything else LSP-enabled, but it is what it is.