The key to being productive as a programmer is to have a great code editor. I have been an avid user of Atom since 2014, and its successor Pulsar since now in 2023.

Pulsar (former Atom) is still the best code editor in my opinion. It is easiest and fastest to use, has all the nice productivity boosting plugins and is overall great for all the same reasons the Atom was great. 🚀

See also !pulsaredit@lemmy.ml

  • spartanatreyu@programming.dev
    1·
    9 months ago

    I remember being really interested in Helix when it came out, but it didn’t have a built-in file picker.

    Is this still an issue for users? Is there a built-in solution, or a usermade solution to this?

    Also, is there plugin support?

    I can’t use an editor without rainbow indent/brackets, without them code just takes too long to read that it becomes frustrating.

    • Turun@feddit.de
      1·
      9 months ago

      Space-f lets you open a file in the current workspace, and :open /path always let’s you open any file on the computer

      Plugin support not yet I think. Not gonna lie, I chose helix over nvim for it’s good out of the box experience, so I didn’t actually have a need for plugins yet.

      Fair enough. That would be a use case for a plugin (or simply a setting!)

      • spartanatreyu@programming.dev
        1·
        9 months ago

        Space-f lets you open a file in the current workspace, and :open /path always let’s you open any file on the computer

        Is this a file tree, or just a fuzzy finder?

        Fuzzy finders aren’t a substitute for a file tree picker. They’re only great, until you don’t know the name of a file, or until you need to know of a file’s existence in the first place.

        • Turun@feddit.de
          1·
          9 months ago

          File tree not a file tree like in a file explorer, more like the output of find, but with filtering. The letters you type to restrict your search only need to present in that order in the file path, not as a string.

          So “abc” would match “./assets/others/abort/cancel.png”, not just “./assets/abc.png”

          Additionally, lower case letters match case insensitive, upper case letters match case sensitive. This is surprisingly helpful if you don’t use exclusively lowercase file names.