Show HN: A single command terminal configuration installer
1–10 of 39 posts
Re: Show HN: A single command terminal configuration installer
#2Not a noob but book marking for the cool library ideas.
Re: Show HN: A single command terminal configuration installer
#3Has anyone else tried it?
Re: Show HN: A single command terminal configuration installer
#4TL;DR: someone's dotfiles. Neovim, tmux, and Oh My Zsh.
Re: Show HN: A single command terminal configuration installer
#5While it looks great, for a real noob the real problem (at least when I was starting out this was mine) is fast terminal navigation. To learn to do that I always thought the normal progression is sort of like this:
1. Mastering getting around terminal with slight configuration (bash, zsh, random dotfiles, maybe a plugin manager)
2. Getting used to editing files in the terminal (Vim)
3. Managing multiple terminals at once (tmux)
Managing all of those changes at once kind of overloads you where it slows you down to much to really consider this a practical change at one once.
You have just about the same exact set up that I do as well barring a few minor differences, Nord theme included, which is pretty funny that they converged like that.
Re: Show HN: A single command terminal configuration installer
#6I think this is good. At the end of the day, the best environment imho for building efficiently is the terminal, but it's slowly becoming a lost art. :/
Re: Show HN: A single command terminal configuration installer
#7The last thing an inexperienced terminal user should be doing is installing a bunch of software without understanding how it fits together, how it is used, or how it is actually configured. If you want to understand your terminal stack, build it; don't have it built for you.
The better approach is to start from a basic setup. For example, with vim, don't use vim-sensible right off the bat. Instead, just use vim. If a need arises, research what you can set up to address it. If you are curious about what is out there, read through the source of plugins like vim-sensible, taking each option, reading the docs for it, learning a bit of vimscript as needed, and only adding stuff to your vimrc if you really understand what you are adding. Don't add a bunch of things all at once. Do one at a time, and try it out for a while.
Re: Show HN: A single command terminal configuration installer
#8TL;DR: someone's dotfiles. Neovim, tmux, and Oh My Zsh.
Pretty much, this.
My own dotfiles are installable with only a couple of commands - I just clone the repo and run a simple shell script that symlinks some things to a central location. The only thing that isn't included is the installation of binary dependencies (like neovim and its plugins), but that differs between OSes and didn't seem worthwhile to automate.
Re: Show HN: A single command terminal configuration installer
#9The last thing an inexperienced terminal user should be doing is installing a bunch of software without understanding how it fits together, how it is used, or how it is actually configured. If you want to understand your terminal stack, build it; don't have it built for you. The better approach is to start from a basic setup. For example, with vim, don't use vim-sensible right off the bat. Instead, just use vim. If a…
My thinking is it's easier to start out with a solid foundation that I think the "sensible" and oh-my-zsh projects give you.
Take tmux-sensible for example, https://github.com/tmux-plugins/tmux-sensible. Each configuration item is explained in detail.
So the goal here is to give new users a starting point that is well documented and explained, instead of finding joeschmo's dotfiles that has "set -g default-command "reattach-to-user-namespace -l $SHELL"" with no explanation on what that does.
Re: Show HN: A single command terminal configuration installer
#10This looks really well done. I've been meaning to do this for some time. While I agree it's best to learn to properly configure your tools, this can be a good first step for newbies.
The problem I run into with sharing dotfiles is that my dotfiles aren't what someone who's new should be using. They need sane defaults that they can build upon, not the mess that my dotfiles have become over 10 years. This seems to be a good solution to that problem; giving some nice basics to set a newbie on the right track.
Really well done.