Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Starship: A minimal, fast, and customizable prompt for any shell

starship.rs

Post reply on HN
Print view View original

31–40 of 216 posts

Re: Starship: A minimal, fast, and customizable prompt for any shell

#31

Post by bredren »

hiAndrewQuinn wrote: post #22
skydhash wrote: post #20

Earlier 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.

I like stuffing everything which might be important to the context window in there, personally. Saving 50ms on the prompt load sure beats a false negative when something goes wrong because I don't even think to ask whether I have the wrong Node version installed or something.

Yes. I show the python or node version of currently active venv and venv name.

Also, I somehow worked in special characters for Python and other things that get screwed up if I don’t have the right nerd font installed on the system.

Re: Starship: A minimal, fast, and customizable prompt for any shell

#32

Post by BowBun »

skydhash wrote: post #20
hiAndrewQuinn wrote: post #17

I like maximalist prompts, and indeed Starship is what Shell Bling Ubuntu [1] installs on a new dev machine. But they're not everyone's cup of tea. If I wanted to recommend to someone the min-maxed, highest density thing they could add to their prompt, it would simply be the time your current prompt appeared + the amount of time the last command you ran took. These two pieces of information together make it very easy…

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.

Problem is you can't get timestamps and run times of your commands 'when you really need it', unlike almost everything else

Re: Starship: A minimal, fast, and customizable prompt for any shell

#33

Post by Twirrim »

voidUpdate wrote: post #2

Does the speed of your shell matter? Surely the speed of the programs that you're running through your shell matter more. I've never been let down by how fast bash can tell a program to start running EDIT: oh, i misunderstood, its just the prompt at the start of your shell... I dont think ive ever been annoyed at how fast that renders either

Every single time your prompt appears, your shell is doing something. I've tried using various prompt customising things in the past, but they've almost all been written in shell, and always been palpably slow. To the degree that I've found it irritating and stopped using them.

Starship is the first one that hasn't irritated me, in no small part because it's lightning fast, typically only couple of milliseconds to gather and render the prompt.

This is the first time I've been able to stick with one.

Re: Starship: A minimal, fast, and customizable prompt for any shell

#35

Post by Twirrim »

b0a04gl wrote: post #15

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

Starship is very fast, taking only a couple of milliseconds to gather the data (and you can easily configure it to minimise what it'll spend time gathering). It's night and day compared to other ones I've tried, where the hundred millisecond-ish delays annoyed me.

Re: Starship: A minimal, fast, and customizable prompt for any shell

#36

Post by pasc1878 »

nodesocket wrote: post #30
hu3 wrote: post #25

I'm a long time user of https://github.com/ohmybash/oh-my-bash It would be nice to have a comparison and reasons to change from popular tools.

Came here to ask the same. Long time ohmyzsh user, and wondering what new features / benefits Starship has.

Basically it is quicker.

I also expect it has everything that you have in your prompt so is a direct replacement without losing anything.

Re: Starship: A minimal, fast, and customizable prompt for any shell

#37

Post by bayindirh »

BowBun wrote: post #32
skydhash wrote: post #20

Earlier 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.

Problem is you can't get timestamps and run times of your commands 'when you really need it', unlike almost everything else

Why the timestamps are that important? Honestly asking.

You can always time your commands with "time".

Re: Starship: A minimal, fast, and customizable prompt for any shell

#38

Post by zikduruqe »

acedTrex wrote: post #27
skydhash wrote: post #20

Earlier 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.

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 = " "

Re: Starship: A minimal, fast, and customizable prompt for any shell

#39

Post by stirfish »

bayindirh wrote: post #37
BowBun wrote: post #32

Earlier quoted context omitted.

Problem is you can't get timestamps and run times of your commands 'when you really need it', unlike almost everything else

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.

Re: Starship: A minimal, fast, and customizable prompt for any shell

#40

Post by bertmuthalaly »

bayindirh wrote: post #37
BowBun wrote: post #32

Earlier quoted context omitted.

Problem is you can't get timestamps and run times of your commands 'when you really need it', unlike almost everything else

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.
Post reply on HN