loading...

Discussion on: Text editor fetishists, unite!

Collapse
moopet profile image
Ben Sinclair

My pet peeves?

First off, and it might sound strange from me as a die-hard vim user, but I don't like the learning curve for a lot of editors-that-think-they're-IDEs. Especially around areas like project management. If I want to edit a file and have to define a new project first I'm always a little miffed with the demand. Then after I get over being miffed I move on to being apprehensive, because I'm not actually sure what the editor thinks it "owns" now, and where some kind of project files might appear and where settings are stored and what happens if I edit a file outside this ecosystem and and and...

Secondly if something like VS Code has (because it's Microsoft...) sucked up all the file associations and started thinking it's the ideal editor for everything from XML to PHP, that aggravates me. Especially as I often don't notice for weeks until I click on something and have to stop for a moment and think, wtf?

Lastly - and I don't mean this passive-aggressively, other commenters - when people don't read the question and turn "what are your pet peeves" into "what editor do you prefer" simply because the title of the post had something about editors in it. We're all veterans of a thousand editor wars.

It's not a race :)

Collapse
qm3ster profile image
Mihail Malo

I avoid this problem by almost never opening files :)
Have you tried that?

Edit: I mean I just open the program, whether graphically or from the command line, vs using open or xdg-open or clicking files.

Collapse
tux0r profile image
tux0r Author

I have noticed that I should have chosen a better title for my question ... :))

If I want to edit a file and have to define a new project first I'm always a little miffed with the demand.

Yup! Gladly, last time I had that was on Eclipse which I stopped using around 2009...