My team wants to follow absurd standards for development. I use vim and found a pretty good way to do this.
au BufRead,BufNewFile *.go set shiftwidth=8
au BufRead,BufNewFile *.go set tabstop=8
au BufRead,BufNewFile *.rb,*.py set shiftwidth=2
au BufRead,BufNewFile *.rb,*.py set tabstop=2
Everything else is 4 spaces by default in the global settings – Rust, Bash, JS, etc.
Full settings for anyone interested:
filetype plugin indent on
set expandtab
set shiftwidth=4
set tabstop=4
au BufRead,BufNewFile *.go set shiftwidth=8
au BufRead,BufNewFile *.go set tabstop=8
au BufRead,BufNewFile *.rb,*.py set shiftwidth=2
au BufRead,BufNewFile *.rb,*.py set tabstop=2
set number
syntax enable
Google/Golang standards, PEP8 standards (), and I guess all the Rails twinks used two spaces back when Ruby was the new hotness so they want to do that. Most people on my team come from a Ruby background. One guy is from game dev/C++. I’m from systems and networking.
My eyes bleed resisting to soap box every single day.
I’m of the opinion that 4 space tabs is is ideal, 8 is acceptable for boomers who can’t see well and more over, 2 spaces just makes it very difficult to see where things are.
Every job I’ve had I used four spaces. Unless they specifically asked for something else. But my whole life I’ve used four spaces: Java, JavaScript, C, C++, Go, Rust, Bash, VisualBasic6, PowerShell, Pascal…
I don’t get why Rob Pike decided to do 8 spaces, unless they just thought it was funny. Vim defaults to 6 so that would have made more sense.
I’m bumping my head against the wall with something that should be so simple.
I want to make some encrypted 7z archives, so I can upload them to google drive for backup.
I don’t care about compression, since the gain are so small, and the added time to create the archive are so huge.
But gnomes built in file roller has no option for compression level when creating the archive. I googled about and installed the dconf-editor, and found the place to set the default compression level.
But all the guides says to set the level to maximum, for storing with no compression. Which goes completely against my own logic when I want zero compression.
But testing with an .mkv file, the cpu is pinned at 100% on both very fast and maximum. So it doesn’t make a difference anyway…
I’ve also tried out peazip, it has the option to store files, and it’s pretty much at regular copy-paste speed, which the “store option” should be.
But every time it finishes making an archive, it spits out an error. It stops at 99% with error 127: Cannot execute requested operation. None of my googling have revealed an answer to that problem.
So I can’t trust it, since it can’t complete its job without an error.
Man I miss Winrar…
So, is there some way to set file roller default compression to zero compression?