4 ms·
My guess is that you ended up on a machine that has the default editor as vi. TO fix this, set your shell's EDITOR env variable to something like nano. I agree
by nouveaux 6y ago
My guess is that you ended up on a machine that has the default editor as
vi. TO fix this, set your shell's EDITOR env variable to something like
nano.
I agree that VI's default is so different from the modern editor that it's
very frustrating to get stuck in it. However, learning vi pays dividends.
- forrestthewoods 6y agoI tried setting the editor to TextEdit app path. That didn’t work. I also tried Sublime, which also didn’t work. Setting the editor is really a 3 step process. Add application to PATH. Create an alias. Specify the alias. VSCode has a command to do steps 1 and 2 for you. My next weekend project is to learn Vi. (Any tutorial suggestions?) I don’t want to. But I have to. Smartphones are so intuitive toddlers can use them. Vi is so non-intuitive it requires going to external tutorials to learn how to edit text. Sigh. :(
- triceratops 6y agovimtutor - it should already be installed on your system alongside vim
- projektfu 6y agoI think it’s hard to get EDITOR working with spaces in the path.
- nouveaux 6y agoUse vim adventures to learn. It will take the pain out of learning and will make you proficient in about a day. After that, force yourself to use it. Install vim plugin in vscode. In about 2 weeks, you will wonder why you didn't learn it sooner.