2 ms·
I like to cut noise out from my code, but I've never understood "distraction free" modes in code editors. If you're trying to be productive, you should be regu
by namuol 13y ago
I like to cut noise out from my code, but I've never understood "distraction free" modes in code editors.
If you're trying to be productive, you should be regularly checking the results of your code changes (i.e. watching test results in a terminal or a browser window); full-screen modes like this only seem to make it more jarring when I switch out of them...
- bilalq 13y agoThe real utility of such modes comes when you're trying to read code. At such moments, you want to get rid of all the things that would normally be of great use. Things like line numbers, status bars, gitgutters, etc... Aside from reading code, such modes are also great for working with markdown files. With them, you really only care about content. The forcing fullscreen thing is definitely not for everyone though, I agree. I think such plugins would do well to have fullscreening be a configurable behavior. Even my own distraction-free plugin is guilty of forcing fullscreen onto GUI Vim users (I never really notice, since I myself use terminal vim).