Recently I stumbled over an article, about how to customize your shell prompt. What really surprised me, is that it lacked one of the most basic tips I learned nearly 20 years back: Always display a timestamp in the prompt, to be able to check how long a process is running or when it ended. (Don’t need it daily, but every so often it saves my butt. ;-)) The other trick is to always have a colorful prompt, to easily discern where output from programs start/stop. In total my PS1 looks like this (with GIT status at the end): [\e[32m]\u[\e[m]@[\e[35m]\h[\e[m] [\e[36m]\A[\e[m] [\e[37m][[\e[m][\e[31m]\w[\e[m][\e[37m]][\e[m]$(__git_ps1 “(%s)”)$

My question is, what customization, tips and tricks do you have for the shell prompt?

    • wolf@lemmy.zipOPEnglish
      3·
      1 year ago

      Damn it! That is such an obvious great idea, I feel like an idiot! Thank you very much! :-)

      Any advice/guide how to change the color for ssh sessions?

      • nfultz@lemmy.ml
        4·
        1 year ago

        Check for the ssh env vars. For example, I use PS1="${SSH_CONNECTION:+\u@\h:}\W\$" to hide the hostname when not on SSH, you could do something similar with the control codes for color.

  • multicorn@programming.dev
    4·
    1 year ago

    If you like customizing your shell, there are really cool things one can do with zsh.

    I have mine set up with suggestions to complete the name of the program, or even command line options for it.

    • wolf@lemmy.zipOPEnglish
      4·
      1 year ago

      zsh … it is totally awesome, I saw a lot of crazy autocomplete stuff by people using it. I stick to bash mostly because it is simply installed everywhere and good enough for my needs. (With some help like autojump for bash.)

  • vojel@feddit.de
    3·
    1 year ago

    I got different colors for Kubernetes clusters. Like green for testing cluster, yellow for development and red for production. Always taking a Quick Look before I do something

  • ProtonBadger@kbin.social
    2·
    1 year ago

    Most prompt customizers have an option for showing how long last command ran and whether it succeeded/failed or simply prompt timestamp, it’s often default. I use Tide, there’s also Starship and a number of others. You can also roll your own ofcourse.

  • GustavoM@lemmy.worldEnglish
    31·
    1 year ago

    Use PS1="▌\t▐\n\w→" to display your local time each time you press enter. And make aliases of lengthy commands such as alias internettest="curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python -" (You need to install python to run this.)

  • 12510198@lemmy.blahaj.zone
    2·
    1 year ago

    A person in this thread already recommended having different colors for different conditions like ssh and running as root, I havent seen anyone mention this specifically but you can determine if the current working directory is writable with something like [ -w "$(pwd)" ] and set the color to red or print a symbol if it doesnt return true.

    Also I recommend putting all the code and logic for your shell prompt in a shell function, and using a substitution shell to put it into the PS1 variable like this:

    __shellprompt ()
{
	if [ "$(id -u)" = 0 ]; then
		local PROMPT_EMBLEM='#'
	else
		local PROMPT_EMBLEM='$'
	fi
	printf "%s" "$(whoami)@$(uname -n):$(pwd)"
	printf "\n%c " "$PROMPT_EMBLEM"
}
PS1='$(__shellprompt)'

    Now this is just a really barebones example, there is a whole lot more you can do like passing in the last exit code through the argv of your shellprompt function like this PS1='$(__shellprompt $?)' and like print it out if its non-zero so you wont have to like echo $? to see if the last command failed, but you should be able to still do this. In my testing, running the shell prompt function in the subsitiution shell didnt effect the $? variable.

    In my first comment on another thread about shell prompts, I posted my full shellprompt, it is slightly outdated (I just changed hostname to uname -n), if you cant find it feel free to send a message or just ask, and I will send you the code.

    • wolf@lemmy.zipOPEnglish
      2·
      1 year ago

      Wow, thank you very much! :-)

      This example is very enlightening. I was kind of aware that one could run shell functions and even use a GIT function in my prompt, but I never thought it through and your example brings the point home.

      I’ll waste most probably a few hours to find my perfect prompt function!

      (Mandatory xkcd link Nerd Sniping)

      • 12510198@lemmy.blahaj.zone
        2·
        1 year ago

        Im glad I was able to help!

        Something that should be noted when adding colors to your shell prompt function is adding the non printable characters that keep the terminal from buggin out, this caused me a massive headache until I figured it out. When putting it in the PS1 variable directly you will put \[ to begin a color sequence and \] to end one, but printf will print a literal [ and ] so instead you will have to use \001 to start and \002 to end, I also recommend changing \e to \033 or \x1B to make things a bit more portable. For a quick example \[\e[1;31m\] would become \001\033[1;31m\002. Without these characters the terminal will like glitch out when you type a long command and then go back to the front.

        If you are like messing around or trying to learn a new programming language, you can try like porting your shell prompt to that language, Ive ported mine to C and set it using the same subsitution shell method, I thought it was a fun lil challenge.

        But anyways, I hope you have fun customizing your shell prompt!

        • wolf@lemmy.zipOPEnglish
          2·
          1 year ago

          Thanks, of course the color escapes are the first thing I ran into yesterday, when I played around with prompt functions. ;-)

          Porting your prompt command to another language is a very nice and practical little project, perhaps I will give it a go with Go. (Pun intended ;-))

          Have a great week!