41–50 of 216 posts
Earlier quoted context omitted.
Why the timestamps are that important? Honestly asking. You can always time your commands with "time".
When you’re debugging, especially a complex system, especially during an outage or postmortem, understanding when your commands executed relative to when your log lines appeared is really helpful.
Earlier quoted context omitted.
Why the timestamps are that important? Honestly asking. You can always time your commands with "time".
I personally use a modified zbell (in zsh) to give me a notification when a command finishes after 30 seconds, and send me an email if it takes over 2 minutes.
Earlier quoted context omitted.
You don't need to know what branch you're on before running commands? I cant tell you the number of times ive been on the wrong branch executing stuff.
For me the AWS integration is nice. That way I know what account I'm on, and what region among my dozens of windows. For example: …/.config master on AWS_Prod (use2) starship.toml: [aws] format = 'on [($profile )(\($region\) )]($style)' style = 'bold #B23D2F' symbol = " "
Atuin and Starship the same Day on place 1? Next zellij :)
Earlier quoted context omitted.
I've used Powerlevel10k for ages ( https://github.com/romkatv/powerlevel10k ), but it seems it's no longer actively developed / maintained. I think it's a lot cleaner, how I have it set up right now it shows some information like timestamp, Ruby versions, command runtime etc on the right side, whereas Starship shows it right at the prompt.
Same here, that's what prompted my search. I felt I could get closest with oh-my-posh.
My personal favourite: PS1="%~ $ "
Atuin and Starship the same Day on place 1? Next zellij :)
Wondering if there are any other life-changing tools I'm missing out on...
every time your shell takes 100ms to render git status that you didn’t even need, you're paying invisible tax on flow. terminals should be reactive memory tools, not passive decoration. we optimize for code runtime but not for our own typing latency