• MsPenguinette@lemmy.world
    link
    fedilink
    arrow-up
    46
    ·
    edit-2
    1 year ago

    My serial killer trait is that I use vi instead of vim cause I’m too lazy to type the extra character. Tho if for some reason, vi tab completed to vim, I’d probably use vim

      • MsPenguinette@lemmy.world
        link
        fedilink
        arrow-up
        19
        ·
        1 year ago

        {vi} = 2 {vim} = 3 {v=vim} = 5

        I’d need to run vi at least 5 times to have a net gain in saving keystrokes. I’m typically in effemerial systems created by the users of our env, so rarely am I going to gain those strokes back

        But also, why am I trying to apply logic to this? I’ll often cat a file before editing it. This shit is just illogical idiosyncrasies I’ve picked up over the years. I’m probably creating posthoc justifications for insane things I do cause it’s hard to override muscle memory

      • ekky43@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        19
        ·
        edit-2
        1 year ago

        Aliases are just bloat! You can do just fine without them. Heck, why not remove the ASCII conversion and read everything in hex or binary?

        It’s all about SPEED and efficiency here!

      • MsPenguinette@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I’m in DevOps so I’m in a lot of effemerial systems so in practice, I will run into systems where profile hasn’t been set up. Tho I do like the idea of making sure all systems properly have that aliased cause it’d be serial killer vibes to spend hours of time to make sure that I can save a keystroke.

        Tho it’d never make it through PR. Also, wild require explaining to my coworkers that I do this

    • expr
      link
      fedilink
      arrow-up
      12
      ·
      1 year ago

      Most all distros alias vi to vim already, so it makes no difference.

      • Chunk@lemmy.world
        link
        fedilink
        arrow-up
        9
        ·
        1 year ago

        You use vi because you are lazy.

        I used vi because I am too stupid to close it.

        We are not the same.

      • MsPenguinette@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I’ll have to check tomarrow if RHEL and UBI do this.

        Did some quick googling and looks like cent has that alias by default but doesn’t do it when root. Which would explain why I do get inconsistent results with vi. I never thought about it in detail besides just knowing that there are some visual changes. Thanks for the info, I’ll be noticing this now that I know!

      • puppy@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        You are missing out! I used to only use vim to edit config files. So I knew my way around (albeit, slowly). I installed the IdeaVim plugin a week ago and learned some new key bindings I wasn’t using. A week in I’m almost faster than before! And it’s only going to get better after I’ve acquired muscle memory (I’m nearly there.) and move on to complex key bindings/sequences. Then it will probably be as if the cursor is directly connected to my mind. I’m hopeful because I’ve seen a mentor of mine do it.

        • Free Palestine 🇵🇸@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          What am I missing out on? I use vi to change values in files on servers. What would you use for that task? Most of my other text-based work like writing Emails, taking notes or programming happens in Emacs.

          • puppy@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            I don’t think you understood what I said. I started using vim key bindings ALSO in my IDE and my speed improved because of it. I didn’t ask you to stop using vi. I merely suggested that you used MORE of it. If your Emacs setup already use vim keybindings that’s exactly what I’m doing too.

            • Free Palestine 🇵🇸@sh.itjust.works
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              1 year ago

              Oh thanks, now I got it. I agree, vi/vim bindings are awesome. I use them everywhere, in Emacs, in my shell, my browser, and in my tiling window manager. When I said, that I wouldn’t want to program in vi, I didn’t mean that because of the keybindings, I meant that because vi just lacks many useful features for programming and you can’t add plugins to it. I have programmed in Neovim for over a year though. Just switched to Emacs, because it has even more features, possibilities and customizability. I will never drop Vim keybindings though.

                • Free Palestine 🇵🇸@sh.itjust.works
                  link
                  fedilink
                  arrow-up
                  2
                  arrow-down
                  1
                  ·
                  1 year ago

                  I use the fish shell. In fish, you can just add fish_vi_key_bindings to your config file and now Vi bindings will be automatically enabled when you start fish. For bash, it’s set -o vi and for zsh it’s bindkey -v. For the browser, you can install plugins like Vimium (Vimium-FF for Firefox) or Tridactyl. I find these to be incredibly useful, I love navigating around websites with j and k or d and u, jumping up with gg and down with G, searching with /, closing tabs with x, reloading websites with r, opening new tabs with t, going back and forward with H and L, etc.

  • Cyborganism@lemmy.ca
    link
    fedilink
    arrow-up
    59
    arrow-down
    35
    ·
    1 year ago

    Emacs sucks. Vim is so much better. And vscode is okay.

    Go ahead. Down vote me. I don’t care. This isn’t Reddit lol.

      • The Cuuuuube@beehaw.org
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        I’m going to give what I’ve realized newer folks to Vim think is a scorching hot take: VimL is nice. Theyre the same editor commands you use in your day to day life, even if you’re using NeoVim + Lua, just all written out in a file.

        That said, using NeoVim + Lua makes it far easier to organize your config, which also makes it easier to write more complex configs. It’s like the difference between building a shed around back for your home office vs building a cathedral. Its fine to work in a shed, but once you know you can build a cathedral, you’re kinda tempted to just up and do it

        • TechNom (nobody)
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          There are only 2 people who know VimL well enough - Bram and Tim Pope (OK, now it’s 1). It’s always better to leave language design to someone else - in the same way aeroplane manufacturers don’t care about making their engines too. Languages need dedicated attention - careful design balancing power and intuitiveness, performance tuning of language runtime, documentation etc. That’s why neovim’s adoption of lua has been a revolution in the development of its plugin ecosystem.

      • expr
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        Vim has vim9 script now which is very similar to common scripting languages like Typescript.

        Vim also doesn’t need tons of configuration.

        • TechNom (nobody)
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          1 year ago

          I know it’s bad to speak ill of the dead - and Bram deserves respect for his contributions and some of his political stances (I mean vim’s charityware status). However, vim9 and some other decisions from him (like async mechanism) were deliberate attempts from him to create a schism between the vim and neovim user communities. Some of them were ideas he was initially not willing to accept and was proven useful by the neovim developers. Vim’s choices were also not much better than Neovim’s (often it’s the reverse). The sudden explosion of neovim lua plugins is an example of this.

      • Cyborganism@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        At first maybe. But when you get your vim config well honed over time you’re good. Plus there’s things like pathogen or other frameworks to add plugins and stuff.

    • Crandel
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      Vim sucks, Emacs is the best editor in the world

    • TechNom (nobody)
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      As someone who uses both - both are good. The only thing that sucks is you. And your reddit version sucks as well.

  • narc0tic_bird@lemm.ee
    link
    fedilink
    arrow-up
    19
    arrow-down
    1
    ·
    1 year ago

    You guys recommend VSCodium over VSCode. Is there a working sync solution similar to the one built into VSCode where you can sync all settings and extensions between machines?

  • bloopernova
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    1
    ·
    1 year ago

    I generally code in VSCode, and manage org-roam notes and information in Emacs. Works well enough for me.

    • Free Palestine 🇵🇸@sh.itjust.works
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      1 year ago

      Any particular reason why you don’t code in Emacs? Since you already set up Org Mode and Org Roam, I’m sure you know how the configuration works and how to write some Elisp. It’s actually not that much work to set up all the things you would need for programming (lsp-mode, etc.)

      • bloopernova
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I guess I just preferred VSCode for coding? Every time I’ve tried to use Emacs for my coding workflows I’ve given up, I think I’m just used to VSCode in that respect. It is weird, I know.

    • ursakhiin@beehaw.org
      link
      fedilink
      arrow-up
      17
      ·
      edit-2
      1 year ago

      I genuinely think it’s funny that in a post that isn’t making fun of Emacs you felt the need to defend Emacs.

      It’s making fun of Emacs users for always finding ways to talk about Emacs. (Which I don’t think is a real problem anymore)

    • Corr@lemm.ee
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      I use vscode with vim plugin. I find this to be a pretty great combo, for me at least

      • The Cuuuuube@beehaw.org
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        VS Code + vim plugin is sooo slooow. I’m happy it works for you but I can’t wait to finish on boarding my onboarding buddy so I can go back to vim where I belong

      • XTornado@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        I do too… but it’s not perfect. If you use the extension that uses neovim in the background is seems is the best option but still I miss my “never needing a mouse” feeling I had on emacs. I mean maybe is just lack of knowing keybindings… but back on the day when I used spacemacs it was all so intuitive.

        I also miss magit…