News for hackers. Stuff that matters.
Re:Colorize Your CLI by monokh on Sunday July 26, 2020 @01:57PM (#23958829)
Really tempted to install starship but I also do a bunch of sensitive stuff with my terminal. Should I be worried about using this? I understand it's open source, yet still not confident.
Re:Colorize Your CLI by matchai on Sunday July 26, 2020 @03:37PM (#23959565)
Starship maintainer here. I'm happy to answer any questions have about how it works.

Every render of the prompt is fully stateless. Starship has no tracking, telemetry, and never calls home. :)

Re:Colorize Your CLI by danyspin97 on Sunday July 26, 2020 @02:15PM (#23958960)
Keep in mind that having bash history is already a treat since `~/.bash_history` is readable by every program you run.

If you want to be 100% safe you could just monitor the process and see if it opens any internet connection but I am confident it is just a local program.

Re:Colorize Your CLI by O_H_E on Sunday July 26, 2020 @09:49PM (#23961622)
> treat

*threat

Re:Colorize Your CLI by 1_player on Monday July 27, 2020 @06:53AM (#23963855)
starship looks good on paper, but the fact that all plugins are by default enabled (from what I can tell from the docs) is a no-go for me.

Why do people need all that information on their prompt? I understand showing the git status, but is it really necessary to know that your battery is discharging and you're currently using node v10.12.3 and elm v1.2.3 every single time you run a command in some directory?

Re:Colorize Your CLI by matchai on Thursday July 30, 2020 @01:32PM (#24000834)
Starship can be quickly configured to have a select few "modules" enabled. This can be configured with `prompt_order`, documented here: https://starship.rs/config/#prompt

I, for one, like to know what version of Node will be used when I'm jumping between projects, so I can know which features are available to me at runtime.

Eventually we'd like to include an interactive configuration tool to help folks find a configuration that meets their needs.