Starship: A minimal, fast, and customizable prompt for any shell
101–110 of 216 posts
Re: Starship: A minimal, fast, and customizable prompt for any shell
#102Earlier quoted context omitted.
For personal workstation, the current directory is enough. Maybe I change the color based the status of the last command. That’s pretty much the only information I need before entering any command. Everything else can be accessed when I really need it.
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.
Re: Starship: A minimal, fast, and customizable prompt for any shell
#103Re: Starship: A minimal, fast, and customizable prompt for any shell
#104Maybe it's finally time for me to sit down and write my own shell prompt once and for all. I wonder if I can make it context-aware of fish's editing vs normal mode when vi mode is enabled
Re: Starship: A minimal, fast, and customizable prompt for any shell
#105Re: Starship: A minimal, fast, and customizable prompt for any shell
#106I found https://ohmyposh.dev/ works for me. There’s something about transient prompts that (at the time?) was a problem for starship. There are several other alternatives I’ve tried with meh results.
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.
Re: Starship: A minimal, fast, and customizable prompt for any shell
#107Genuine question for all the people putting timestamps in your prompts: do you never look at your command history and see that they’re all timestamped?
Run a full screen term on my machine for a good chunk of my workflow and I just like to have time and battery in my term. I render it as ‘(15:35) [80} $ ‘ and for boxes without batteries it’s just ‘(15:35) $ ‘
Some times I’ll go back through my scroll back and look at the time when I’m trying to figure things out. Or when I run a command that generates a ton of output, I’ll note the time and run the command then later search back to the time in scroll back to start at the top of the log.
None of these are features I truly miss on a vanilla box, I can look at a clock or watch and will put a comment into the scroll back to find later.
Re: Starship: A minimal, fast, and customizable prompt for any shell
#108I'm trying to understand what they are demonstrating with the "false; true" commands in the little video loop. Can someone chime in?
`false` returns an exit code != 0
The prompt indicates whether the last command returned exit code 0.
Re: Starship: A minimal, fast, and customizable prompt for any shell
#109Personally, over time, I have stopped caring too much about prompt customization. I concluded that, no matter how carefully you curate your prompt, 90% of the information shown will be irrelevant 90% of the time*. After a while, your brain will start perceiving this as visual clutter and filter it out, to the point you may even forget the information is there, right in front of your eyes.
And for the things that matter, you probably need more details than any prompt can show you. E.g. are there changes in your git branch? Ok there are, good to know, but which files have changed? Just knowing that there are changes is not really actionable information. You need to run additional commands to get actionable details.
* the numbers are completely arbitrary, but you get the picture