I think the possible valid answers are: “vi”, “emacs”, “both”, “seriously it’s 2024”, and " huh?"

    • unmagical@lemmy.ml
      4·
      10 months ago

      Proficiency is absolutely key. I was troubleshooting a feature with a Jr the other day and asked him to search through the log out put (that was currently being displayed on his terminal). Unfortunately he was trying out a new emulator and didn’t know how to actually search the output.

      We went about it a different way, but at the end I just told him it didn’t matter what tools he used as long as he actually knew how to do what’s required with them and to please get that figured out for next time.

  • Nibodhika@lemmy.world
    8·
    10 months ago

    I learnt Emacs years ago, it’s very helpful to the day-to-day terminal use, however if I could go back I would learn Vi instead, it’s better for pinky strain.

  • ReverseDiarrhea@lemm.eeEnglish
    7·
    10 months ago

    emacs. If you want vim keybindings there is a mode in emacs called “evil-mode”. If sticking with pure emacs I recommend rebinding the caps lock key on your keyboard to control.

  • agent_flounder@lemmy.worldEnglish
    6·
    10 months ago

    Vi for me for config, script, and text type files. Used to use emacs a lot for developing hobby stuff but prefer other IDEs now.

  • sincle354@kbin.social
    5·
    10 months ago

    Both because they are the ultimate tools in maneuvering a terrible, terrible development environment. For reference, Sigasi Studio costs 2,000$ PER YEAR, and it still doesn’t work for our dev environment!

    Let me paint a picture: Corporate job that won’t let you download anything except whatever you can smuggle through a git checkout. It took a month to convince IT to download vim 9.0 on the server. The programming language? VHDL and SystemVerilog and UVM. Horrible language support that relies on proprietary compilers/simulators, and always the ones you aren’t using. The one you are using is so obtuse that it has literally 50 configuration files for a single project. All of it is run with a janky python script with half of the flags not working. LSP support is out of the question since it dynamically pulls files from god knows where with at least 10 layers of …/ relative pathing.

    All I can do on vim is

    • ctrl+p for fuzzy file finding and a massive blacklist of intermediate files to ignore,

    • a custom :Make command with custom errorformat that you can navigate through,

    • Universal Ctags with per library indexes to reference those far off files,

    • and a fuckton of grepping for when Go To Definition (ctrl+]) grabs the wrong location.

    Vim’s autocomplete is almost always good enough. If my laundry list of plugins break, I can literally fix them on the spot and even submit the merge request on github. If you take into consideration all of this configuration and learning effort, I still save hours of navigating through the hundreds of files I have to essentially reverse engineer. My coworkers are all electrical engineers and it shows They’re using godforsaken nedit with no syntax highlighting…

  • jordanlund@lemmy.world
    5·
    10 months ago

    Nano (pico). You shouldn’t have to look at a quickref to save and quit a document.

    Get in, make your changes, get out.