I’ve used VS Code for a long time, but have recently grown weary of Microsoft’s approach to OSS. I’ve checked out VS Codium which seems like it might be a great option.

What text editor are you using?

  • @vi21@lemmy.ml
    5•2 years ago

    I’m using GNU Emacs, which is, from my experience, great for open source software and decentralized development. Last year, I found an issue in a package/extension, I could make an experiment by modifying and running its code on the fly. I didn’t even need to reload the whole package/extension. So I figured the solution out and submitted a pull request quickly.

  • SudoDnfDashY
    4•2 years ago

    I only really use Vim. Mainly because vi is installed on basically every server and distro, so it is what I got used to.

  • Kromonos
    3•2 years ago

    I’ll make myself unpopular with Sublime Text and VSCode. 😆
    On the console, however, I actually use VIM almost exclusively.

    • @a_Ha@lemmy.ml
      2•2 years ago

      1- terminal-based text editor,
      2- with mouse support,
      3- 1000 x better than nano(editor) & vim (just kidding, 5 x better)

      • Tmpod
        1•2 years ago

        Vim and neovim have mouse support as well. Micro has less plugins and is overall less configurable than (neo)vim. The style sure is different, but in terms of features, vim outclasses micro atm.

        • @GenkiFeral@lemmy.ml
          3•2 years ago

          I may break down and learn some vim keybindings soon since so many other Linux or FOSS programs use it or can use it. But, until then, why waste time learning a bunch of stuff when micro allows me to use the newer standard keybindings that most programs use (^s to save; ^v to paste, etc)?

  • @iortega@lemmy.eus
    3•2 years ago

    TL;DR: Neovim.

    Because I feel exceptionally happy today, I’m going to talk about my journey among text editors:

    Unnecessary text

    I will start from Vim.

    I started using Vim 5 years ago.
    i = 0
    while (still using vim) and i < 6:
    ----test Emacs vanilla
    ----give up with Emacs vanilla
    ----i++
    ----wait 1-4 months
    test Emacs Xah-Fly-Keys;
    Success
    wait 2 months
    Back to Vim.
    Test again vanilla Emacs 2 more times while using vim.
    Test again xah-fly-keys Emacs.
    After Several months…
    Upgrade to Neovim!
    2 days later: Back to Vim.
    X more time.
    We are on Q1 2020. Let’s use Doom Emacs!
    While using Doom Emacs I copy vim configs to Neovim because I got bored of Doom for a week.
    Doom possesses me for 2 years (while still using Neovim for terminal things sometimes).
    2021 Summer I move my Vimrc configs on neovim to Lua. Still Doom.
    Doom Emacs decides to no longer open and freezes on startup. Nice.
    Now I’m on Neovim. Waiting for nativecomp Emacs. I still regularly open Doom Emacs to check whether it got fixed magically by itself (no luck as of today).

    I’m happy with with neovim currently. I feel like neovim is like more robust and Doom Emacs can like do many many super cool and maybe little things, but sometimes decides to bug itself. Hard choice.

      • @iortega@lemmy.eus
        1•2 years ago

        Your comment didn’t arrive to me until today. I already fixed the problem. I seemed to have some kind of error on my config, but for some reason I didn’t matter until the day Emacs broke. dunno.