How I'm still not using GUIs in 2019: A guide to the terminal

Re:How I'm still not using GUIs in 2019: A guide to the term... by jandrese on Thursday February 28, 2019 @10:05AM (#19271757)

This is why defaults matter. People sometimes downplay changes with "well, you can just tweak it if you don't like it", but in the long run tweaking the install every time is effort. Especially when you're working on non-internet connected machines. It's why I get annoyed when for example Ubuntu stops shipping the ability to burn DVDs on the install disk.

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by brootstrap on Thursday February 28, 2019 @10:14AM (#19271835)

I think vanilla VI (basically just modal editing in general) empowers the user enough to make it worth knowing. I'm pretty damn proficient editing code in a project (that I know granted) with hundreds of files using standard VI when i ssh to a VM or AWS machine etc. Still more proficient than people using an IDE locally without VI modal editing :p

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by zelos on Thursday February 28, 2019 @10:42AM (#19272083)

The default vim config is pretty weird: incremental search is off by default for some reason, I think it still defaults to using tabs for indentation, it doesn't change the working directory to the current file's.

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by flukus on Friday March 01, 2019 @12:51AM (#19278258)

Incremental Search - This can be incredibly slow on large files and/or network mounted files. It can also interact with line wrapping and highlight search to slow vim to a crawl. So I think it makes sense to leave it off.

Tabs - That's the way god intended it. Stop trying to force your indentation width on me.

Stable working directory - This is how every text editor I'm aware of works. I can see use cases where you might want to change it manually or automatically, but I don't want to have to guess which directory I'm in every time I open a file.

Even some seeming no brainers like turning syntax highlighting on can be terrible because it doesn't work well with dark backgrounds or other random colour schemes.

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by balp on Friday March 01, 2019 @12:33AM (#19278172)

Change working directory seans like the most stupid idea i ever heard... That would make:

  vim module/code.cpp
  :make

Not use the build system on the top level...

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by AnIdiotOnTheNet on Thursday February 28, 2019 @12:22PM (#19273008)

Why would you have to tweak it every install? Isn't the whole point of separating the configuration from the application's data so that you can move it around?

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by jandrese on Thursday February 28, 2019 @02:12PM (#19274138)

Moving in a configuration is tweaking it. And then you're on a machine that is STIGed or is on a standalone network or you're helping someone do something on their account. The end result is you end up back in the default mode a lot so you might as well learn it.

[ Parent | on HN ]