241–250 of 304 posts
I use oh my zsh for exactly one reason: I can get a good shell experience out of the box and immediately start working on stuff productively, whether it's a new machine, a new remote host or a container. I could spend hours figuring out all those things, bit I'd rather use that time for something more important.
This thread feels so foreign to me. I use basic ass vanilla Windows terminal. It’s fine. I also use the vanilla built-in to VSCode terminal. It is also fine. Terminals are such a small, unimportant part of my job I barely even think about them.
You'll never get back those milliseconds. Just like I can't get back the time I wasted reading this article.
The amount of time this author is complaining about is like, a fraction of the time I spend getting through the first few sips of coffee in my day. I'm sure there's so many bigger time optimizations to tackle first. This feels like a strange hang up to me.
I notice the delay, but I try to check myself with it. Not everything has to be instant gratification. We're ruining our brains.
Earlier quoted context omitted.
FWIW if you're on a machine where you're allowed to use non-default configs like oh-my-zsh, you could also just copy over your own custom config. It seems like you're implying the alternative to using oh-my-zsh is to rewrite your config from scratch every time or use the default. It doesn't quite add up to me. If you craft a config file of your liking one time, then back it up somewhere, track it with git, whatever,…
> just copy over your own custom config That already defeats the purpose: I don't want to copy things around I never spend time crafting a custom config
> For Vim users, I also suggest enabling Vim mode in Zsh. It makes editing commands much faster. I am also an avid Vim user but I disagree. The default readline is perfectly fine for single line commands (you do have to know your way around some basic commands though C-a/u/k/l/w...). To edit long commands in $EDITOR you can always do C-x C-e in bash/zsh (M-v in Fish). As a matter of fact everytime I pair program with…
Readline settings depend on what you're already used to. If you're comfortable with vi key bindings, then being in normal mode, navigating with `w`/`b`, deleting a word with `dw`, deleting up to a quote with `dt"`, etc., are all done with muscle memory, and should be much faster than learning the equivalent Emacs bindings, pressing unintuitive key chords, or opening the command in an editor. I don't like opening an editor since it's an interruption, and it hides the output of the previous command.
I wish I could have the full power of Vim in my shells. For example, I miss the delete between characters binding. `di"` or `di'` are great for modifying argument values.
Earlier quoted context omitted.
I'm so glad I switched to fish, I'd rather have genuinely good settings out of the box rather than endless configuration, and honestly it's much better out of the box than any configuration I've ever had. Only drawback is that it's not POSIX, no issue for me, but maybe for people who have a lot of muscle memory with bash.
I tried fish for a while but as someone who heavily used bash before I couldn't get used to the new language. I also didn't feel they the language was much better than bash, at least for my usage. But I loved the default automatic coloring of arguments, underlining of files, etc. Later I found fizsh, which I love and still use as default shell now. It's basically a configuration around zsh adding the colors, completi…
Are we really quibbling over 400ms startup delay to open a new terminal?
HN has gone on a decade long crusade against Electron, of course 400ms is a lot.
Earlier quoted context omitted.
I've been using it for the last 6 or 7 years and I can only remember one specific feature I use a lot: "unset HISTFILE" to disable history when I need to run commands with passwords. Other than that, oh-my-zsh with git, systemd, and fzf plugins. Saves a lot of typing. The main selling point for me is how easy it is to setup.
Just out of curiosity, what sort of typing do those plugins save in comparison to doing it in bash? Can you give some examples?
git commit -> gc
git status --short -b -> gsb
git checkout -> gco
systemctl --user restart -> scu-restart
Nothing that you couldn't come up with yourself, but I've been using for so long it has become a standard for me.
The fzf plugin enables a fuzzy finder when you hit ctrl+r or ctrl+t. You need fzf installed.
Earlier quoted context omitted.
I use a lot of short-lived terminals. I have zsh+foot configured so that ctrl+shift+n opens a new terminal with the same current directory, so when using Vim, that's as fast as putting Vim in background, but I can tile both windows easily. I never have more than a one or two dozen terminals at a time, but I definitely open hundred of short-lived ones.
Why? You've said you do but not why you do? Why not leave a terminal open?