3 ms·

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 informatio

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.

hiAndrewQuinn 1y ago
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.
- bayindirh 1y ago
  When starting to work on something, I generally do a sanity check to see that the fundamentals are there and correct versions, then throw that part of the context out of mind, knowing that I stand on firm ground. I found out that with this verify-and-forget step, I work much more efficiently. As a result, my workflow becomes independent of the machine I work on, because I become the tool, not my setup. After that point, only having a "$" at the beginning of the line is enough. Of course everyone have their own choices, and YMMV.
- bredren 1y ago
  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.
  - JimDabell 1y ago
    How often are you switching these things that you need their values in sight at all times though? Even for cases where I need to use old versions, I don’t need a reminder of that every time I run a command.
    - bredren 1y ago
      All of the time. Often I'm working with 3-4 different project contexts simultaneously. It isn't that useful but I do glance it when I'm working on dependencies and to ensure the context between a terminal session and pycharm's interpreter match. The information doesn't cloud the prompt for me though, as it is right justified and I don't really think about time to load, as the machines are relatively recent Apple Silicon.
acedTrex 1y ago
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.
- zikduruqe 1y ago
  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 = " " <- cloud symbol [aws.region_aliases] us-east-1 = 'use1' us-east-2 = 'use2'
  - acedTrex 1y ago
    Oh ya, for work the kubeconfig integration is absolutely essential, i bounce between local clusters and shared nonprod clusters all the time and while its not an outage to break the nonprods its going to annoy a lot of people so its nice to know which one is active.
- alganet 1y ago
  I literally use just PS1='$ '. `git status` to know git stuff. `pwd` for the current working directory, etc I also don't use aliases like `gs` or `..` One good thing about having a very minimal setup is that you feel at home anywhere. It wasn't always like this. I used many, many prompts and shell tools over the decades. The only tool that stood the test of time is tmux.
  - horsawlarway 1y ago
    Same here. I definitely went through a powerline, alias, huge vimrc, etc phase, but it turns out just sticking to the base toolset is pretty handy. I can sit down at (or ssh into) any machine and be basically just as productive, and it also turns out that I just always want to know more than nicely fits into the prompt anyways. There's something to be said for accepting the defaults of a tool, and learning to use them well. Customization is powerful, but... I think most times it's not the right call until you're already an expert in the tool at hand.
BowBun 1y ago
Problem is you can't get timestamps and run times of your commands 'when you really need it', unlike almost everything else
- bayindirh 1y ago
  Why the timestamps are that important? Honestly asking. You can always time your commands with "time".
  - stirfish 1y ago
    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.
    - bayindirh 1y ago
      I generally use Konsole's "notify when program exits" feature. For longer tasks, I have a small tool which I pipe to, and it sends me push notification with the output (if I prefer).
      - stirfish 1y ago
        I had a tool I'd pipe to, but I'd often only think about it after I'd realize that the command was going to take a while. A push notification sound cool; I used email because I knew how to hack it together with curl. Here's one zbell implementation, not sure it's the original but it looks like it does the trick: https://gist.github.com/oknowton/8346801 https://gist.github.com/oknowton/8346801
        bayindirh 1y ago
        Thanks for sharing the bell. I'll take a look. If you want to try push notifications, I use https://pushover.net https://pushover.net as a service. I developed the tool myself, and it's at https://git.sr.ht/~bayindirh/nudge https://git.sr.ht/~bayindirh/nudge if you feel like checking it out. If you want to host the whole push notification infrastructure, you can look at https://ntfy.sh https://ntfy.sh which also can be integrated with cURL.

hiAndrewQuinn 1y ago

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.

bayindirh 1y ago
When starting to work on something, I generally do a sanity check to see that the fundamentals are there and correct versions, then throw that part of the context out of mind, knowing that I stand on firm ground. I found out that with this verify-and-forget step, I work much more efficiently. As a result, my workflow becomes independent of the machine I work on, because I become the tool, not my setup. After that point, only having a "$" at the beginning of the line is enough. Of course everyone have their own choices, and YMMV.
bredren 1y ago
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.
- JimDabell 1y ago
  How often are you switching these things that you need their values in sight at all times though? Even for cases where I need to use old versions, I don’t need a reminder of that every time I run a command.
  - bredren 1y ago
    All of the time. Often I'm working with 3-4 different project contexts simultaneously. It isn't that useful but I do glance it when I'm working on dependencies and to ensure the context between a terminal session and pycharm's interpreter match. The information doesn't cloud the prompt for me though, as it is right justified and I don't really think about time to load, as the machines are relatively recent Apple Silicon.

acedTrex 1y ago

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.

zikduruqe 1y ago
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 = " " <- cloud symbol [aws.region_aliases] us-east-1 = 'use1' us-east-2 = 'use2'
- acedTrex 1y ago
  Oh ya, for work the kubeconfig integration is absolutely essential, i bounce between local clusters and shared nonprod clusters all the time and while its not an outage to break the nonprods its going to annoy a lot of people so its nice to know which one is active.
alganet 1y ago
I literally use just PS1='$ '. `git status` to know git stuff. `pwd` for the current working directory, etc I also don't use aliases like `gs` or `..` One good thing about having a very minimal setup is that you feel at home anywhere. It wasn't always like this. I used many, many prompts and shell tools over the decades. The only tool that stood the test of time is tmux.
- horsawlarway 1y ago
  Same here. I definitely went through a powerline, alias, huge vimrc, etc phase, but it turns out just sticking to the base toolset is pretty handy. I can sit down at (or ssh into) any machine and be basically just as productive, and it also turns out that I just always want to know more than nicely fits into the prompt anyways. There's something to be said for accepting the defaults of a tool, and learning to use them well. Customization is powerful, but... I think most times it's not the right call until you're already an expert in the tool at hand.

BowBun 1y ago

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

bayindirh 1y ago
Why the timestamps are that important? Honestly asking. You can always time your commands with "time".
- stirfish 1y ago
  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.
  - bayindirh 1y ago
    I generally use Konsole's "notify when program exits" feature. For longer tasks, I have a small tool which I pipe to, and it sends me push notification with the output (if I prefer).
    - stirfish 1y ago
      I had a tool I'd pipe to, but I'd often only think about it after I'd realize that the command was going to take a while. A push notification sound cool; I used email because I knew how to hack it together with curl. Here's one zbell implementation, not sure it's the original but it looks like it does the trick: https://gist.github.com/oknowton/8346801 https://gist.github.com/oknowton/8346801
      - bayindirh 1y ago
        Thanks for sharing the bell. I'll take a look. If you want to try push notifications, I use https://pushover.net https://pushover.net as a service. I developed the tool myself, and it's at https://git.sr.ht/~bayindirh/nudge https://git.sr.ht/~bayindirh/nudge if you feel like checking it out. If you want to host the whole push notification infrastructure, you can look at https://ntfy.sh https://ntfy.sh which also can be integrated with cURL.