Re: Text Editor Question

[MidLifeXis]

An editor (or any toolchain) is only as good as it allows you to perform. I often times compare a good development environment to a mechanics tool chest. There are some worn tools that look ugly, but perform a job very well for a particular mechanic. The same tool in another mechanic's hands may cause them to lose a thumb. There may be a tool created by the mechanic for a particular job. There may be a couple of tools way in the back of the lowermost drawer that are only used once in a great while, but allow the job to be done right.

Basically, if you have the flexibility (for example, team mechanics may dictate a standard toolset), become intimately familiar with your toolset. If a certain tool causes you to injure yourself, either modify it or switch tools. Learn your preferred toolset well and the functional basics of others that you are likely to encounter.

Personally, I use Emacs with org-mode, magit, perl-mode and cperl-mode (each has its strengths), a unit testing framework (called on file save), some format shackles, various other modes for other languages, ECB for some window management saneness, tramp for editing of remote files, vlf for large files (edits using a sliding window), and a bunch of home-grown tools that make my programming life easier. I have used Emacs for 20-mumble years, so it is comfortable. I use vi, sed, awk, and so on when it makes sense.

Different toolsets have different nuances that fit different styles of programming and programmers. Find one that fits and learn it well.