: is your commandline, it does a lot of actions. w is write, q is quit. So you’re doing a write quit, the ! just tells it to fuck off and do the fucking command essentially.
If you open a read only file, and you need to quit just hit it with the :q! or if you haven’t made any changes, :q will work just fine.
naturally, as one would expect, you can hit all of these independently. :w just writes changes, :q will close as aforementioned.
Look, some of us old farts started on Linux back before nano was included by default, and your options for text editing on the command line were either:
vi/vim, a perfectly competent text editor with arcane and unintuitive key combos for commands
emacs, a ludicrously overcomplicated kitchen-sink program that had reasonable text-editing functionality wedged in between the universal woodchuck remote control and the birdcall translation system
Given those options, most of us chose to learn how to key-chord our way around vim, and old habits die hard.
Is it really? It’s been a couple of years since I used Java, but vs code sucked for it compared to IntelliJ. I used vscode for everything else but could never make a Java workflow stick.
It’s sort of minimalistic / lightweight alternative for IntellJ. Red Hat is working on the extension(s) which have worked fine for me at least for the past few years and it gets updates regularly.
I use VSCode for C++, C#, Java, Python and for things like docker-files, html etc. IntelJ is fine but a bit bloated in comparison with its menus, sub-menus, sub-sub-menus and built in unnecessary extra features for those just looking for code editor.
VSCode workflow with Java is mainly using it to write code, run tests, configure maven/gradle/docker/etc rest is more or less using CLI and Command palette.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.