4 ms·
"but the more you get used to plain-text, the easier it becomes to type commands rather than to search for options or buttons. The hard part is to remember whic
by hutzlibu 8y ago
"but the more you get used to plain-text, the easier it becomes to type commands rather than to search for options or buttons. The hard part is to remember which commands to type."
And this is where terminals suck and IDE's are strong. Integrated autocomplete and documentation. I do not need to remember every function or parameter, but I can directly look them up, while I type.
Is there something like this for terminals? I have not seen it, yet ... so, to put it in a picture:
https://xkcd.com/1168/ https://xkcd.com/1168/
But yes there is man and --help, but it is not really straightforward and fast, like a modern IDE. And usually I never find in time in --help what I am looking for, so am faster with googling anyway.
- turbinerneiter 8y agoThere is a whole bunch of shells with all kinds of autocomplete. Terminal editors like vim have plugins for autocomplete and integrated documentation. CLI programs typically have -h or --help. The whole "Terminal vs. IDE" argument is kinda weird. You can have an IDE in a terminal. This whole thing is about CLI/TUI vs. GUI, not terminal vs. IDE.
- hutzlibu 8y ago"this whole thing is about CLI/TUI vs. GUI, not terminal vs. IDE. " Good point. But can you recommend a vim setup with plugins? It has been a while since I tried it, and it was not to my liking, but I was more GUI adopted at that time.
- turbinerneiter 8y agoI'm the wrong guy to ask, I kinda dislike IDEs. I use vscode sometimes, exactly for the code completion and integrated documentation you mentioned. But I often use vim for the lack of that. Every helper can also be a distraction, every functionality is an interface you have to learn. Right now, I only have formatters (which also work as syntax checkers).