Hacker News Reader

Comment by vertex-four | Hacker News Reader

That vim dumps you into a screen with no guidance and where your keypresses appear to do nothing (or apparently random things!) would be the problem here. It would take very little to have it say "type :help to learn how to use this program" in the bottom of the screen when it starts up. It's also confusing because many Linux systems are set up by default to launch vim whenever another application requests an editor, even if the user uses something they are more comfortable with otherwise. This could be resolved by asking "which editor do you want to use?" instead of dumping the user into a randomly selected editor.

You can build powerful systems without confusing people who often never intended to wind up in your program in the first place. You can even build them to show people how to use them.

View on HN

It would be great to have a tutorial you can run, a tutor of some kind perhaps.

> It's also confusing because many Linux systems are set up by default to launch vim whenever another application requests an editor, even if the user uses something they are more comfortable with otherwise.

  export EDITOR=/my/fancy/editor

Way to miss the entire point.

You usually don’t figure this out until after you’ve already run into this issue.

In Windows if you open a new filetype for the first time, it asks you what application you’d like to set as the default type, and on top of that it tells you where to go to change that later. That’s what beginner friendly UX looks like, not just throwing the newborn into the pool like Linux does with Vim editing.

It is not that I don't understand the "problem" - after all, I ended my very first accidental vi session with a reboot as well. But that was 23 years ago, long before Linux/GNU distros would be installed with a GUI and then boot into a GUI.

If the "newborn" in 2020 insists on using the terminal instead of the much more beginner friendly options that are the default nowadays... granted, but why compare a terminal editor in unix to a GUI? That is like comparing apples and oranges and then complaining that the strawberries don't taste like bananas.

Throwing up a menu to provide context and ask you what you want to do, rather than assuming a default, is not some thing that only magical GUIs can do. CLIs with menus is not some crazy new thing.

As an example of how manually configuring the editor flag can be annoying, consider a job where you regularly ssh into many machines, each that just by default use vim. I know how to use vim, I just don't like it, but pretty much every single machine I have booted into always assumes I want to use vim, and even if you remember to change the flag doing it to many machines all the time is majorly annoying.

That's what the EDITOR environment variable is for.

Which is great... as long as you knew about that environment variable before you got into this situation in the first place. You're not exactly told about it during the install process or "first steps" guides for any distro I'm aware of.

Reply on news.ycombinator.com