• OpenStars@startrek.website
        link
        fedilink
        English
        arrow-up
        5
        ·
        5 months ago

        You don’t ever close vim. You pray to the gods and hope that vim chooses to quit for you. (technically accurate if you think about it - i.e. otherwise you leave swap files all over the place:-P)

        And hope that you do not mess up and summon a daemon instead:-P.

  • azimir@lemmy.ml
    link
    fedilink
    arrow-up
    21
    arrow-down
    2
    ·
    5 months ago

    If an IDE doesn’t have vi key bindings it isn’t going to be used by me. That’s what finally get me to change from terminal only dev to vscode. Until I found the vi editing extension the IDE wasn’t of interest.

    Yes, vi is just that good.

    I hear emacs bindings are also great, but I just know how to save and exit from emacs.

    • Drew Belloc@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      5 months ago

      I use doom emacs and have to say, it takes everything that I like about vim and adds to emacs, plus a lot of useful features that i would have to install myself otherwise that can be enable by just uncommenting a feel lines in the config file.

      It’s can feel a bit bloated at first but allows me to have the perfect IDE (for me at least) in a matter of minutes.

      And the best of all is that I don’t need to use the emacs keybinds if I don’t wanna (and I don’t).

      • azimir@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        5 months ago

        One of the interesting aspects of humanity is how much people like given text editing methods. There’s a handful of approaches and after learning one or two, people really figure out what works for them.

        I am more than happy to say I like vim, but in the end you should use what you like best. Just done be surprised when I can write and edit a ton of text really fast while your nano session is comfortable, but slow.

    • TΛVΛR
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      Emacs keybinds are fine, used them for some years. But once I tried modal bindings I never wanted to go back, “key-chords” just add strain.

      Fortunately emacs has many options for modal keybindings, I prefer meow over vim personally

  • 1984@lemmy.today
    link
    fedilink
    arrow-up
    6
    ·
    5 months ago

    I used to use a lot of nvim but actually went to Jetbrains now at work… It’s just a lot easier to work with for teams.

    • flashgnash@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      Can you not get an nvim extension? There’s one for Vscode that works very well and even uses your existing nvim config

      • mac@infosec.pub
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        What does it carry over from your swim config? What are the benefits of using Nvidia inside of VSCode as opposed to just nvim?

        • flashgnash@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          You get everything Vscode does, vscode’s LSPs, vscode’s element rename/jump to definition (which I realise nvim has but I can’t get it to work properly and code does it out of the box), live share sessions, built in split panes and git integration etc etc

          It carries over everything as far as I can tell (besides the graphical changes obviously), motions, plugins, shortcuts

          I’m sure you can achieve most things Vscode does in neovim but using Vscode/ium and nvim is a massive shortcut

          • mac@infosec.pub
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            5 months ago

            Honestly it seems like you gain nothing but a slightly bloated electron wrapper around NeoVim.

            All those features you listed either work out of the box or require minimal configuration in NeoVim.

            • flashgnash@lemm.ee
              link
              fedilink
              arrow-up
              3
              ·
              5 months ago

              As far as I’m aware none of the things I mentioned work out of the box in neovim (jump to definition does but only within the same file which is kinda useless for me

  • Crow@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    5
    ·
    5 months ago

    Vim actually has a surprising ammount of features already built in, you don’t even really need any Plugins. It has a file browser, terminal emulator, and window tiling built in

    • flashgnash@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      5 months ago

      Helix is great except when you switch to vim for whatever reason and everything is backwards

      • mac@infosec.pub
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        This was the thing that stopped me from hopping over in the first place, the vim binds just make too much sense

        • flashgnash@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          Personally I kinda prefer helix bindings but vim bindings I think are far more useful to know when using anything other than helix

          • mac@infosec.pub
            link
            fedilink
            arrow-up
            1
            ·
            5 months ago

            Honestly I’m sure they are great but vim bindings are near ubiquitous amongst technologies now so it’s difficult to get everyone to move away from it.

  • bloodfart@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    4
    ·
    5 months ago

    lol if you can’t use vim.

    Who cares that you can cut a perfect miter joint with a jig and a table saw when you can’t cut a butt joint with a hand saw.

    • 342345@feddit.de
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      5 months ago

      I looked up miter joint and butt joint and I’m beginning to understand what you wanted to say.

      Yes, maybe.

      It doesn’t hurt to know the basic commands to insert, copy, paste with vim. But with bim, handling the tool always consumed a too big percentage of my attention in respect to doing the task at hand. I still use it for small file changes.

      • bloodfart@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        5 months ago

        My comment really applies more to vi than vim but everyone’s using them interchangeably nowadays. When implementing systems where internet connection or excess install size aren’t possible or recommended, you gotta be able to work with the tools at hand.

        Of course, the comparison is custom cabinetry to ikea. Your local meth head needs to understand how to use hand tools because he or she may need to use them for myriad reasons ranging from “I don’t have the power version of this” to “it’s faster” to “the cut is cleaner” to “they pay me more to use this”. The person designing hudfł needs to be concerned first and foremost with how to shave a sixteenth off every panel so his accounting department doesn’t have to pay to reforest an extra hundred acres this year.

        Perhaps someone working entirely in programming has good reason to not know vim, but I still cling to the antiquated notion that the person designing furniture out of manufactured materials ought to be able to build a box you’d feel comfortable with company seeing.

  • N3Cr0@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    8
    ·
    5 months ago

    There is no point in typing the “m” in vim. Just edit your files with the vi shortcut.