I edit with (g)vim on Ubuntu Linux.
My vim configuration (github.com/juanlanus/vimconfig) renders a screen of almost only lines of code, no space wasted in clickacle artifacts.
The fonts are "Source Code Pro Medium" and the beautifun "Montserrat" for proportional spacing.
I use mainly BitBucket (instead of GitHub) because it allows me to have private repos for free. I interact with the remote repos using plain command line Git.
GNOME Terminal, the Ubuntu default.
Actually, I'm old and I use vi, later vim, since like 40 years ago, in SCO Unix and later in Windows 98 (it was a 70K exe).
To me, vim is the most productive tool, the one with highest usability, because is allows me to do more work with less keystrokes more safely.
I don't confuse usability with ease to learn. To be proficient with vim you need some training, and then some more. But it gets the job done quickly; for example I seldom take my hands out of the keyboard to grab the mouse.
I edit with (g)vim on Ubuntu Linux.
My vim configuration (github.com/juanlanus/vimconfig) renders a screen of almost only lines of code, no space wasted in clickacle artifacts.
The fonts are "Source Code Pro Medium" and the beautifun "Montserrat" for proportional spacing.
I use mainly BitBucket (instead of GitHub) because it allows me to have private repos for free. I interact with the remote repos using plain command line Git.
GNOME Terminal, the Ubuntu default.
Actually, I'm old and I use vi, later vim, since like 40 years ago, in SCO Unix and later in Windows 98 (it was a 70K exe).
To me, vim is the most productive tool, the one with highest usability, because is allows me to do more work with less keystrokes more safely.
I don't confuse usability with ease to learn. To be proficient with vim you need some training, and then some more. But it gets the job done quickly; for example I seldom take my hands out of the keyboard to grab the mouse.
the last few lines are so true